| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 929978: Fix console log stream delay on idempotent command https://review.opendev.org/c/zuul/zuul/+/929978 | 00:35 | |
| @gchristensen:matrix.org | > <@fungicide:matrix.org> to be clear, that was approved roughly a month ago, so https://zuul-ci.org/docs/zuul/latest/developer/specs/zuul-workload-identity-federation.html is a better url for it at this point | 00:36 |
|---|---|---|
| Thank you! I should come clean: I used my explainer above as an analogy of what I'm actually doing. Which is my company makes FlakeHub, a platform for Nix flakes. We support logging in with GitHub Actions and GitLab Pipelines (and soon Semaphore and CircleCI), and want to also support Zuul users. Thank you for the links, we're going to dig in :). | ||
| -@gerrit:opendev.org- Simon Westphahl proposed: | 06:11 | |
| - [zuul/zuul] 933086: Allow waiting for tree cache ltime sync point https://review.opendev.org/c/zuul/zuul/+/933086 | ||
| - [zuul/zuul] 929273: Add support for 'min-ready' provider nodes https://review.opendev.org/c/zuul/zuul/+/929273 | ||
| - [zuul/zuul] 931779: Implement 'max-ready-age' handling https://review.opendev.org/c/zuul/zuul/+/931779 | ||
| - [zuul/zuul] 931780: Implement re-use of ready nodes w/o request https://review.opendev.org/c/zuul/zuul/+/931780 | ||
| - [zuul/zuul] 932170: Store state time for provider nodes https://review.opendev.org/c/zuul/zuul/+/932170 | ||
| - [zuul/zuul] 932179: Only expire nodes when no pending layout update https://review.opendev.org/c/zuul/zuul/+/932179 | ||
| @kiransurya:matrix.org | I want to fetch all the successful commits that were made during periodic pipeline. How can I make it? | 06:17 |
| @kiransurya:matrix.org | * I want to fetch all the successful commits that were made during periodic pipeline for each release. How can I make it? | 06:40 |
| -@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 933215: Clarify retry(-limit) build status docs https://review.opendev.org/c/zuul/zuul/+/933215 | 08:46 | |
| -@gerrit:opendev.org- Benjamin Schanzel proposed: [zuul/zuul] 933085: zuul-web: Simplify tenant list https://review.opendev.org/c/zuul/zuul/+/933085 | 09:03 | |
| -@gerrit:opendev.org- Benjamin Schanzel proposed: [zuul/zuul] 933085: zuul-web: Simplify tenant list https://review.opendev.org/c/zuul/zuul/+/933085 | 09:08 | |
| @blart_versenwald_3:matrix.org | Is it possible to get a list of all jobs that have used "my" job as parent ? Basically, what I want is a list of all jobs (and in what projects) depend on my job. | 11:35 |
| @jangutter:matrix.org | blart_versenwald_3: sort-of like this? https://zuul.opendev.org/t/openstack/jobs | 12:21 |
| @blart_versenwald_3:matrix.org | > <@jangutter:matrix.org> blart_versenwald_3: sort-of like this? https://zuul.opendev.org/t/openstack/jobs | 12:29 |
| Ahh, yeah of course! My list was so huge that I wanted to filter on my job, but that also removed all children due to filter. | ||
| Thanks! :) | ||
| My next step would be to list the history of each of those children to understand when in time they were executed. There is a second part that I did not mention earlier, and that is that I want to know when the children last were using my job. Is there an easy way to find out this also? | ||
| @jangutter:matrix.org | As for the list of jobs, I think you can construct the tree from the json API: | 12:30 |
| ``` | ||
| # Just list the direct descendants of the `kolla-ansible-base` job, you'll need to iterate for the decendants of them... | ||
| curl https://zuul.opendev.org/api/tenant/openstack/jobs | jq '.[] | select(.variants[0].parent == "kolla-ansible-base") | .name' | ||
| ``` | ||
| @jangutter:matrix.org | blart_versenwald_3: I think you can use the `builds` api to query for the most recent builds of that job, kinda like how you would do it in the UI, look at https://zuul.opendev.org/openapi for more details. | 12:33 |
| For example, https://zuul.openstack.org/builds?job_name=kolla-ansible-rocky9-podman&skip=0 is an easy way to check when last the job has run. You can convert that to an api call for a machine parseable one. | ||
| @blart_versenwald_3:matrix.org | > <@jangutter:matrix.org> blart_versenwald_3: I think you can use the `builds` api to query for the most recent builds of that job, kinda like how you would do it in the UI, look at https://zuul.opendev.org/openapi for more details. | 12:37 |
| > | ||
| > For example, https://zuul.openstack.org/builds?job_name=kolla-ansible-rocky9-podman&skip=0 is an easy way to check when last the job has run. You can convert that to an api call for a machine parseable one. | ||
| Thanks jangutter ! | ||
| @jangutter:matrix.org | blart_versenwald_3: I'm glossing over things like job variants of course - technically a job can switch inheritance between runs, but my assumption is you're looking for something useful more than being 100% pedantic | 12:38 |
| @blart_versenwald_3:matrix.org | > <@jangutter:matrix.org> blart_versenwald_3: I'm glossing over things like job variants of course - technically a job can switch inheritance between runs, but my assumption is you're looking for something useful more than being 100% pedantic | 12:41 |
| Let's say that a job have switched parent from my job to another. Would it still be listed under my job in https://zuul.opendev.org/t/openstack/jobs ? | ||
| However in this case I do not think it is a big problem, I can always manually inspect if that is the case (not that many children) | ||
| @jangutter:matrix.org | blart_versenwald_3: I think `jobs` only lists the _current_ config that Zuul has loaded on each branch it's listening to there. For example if you propose a new job in `check` it won't show up there, once it's merged to a branch, it will show. So if you change a jobs inheritance, and it's merged, `jobs` won't list the historical version of it, _unless you've kept it on a branch_. | 12:45 |
| @jim:acmegating.com | blart_versenwald_3: the only way to find that out historically would be to look at the inventory.yaml file if you saved it on the log server. that includes a variable called "_inheritance_path" which would list your job if it inherited from it. | 12:46 |
| @jim:acmegating.com | * blart_versenwald_3: the only way to find that out historically would be to look at the inventory.yaml file if you saved it with the job logs. that includes a variable called "\_inheritance\_path" which would list your job if it inherited from it. | 12:46 |
| -@gerrit:opendev.org- Simon Westphahl proposed on behalf of Tobias Henkel: [zuul/zuul] 756077: Increase merge retries and delays in between https://review.opendev.org/c/zuul/zuul/+/756077 | 12:46 | |
| @jangutter:matrix.org | corvus: Nice, that would be the 100% accurate way, scanning the builds individually. | 12:50 |
| @jim:acmegating.com | but potentially slow and intensive, depending on how much you can narrow it down | 12:51 |
| @jim:acmegating.com | example: https://zuul.openstack.org/build/c2aaab7414d44a1bba73d46e0574810d/log/zuul-info/inventory.yaml#100 | 12:51 |
| @jim:acmegating.com | btw, that's not something we consider a stable api; that's a human debugging variable and the string format there is subject to change; but it'll probably stay there until we define a more stable api for that information. anyway, good enough for this task i think. | 12:52 |
| @jangutter:matrix.org | Yeah, in the rare case where "go to the audit logs" is needed above "let's hunt down 99% of the things we need to fix" | 12:52 |
| @blart_versenwald_3:matrix.org | Thank you jangutter and corvus I have what I need! | 12:58 |
| @yodakv:matrix.org | > <@dfajfer:fsfe.org> did you laready submit a change? | 15:50 |
| Yep, please review it here : https://review.opendev.org/c/zuul/nodepool/+/933030 | ||
| On a first step would great if Azure driver to support Spot VM. | ||
| @yodakv:matrix.org | > <@dfajfer:fsfe.org> did you laready submit a change? | 15:50 |
| * Yep, please review it here : https://review.opendev.org/c/zuul/nodepool/+/933030 | ||
| On a first step would great if Azure driver support Spot VM. | ||
| -@gerrit:opendev.org- Zuul merged on behalf of Clark Boylan: [zuul/nodepool] 933162: Bump dib up to 3.36.0 or newer https://review.opendev.org/c/zuul/nodepool/+/933162 | 16:31 | |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 933166: Simplify stream test_command https://review.opendev.org/c/zuul/zuul/+/933166 | 18:04 | |
| -@gerrit:opendev.org- Joseph Kostreva proposed: [zuul/zuul] 923183: Add commentable_files variable to GerritChange https://review.opendev.org/c/zuul/zuul/+/923183 | 19:40 | |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Benjamin Schanzel: [zuul/zuul] 933085: zuul-web: Simplify tenant list https://review.opendev.org/c/zuul/zuul/+/933085 | 20:02 | |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: | 21:13 | |
| - [zuul/zuul] 933065: Re-add volume attributes to aws driver https://review.opendev.org/c/zuul/zuul/+/933065 | ||
| - [zuul/zuul] 933374: Fix openstack region handling https://review.opendev.org/c/zuul/zuul/+/933374 | ||
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 933377: Launcher: fix deleting servers https://review.opendev.org/c/zuul/zuul/+/933377 | 22:16 | |
| -@gerrit:opendev.org- Zuul merged on behalf of Simon Westphahl: [zuul/zuul] 933086: Allow waiting for tree cache ltime sync point https://review.opendev.org/c/zuul/zuul/+/933086 | 23:37 | |
| -@gerrit:opendev.org- Zuul merged on behalf of Simon Westphahl: | 23:41 | |
| - [zuul/zuul] 929273: Add support for 'min-ready' provider nodes https://review.opendev.org/c/zuul/zuul/+/929273 | ||
| - [zuul/zuul] 931779: Implement 'max-ready-age' handling https://review.opendev.org/c/zuul/zuul/+/931779 | ||
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!