| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 922359: Avoid exception when no buildset files https://review.opendev.org/c/zuul/zuul/+/922359 | 00:56 | |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/nodepool] 922242: Continue trying uploads for other providers after failure https://review.opendev.org/c/zuul/nodepool/+/922242 | 06:31 | |
| -@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 922310: Add ZKObject-based launcher API https://review.opendev.org/c/zuul/zuul/+/922310 | 11:04 | |
| -@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 922310: Add ZKObject-based launcher API https://review.opendev.org/c/zuul/zuul/+/922310 | 11:31 | |
| -@gerrit:opendev.org- Benedikt Löffler proposed: [zuul/nodepool] 922403: Don't delete snapshot from import-snapshot tasks https://review.opendev.org/c/zuul/nodepool/+/922403 | 14:43 | |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Simon Westphahl: | 16:41 | |
| - [zuul/zuul] 921949: Add basic zuul-launcher client/server skeleton https://review.opendev.org/c/zuul/zuul/+/921949 | ||
| - [zuul/zuul] 922019: Properly sort imports in model.py https://review.opendev.org/c/zuul/zuul/+/922019 | ||
| - [zuul/zuul] 922310: Add ZKObject-based launcher API https://review.opendev.org/c/zuul/zuul/+/922310 | ||
| @jkkadgar:matrix.org | In the following scenario: Change A is reviewed, gated and merged into a repository. This change includes an update to a job that runs in the post pipeline. When the post pipeline runs, the updates to the job are not included in the build execution. It shows the correct Old and New revisions however. Is this expected behavior? Should I be using a different pipeline? | 17:28 |
|---|---|---|
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: | 22:08 | |
| - [zuul/zuul] 922433: Add ability to fail tests if tracebacks appear in logs https://review.opendev.org/c/zuul/zuul/+/922433 | ||
| - [zuul/zuul] 922434: Handle some TemplateNotFoundErrors https://review.opendev.org/c/zuul/zuul/+/922434 | ||
| - [zuul/zuul] 922435: Don't log tracebacks on malformed JSON error https://review.opendev.org/c/zuul/zuul/+/922435 | ||
| - [zuul/zuul] 922436: Mark mqtt test exception as okay https://review.opendev.org/c/zuul/zuul/+/922436 | ||
| @clarkb:matrix.org | > <@jkkadgar:matrix.org> In the following scenario: Change A is reviewed, gated and merged into a repository. This change includes an update to a job that runs in the post pipeline. When the post pipeline runs, the updates to the job are not included in the build execution. It shows the correct Old and New revisions however. Is this expected behavior? Should I be using a different pipeline? | 22:52 |
| I feel like that scenario generally works for us. Perhaps it has to do with your triggers? For example with Gerrit you can trigger post merge jobs on ref updated and change merged events. Maybe the difference is realted to the difference of those events? | ||
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!