| @blaisep-sureify:matrix.org | This is great, now I understand how software factory does the github integration. Thank you | 02:34 |
|---|---|---|
| -@gerrit:opendev.org- David Ostrovsky proposed: [zuul/zuul-jobs] 846909: ensure-java role: Bump default java_version to 11 https://review.opendev.org/c/zuul/zuul-jobs/+/846909 | 06:34 | |
| @chgans:matrix.org | I've reported this issue: https://storyboard.openstack.org/#!/story/2010098 | 09:53 |
| @chgans:matrix.org | This is related to my attempt at demo'ing zuul+gerrit+repo (AOSP) | 09:53 |
| @chgans:matrix.org | I found it strange not being abble to attached files (demo source, screenshot, ...). | 09:54 |
| @chgans:matrix.org | Please let me know if there's anything i can do to improve the issue report | 09:54 |
| @fungicide:matrix.org | > <@chgans:matrix.org> I found it strange not being abble to attached files (demo source, screenshot, ...). | 13:59 |
| yes, latest storyboard has a story attachments feature, but we're stuck on an older version in opendev until someone finds time to redo the deployment mechanism (we need to move to a newer platform in order to have new enough python for it, and our old configuration management software is incompatible with the newer platform we'd need, so the plan is to switch to deploying containers of storyboard services) | ||
| @fzzfh:matrix.org | hello folks. I use softwarefactory zuul with remote logserver as CI. but zuul don't return logserver address on opendev comment. I have add zuul/web-root: http://47.111.113.211:8081/zuul/t/local. now it return http://47.111.113.211:8081/logs/19/194c4c8994a6a63782408f9c078dd9e3fb9ea89c/post/config-update/3a89a7b/, but my actual log address is http://47.111.113.211:8081/logs/19/194c4c8994a6a63782408f9c078dd9e3fb9ea89c/post/config-update/3a89a7b/. which param shoud I modify, any help would be appreciated. | 15:44 |
| @fzzfh:matrix.org | * hello folks. I use softwarefactory zuul with remote logserver as CI. but zuul don't return logserver address on opendev comment. I have add zuul/web-root: http://47.111.113.211:8081/zuul/t/local. now it return http://47.111.113.211:8081/zuul/t/local/build/19e74214767543b298c4e6c94c7788ed , but my actual log address is http://47.111.113.211:8081/logs/19/194c4c8994a6a63782408f9c078dd9e3fb9ea89c/post/config-update/3a89a7b/. which param shoud I modify, any help would be appreciated. | 15:46 |
| @fzzfh:matrix.org | I had use uploads-logs role with var: zuul_log_url. this include zuul_reutrn: log_url | 15:47 |
| @fzzfh:matrix.org | log can upload to remote logserver. but zuul don't return actual address. | 15:48 |
| @fungicide:matrix.org | fzzf: opendev's zuul doesn't comment with a link to the job logs, it comments with a link to the build result on the zuul dashboard | 15:48 |
| @fungicide:matrix.org | what you've observed is the intended behavior | 15:50 |
| @fzzfh:matrix.org | in https://review.opendev.org/c/openstack/manila/+/845586, like https://elab-os-logsrv.delllabs.net/86/845586/5/check/DellEMC_Unity_Manila_dhss_true/dfedc34/DellEMC_Unity_Manila_dhss_true/555 | 15:51 |
| @fzzfh:matrix.org | what should I modify, for return log.. | 15:51 |
| @clarkb:matrix.org | In opendev the base job runs the upload-logs-swift role which registers upload_results.url with zuul as a zuul return with this path: zuul.log_url | 15:51 |
| @fungicide:matrix.org | fzzf: there isn't an option to do what you're describing. the intended behavior is that zuul comments with the build result page for each build | 15:52 |
| @fungicide:matrix.org | can you describe why that isn't suitabel for your use case? | 15:53 |
| @fungicide:matrix.org | * can you describe why that isn't suitable for your use case? | 15:53 |
| @clarkb:matrix.org | Oh I see its the link to the build record in zuul that is the problem. Ignore me fungi has got it handle | 15:53 |
| @clarkb:matrix.org | * Oh I see its the link to the build record in zuul that is the problem. Ignore me fungi has got it handled | 15:53 |
| @fzzfh:matrix.org | I see other CI have return log on comment. what should I do for this? | 15:55 |
| @fzzfh:matrix.org | > <@clarkb:matrix.org> In opendev the base job runs the upload-logs-swift role which registers upload_results.url with zuul as a zuul return with this path: zuul.log_url | 15:57 |
| do you mean use upload-logs-swift role? I found SF base job have use add-fileserver and upload-logs role. | ||
| @fungicide:matrix.org | fzzf: those ci systems are using different software. i don't understand your question | 15:57 |
| @fzzfh:matrix.org | I want let zuul return log on opendev comment as CI.. | 15:57 |
| @fungicide:matrix.org | fzzf: zuul doesn't do that | 15:58 |
| @fzzfh:matrix.org | * I want let zuul return log on opendev comment for finish CI work | 15:58 |
| @fungicide:matrix.org | it's not how zuul is designed to work | 15:58 |
| @fzzfh:matrix.org | I see zuul have return like http://47.111.113.211:8081/zuul/t/local/build/19e74214767543b298c4e6c94c7788ed on comment.. | 16:00 |
| @fzzfh:matrix.org | when I use **success: gerrit:{}**. zuul would return result on comment | 16:02 |
| @tristanc_:matrix.org | fzzf: I guess your Zuul service is not publicly available, in that case, you'll have to setup the zuul-web service on the public host. | 16:10 |
| @clarkb:matrix.org | I guess the use case here is not wanting to make the zuul public, but being ok with the logs thesmelves being public? | 16:11 |
| @tristanc_:matrix.org | it's a common issue with third-party CI where the zuul control plane is not public | 16:11 |
| @clarkb:matrix.org | The zuul interface for job results really is much nicer than the raw logs. I'm not going to speak for openstack and the requirements they want to maintain but it seems like a good idea to make that a requirement | 16:12 |
| @fzzfh:matrix.org | I want let CI return logs, what should be done. is there any other way | 16:27 |
| @clarkb:matrix.org | fzzf: currently I think theo nly way is to report the build link. | 16:38 |
| @clarkb:matrix.org | * fzzf: currently I think the only way is to report the build link. | 16:38 |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/nodepool] 846625: Suppress component registry logging in command https://review.opendev.org/c/zuul/nodepool/+/846625 | 17:10 | |
| @fungicide:matrix.org | fzzf: zuul is designed so you can run the zuul-web service on a completely separate machine and just give it access to the database and zookeeper. that way your build results pages and the rest of the zuul dashboard can be put in a "dmz" or otherwise outside whatever packet filtering you have in place for the rest of the deployment. alternatively, you can set up a reverse proxy or do some sort of port redirection to make it accessible from the internet | 17:44 |
| @clarkb:matrix.org | corvus: can you check the comments on https://review.opendev.org/c/zuul/zuul-jobs/+/846909 as far as sneding notice for that change goes | 18:16 |
| @jim:acmegating.com | Clark: fungi i *think* that one makes sense to announce... i feel like it's highly likely to be used outside of opendev, so it's high on the list of roles i wouldn't consider codesearch to be exhaustive for. i think the main argument against it would be "it's so ancient of course no one uses that default" but then i think about enterprise use. at least, a 2 week notice seems prudent? or am i missing something? | 18:30 |
| @clarkb:matrix.org | I'll defer to your judgement on that. I'm not sure how many others are using zuul with java projects. I don't mind either as we've already set it to 11 where we need 11 | 18:36 |
| @clarkb:matrix.org | From a design perspective I almost wonder if we shouldn't drop defautls like that entirely and force users to be explicit about what they want always | 18:36 |
| @jim:acmegating.com | definitely yes for non-opendev java users with zuul. i can't say how many are using that role from upstream though. | 18:37 |
| @jim:acmegating.com | i'll send the email | 18:39 |
| @jim:acmegating.com | Clark: i think i agree a discussion about defaults sounds good. maybe the expectation could be that projects set project vars for things like that. | 18:41 |
| @jim:acmegating.com | Clark: maybe worth a zuul-discuss thread? | 18:42 |
| @clarkb:matrix.org | Sure. Do you want me to start one? | 18:42 |
| @jim:acmegating.com | i just sent the announce email | 18:43 |
| @jim:acmegating.com | zuul-maint: how is this proposed tag for nodepool (third time's the charm?): | 18:44 |
| commit a63f128d7392bf0e60f6150637a5564da536b0e3 (HEAD -> master, tag: 6.1.0, origin/master, refs/changes/25/846625/1) | ||
| @jim:acmegating.com | zuul-maint: and also, how does this look for zuul (the rare synchronized zuul/nodepool release!): | 18:46 |
| commit f3e4d399b0edcd98c97176fdfe38251e0ea86bd4 (HEAD -> master, tag: 6.1.0, origin/master) | ||
| @mhuin:matrix.org | wanna make it a hat trick and add a release for zuul-client? 🙂 | 18:47 |
| @jim:acmegating.com | zuul-maint: and this for zuul-client (sure thing!): | 18:48 |
| commit a6ce77acffd852219fd43a6dc61cbe637aa85bf2 (HEAD -> master, tag: 0.1.0, origin/master, origin/HEAD, refs/changes/22/834522/1) | ||
| @mhuin:matrix.org | do you think it warrants a minor version bump? Last release was 0.0.4 | 18:50 |
| @clarkb:matrix.org | > <@jim:acmegating.com> zuul-maint: and also, how does this look for zuul (the rare synchronized zuul/nodepool release!): | 18:50 |
| > commit f3e4d399b0edcd98c97176fdfe38251e0ea86bd4 (HEAD -> master, tag: 6.1.0, origin/master) | ||
| This is a change ahead of opendev but it is only a docs update. LGTM | ||
| @jim:acmegating.com | mhu: yeah, i think the new commands + config file change warrant it. (looking back, 0.0.3 probably should have been 0.1.0 but oh well) -- https://zuul-ci.org/docs/zuul-client/releasenotes.html | 18:58 |
| @mhuin:matrix.org | ok LGTM either way | 18:58 |
| @iwienand:matrix.org | in nodepool cmd line, we have "image-pause" and "image-unpause", but do any of the commands show the current paused status of images? | 19:46 |
| @jim:acmegating.com | ianw: believe it or not, that's literally on my todo list for today, so maybe wait a few hours :) | 20:00 |
| @iwienand:matrix.org | heh, i was going to write something, but your approach sounds even better :) | 20:03 |
| @jim:acmegating.com | ianw: ah, apparently "dib-image-list" will have `paused` in the `State` column | 20:12 |
| @jim:acmegating.com | that will show output for the pause commands, but not show what's in the config file | 20:18 |
| @jim:acmegating.com | ianw: were you looking for the "zk pause" or the "config file pause" ? | 20:24 |
| @iwienand:matrix.org | corvus: the ZK pause -- basically one admin had paused a build a while ago via cmdline, and i was unsure if it was currently unpaused | 20:26 |
| @iwienand:matrix.org | have to admit i didn't look at the image-list, i guess it makes some sense that the current image is "paused" and so no new images are built | 20:26 |
| @iwienand:matrix.org | although i was thinking of it more "we've paused building new images", so the current image is active, if that makes sense | 20:27 |
| @jim:acmegating.com | ianw: "dib-image-list" but yeah... the data model isn't quite right.... :/ | 20:28 |
| @jim:acmegating.com | but it's pretty close | 20:28 |
| @jim:acmegating.com | (image-list, which shows the uploads, won't show that it's paused, so they're still active; it's really the building, and therefore dib-image-list which shows the builds that will output `paused` as the state) | 20:29 |
| @iwienand:matrix.org | yeah, sorry, dib-image-list. gentoo is an example from http://nl01.opendev.org/dib-image-list | 20:30 |
| @iwienand:matrix.org | both those being paused implies that new builds are paused. an explicit "image-status" type command that listed the image names and paused status might be slightly clearer | 20:33 |
| @jim:acmegating.com | ianw: i agree; i think ultimately we need to rename a bunch of commands too. that's what "image-list" should be, and then we should have image-build-list and image-upload-list. this may be several changes. :) | 20:34 |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Simon Westphahl: [zuul/nodepool] 725810: Expose image build requests in web UI and cli https://review.opendev.org/c/zuul/nodepool/+/725810 | 20:45 | |
| @jim:acmegating.com | that was just a rebase ^ | 20:46 |
| @jim:acmegating.com | i think that the dib-request-list command there should also be combined with what we were just talking about... | 20:46 |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 847092: Convert dib-request-list to image-status command https://review.opendev.org/c/zuul/nodepool/+/847092 | 21:13 | |
| @jim:acmegating.com | ianw: swest tobiash ^ the manual build request and manual image pause systems seemed similar enough that it makes sense to have an "image-status" command that output information about both at the same time. so i morphed swest's "dib-request-list" command into "image-status". how's that look? | 21:14 |
| @jim:acmegating.com | ``` | 21:15 |
| +-------------+--------+---------------+-------------------+ | ||
| | Image | Paused | Build Request | Build Request Age | | ||
| +-------------+--------+---------------+-------------------+ | ||
| | fake-image | True | pending | 00:00:12:29 | | ||
| | fake-image2 | False | | | | ||
| +-------------+--------+---------------+-------------------+ | ||
| ``` | ||
| @jim:acmegating.com | that's what that looks like | 21:15 |
| @iwienand:matrix.org | ++ the regular naming pattern of image-* makes sense to | 21:22 |
| @iwienand:matrix.org | to me | 21:22 |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 847106: Add nodepool.image_build_requests metric https://review.opendev.org/c/zuul/nodepool/+/847106 | 21:53 | |
| @jim:acmegating.com | pushed zuul, nodepool, zuul-client tags | 22:49 |
| @jim:acmegating.com | and emails sent! | 23:59 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!