| -@gerrit:opendev.org- Dong Zhang proposed: [zuul/zuul] 920322: WIP: Debug web error in new version https://review.opendev.org/c/zuul/zuul/+/920322 | 08:13 | |
| @f2ked:matrix.org | I would like to test zuul+nodepool on an existing gerrit+jenkins. I'm thinking I could just make a `check` only pipeline with only a `trigger.gerrit.[event].comment` entry and `success` and `failure` log something, but don't actually report back to gerrit? 🧵 | 12:43 |
|---|---|---|
| @f2ked:matrix.org | I can't be the first to attempt something like this, any tips or tutorials around? | 12:43 |
| @fungicide:matrix.org | > <@f2ked:matrix.org> I would like to test zuul+nodepool on an existing gerrit+jenkins. I'm thinking I could just make a `check` only pipeline with only a `trigger.gerrit.[event].comment` entry and `success` and `failure` log something, but don't actually report back to gerrit? 🧵 | 13:46 |
| https://zuul-ci.org/docs/zuul/latest/config/pipeline.html#attr-pipeline.success ... `pipeline.success` is documented as being optional, `pipeline.failure` doesn't say it's optional but i believe it is as well, so you should be able to just leave those out of your pipeline definition and rely on zuul's dashboard to see build results | ||
| @fungicide:matrix.org | the main challenge is, i think, that you can't make zuul refrain from leaving comments on changes which would introduce job configuration errors | 13:47 |
| @fungicide:matrix.org | otherwise it will refrain from commenting and voting on changes with that pipeline | 13:47 |
| @f2ked:matrix.org | leaving a comment without a vote would actually be nice | 14:30 |
| @f2ked:matrix.org | looking at https://zuul-ci.org/docs/zuul/latest/drivers/gerrit.html#reference-pipelines-configuration | 14:34 |
| the `release` and `tag` pipeline do not have `success` or `failure` | ||
| @f2ked:matrix.org | `deploy` and `promote` has | 14:35 |
| ``` | ||
| success: | ||
| gerrit: {} | ||
| failure: | ||
| gerrit: {} | ||
| ``` | ||
| @f2ked:matrix.org | * `deploy` and `promote` has | 14:35 |
| ``` | ||
| success: | ||
| gerrit: {} | ||
| failure: | ||
| gerrit: {} | ||
| ``` | ||
| I wonder what the difference is? | ||
| @f2ked:matrix.org | Or I could set `Verified: 0`? | 14:41 |
| @f2ked:matrix.org | hmm.. I've been using threads on this matrix channel, but it does not seem popular. Should I refrain from using them? | 15:02 |
| @jim:acmegating.com | indeed several of us prefer the non-threaded form of interaction (whether due to client implementations or otherwise) | 15:18 |
| @fungicide:matrix.org | f2ked: pipelines triggered from gerrit's ref-updated events don't have any change context, only git references, so zuul wouldn't know what change to comment on for success and failure results. you can still couple them with other reporters like smtp or mqtt | 15:43 |
| @fungicide:matrix.org | f2ked: or just query the build or buildset views in the zuul dashboard | 15:44 |
| @f2ked:matrix.org | I'm actually hoping to `trigger.[event].comment-added`, but I'm fine with leaving no comment is response. | 15:48 |
| thanks for the help | ||
| @fungicide:matrix.org | sure, i was just explaining why the release and tag pipeline examples you looked at didn't include calls to any gerrit reporter | 16:08 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!