-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 900489: Thin the workspace repo clone https://review.opendev.org/c/zuul/zuul/+/900489 | 00:06 | |
-@gerrit:opendev.org- Simon Westphahl proposed: [zuul/nodepool] 900512: Ignore unrelated error labels in request handler https://review.opendev.org/c/zuul/nodepool/+/900512 | 10:39 | |
-@gerrit:opendev.org- Simon Westphahl proposed: [zuul/nodepool] 900512: Ignore unrelated error labels in request handler https://review.opendev.org/c/zuul/nodepool/+/900512 | 10:40 | |
-@gerrit:opendev.org- Simon Westphahl proposed: [zuul/nodepool] 900512: Ignore unrelated error labels in request handler https://review.opendev.org/c/zuul/nodepool/+/900512 | 13:03 | |
@noonedeadpunk:matrix.org | Hey there! I was wondering how I can make 1 job to run only when another one is finished. As I thought it's quite trivial to do with requires/provides but I see how these 2 launch at same time (at least in debug pipeline) | 15:25 |
---|---|---|
@noonedeadpunk:matrix.org | Or that's exactly because of independent pipeline where requires/provides doesn't have any effect? | 15:26 |
@noonedeadpunk:matrix.org | So my usecase is: I have job A that makes general post-merge things, which should be always executed. And then I have a job B that must make adjustments after A in case some specific files were modified | 15:27 |
@noonedeadpunk:matrix.org | So I define more specific `files` for B and tried to set A `provides: basic-promote` and then B `requires: basic-promote` and expected that B will be in queue until A is fully finished | 15:28 |
@noonedeadpunk:matrix.org | But kinda wonder if that could be used within same project or that's only cross-project.... | 15:29 |
@noonedeadpunk:matrix.org | Or should I use `hold-following-changes` for that? | 15:30 |
@noonedeadpunk:matrix.org | That looks even more cross-project focused though... | 15:31 |
@noonedeadpunk:matrix.org | Lol somehow missed `dependencies` | 15:32 |
@noonedeadpunk:matrix.org | disregard me:) | 15:34 |
@fungicide:matrix.org | Dmitriy Rabotyagov: yes, dependencies are what you want for sequencing jobs within a buildset, provides/requires is more useful for relationships between builds that may be in different buildsets entirely | 16:38 |
@clarkb:matrix.org | The spec for improving circular dependency handling in zuul also as a side effect should simplify some of this | 16:42 |
@clarkb:matrix.org | though maybe not this particular case | 16:42 |
@noonedeadpunk:matrix.org | Yeah, dependencies were exactly what I needed, was just blind to find them in doc... | 16:43 |
@noonedeadpunk:matrix.org | And writing up a question opened my eyes regardless I was looking for it for an hour before... | 16:44 |
@noonedeadpunk:matrix.org | * And writing up a question opened my eyes regardless I was looking for it already for an hour... | 16:44 |
-@gerrit:opendev.org- Zuul merged on behalf of Simon Westphahl: [zuul/nodepool] 900512: Ignore unrelated error labels in request handler https://review.opendev.org/c/zuul/nodepool/+/900512 | 20:54 | |
-@gerrit:opendev.org- Zuul merged on behalf of Simon Westphahl: [zuul/zuul] 896921: Improve error reporting for circular dependencies https://review.opendev.org/c/zuul/zuul/+/896921 | 21:03 | |
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 900489: Thin the workspace repo clone https://review.opendev.org/c/zuul/zuul/+/900489 | 23:22 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!