| -@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 964459: Reset the success flag before each run playbook https://review.opendev.org/c/zuul/zuul/+/964459 | 07:10 | |
| -@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 964459: Reset the success flag before each run playbook https://review.opendev.org/c/zuul/zuul/+/964459 | 09:50 | |
| @mhuin:matrix.org | hey there, I know it is possible to promote a change with the Zuul API so that it's moved up in a dependent pipeline like in gating. But is it possible to ensure a buildset is the next one enqueued across all tenants and pipelines? Basically how is zookeeper's queue handled, FIFO or is there a way to prioritize a buildset? (assuming getting the nodeset is not a bottleneck) | 13:04 |
|---|---|---|
| @clarkb:matrix.org | mhu: are you talking about node assignments? | 15:23 |
| @clarkb:matrix.org | I believe things are queued in order by pipeline priority. Its only until you get to node assigments where slow clouds can make it apepar that things are out of order | 15:24 |
| @clarkb:matrix.org | (I guess semaphores can also impact ordering but if we assume no semaphores then this is the case) | 15:24 |
| @mhuin:matrix.org | it's a bit of a hypothetical, but let's say there's a change I really want gated asap but the zuul instance is a pretty busy one with limited node provider resources used across several tenants. The change is queued but waiting, there are other changes in waiting state across different pipelines and tenants. Would there be a way to promote that high prio change over every tenant/pipeline to ensure it's queued in its gate pipeline ASAP? Or would we need to just dequeue everything else to make way for it? | 15:28 |
| @clarkb:matrix.org | I think you need to dequeue other stuff. Another option would be to have a special pipeline with priority higher than everything else that gets things manually queued to it and then rely on that higher priority. But I don't think there is a way of assigning that to an arbitrary change | 15:29 |
| @mhuin:matrix.org | Okay, I'll read up about pipeline priorities, but I like the idea of having a special gate pipeline "in case of fire" if it does prioritize above every other tenant/pipeline for emergency stuff | 15:31 |
| @fungicide:matrix.org | yeah, promoting resets the git history/dependencies of all the other changes in the queue, so it's equivalen to dequeuing all changes, enqueuing your priority change, then enqueuing all the other changes again | 15:31 |
| @fungicide:matrix.org | it's not particularly magic | 15:31 |
| @mhuin:matrix.org | @fungi: and this is scoped to a pipeline/Tenant I guess | 15:32 |
| @fungicide:matrix.org | yes, if your change is appearing in multiple tenants and/or pipelines you'd have to explicitly promote each of them | 15:33 |
| @mhuin:matrix.org | pipeline priorities are relative to a tenant or across all of them? | 15:36 |
| @mhuin:matrix.org | although having 2 gate pipelines for a given project probably opens a big can of worms, and you're better off just promoting that change in the single gate pipeline | 15:37 |
| @clarkb:matrix.org | mhu: I think with nodepool pipeline priorities are global but I'm not sure off the top of myhead | 15:41 |
| @mhuin:matrix.org | well it was more of a thought experiment anyway | 15:42 |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: | 16:09 | |
| - [zuul/zuul] 964556: Update no_log in win_command and friends https://review.opendev.org/c/zuul/zuul/+/964556 | ||
| - [zuul/zuul] 964557: Add assertions about no_log and registered results https://review.opendev.org/c/zuul/zuul/+/964557 | ||
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Jan Gutter: [zuul/zuul] 963276: Fix ansible command plugin when using no_log https://review.opendev.org/c/zuul/zuul/+/963276 | 16:09 | |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 964556: Update no_log in win_command and friends https://review.opendev.org/c/zuul/zuul/+/964556 | 18:22 | |
| -@gerrit:opendev.org- Zuul merged on behalf of Jan Gutter: [zuul/zuul] 963276: Fix ansible command plugin when using no_log https://review.opendev.org/c/zuul/zuul/+/963276 | 18:22 | |
| @jim:acmegating.com | zuul-maint: how does this look for a zuul release: | 20:59 |
| commit fb2f7c6784c82dab9ab3c04c6a877db3ab3df9cb (HEAD -> master, tag: 13.0.1, origin/master, gerrit/master) | ||
| @clarkb:matrix.org | corvus: did you want to have opendev rollout the changes first? I know we don't cover windows but would cover against any regressions in the linux streaming | 21:10 |
| @clarkb:matrix.org | that said there are functional tests so may be worthwhile to just quickly get the update out | 21:10 |
| @clarkb:matrix.org | the commit and tag value look fine to me as long as we don't think we need that extra coverage first | 21:11 |
| @jim:acmegating.com | Clark: i think for this we should rely on the tests and not delay | 21:13 |
| @clarkb:matrix.org | ack | 21:19 |
| @fungicide:matrix.org | belated lgtm. thanks! | 22:00 |
| @jim:acmegating.com | images and announcement are out now https://lists.zuul-ci.org/archives/list/zuul-announce@lists.zuul-ci.org/thread/UJEL6DLYNEN7S4M66QWSC37VZYZ7WAM3/ | 22:10 |
| @fungicide:matrix.org | awesome | 22:14 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!