Last modified: 2014-05-20 14:49:51 UTC
It would be clearer if jenkins-bot's comments on gerrit changes named the pipeline involved, particularly when a change triggers multiple jobs. For example a branch commit that you immediately +2, such as https://gerrit.wikimedia.org/r/#/c/70910/ , seems to generates an initial check-in job, a "+2d-so-maybe-merge" job, and a post-merge doxgen job. jenkins-bot Patch Set 1: Verified+2 Build succeeded. - … jenkins-bot Patch Set 1: -Verified Starting gate-and-submit … jenkins-bot Change has been successfully merged into the git repository. jenkins-bot Patch Set 1: Verified+2 Build succeeded. - … jenkins-bot Patch Set 1: Build failed. - … It's hard to tell these jobs apart, hard to tell whether the "Starting gate-and-submit" succeeded/failed/continues, and the '-' is a mystery. The workaround is to expand the comments and look at the group of CI tasks run to infer what kind of job succeeded or failed; or be intimately familiar with all the Zuul pipelines. This seems better: jenkins-bot Patch Set n: <pipeline name> build [succeeded.|FAILED!] where I think from https://integration.wikimedia.org/zuul/ the pipeline names are <check-only check-voter gate gate-and-submit gate-silent post postmerge publish test>. (BTW the last comment in the example is doxygen failing on a branch, bug 50325)
This bug report is a follow up to a conversation I had with S on IRC. It is indeed confusing to users when jenkins-bot 'spam' comments on a bug, you barely know what has been tested. Adding the pipeline name in the message would indeed make it easier to track what is going on.
This can be done in the layout.yaml configuration, each pipeline message can be overridden with 'failure-message' and 'success-message' statements.
Made possible with Zuul change https://review.openstack.org/#/c/19677/
Change 107570 had a related patch set uploaded by Hashar: explicitly define success/failure messages https://gerrit.wikimedia.org/r/107570
Change 107570 merged by jenkins-bot: explicitly define success/failure messages https://gerrit.wikimedia.org/r/107570
We have upgraded Zuul last week. Gerrit change #107570 introduces default success/failures messages to all our pipelines. Anyone can thus tweak them as needed.
Change 134098 had a related patch set uploaded by Hashar: Report pipeline name in build status message https://gerrit.wikimedia.org/r/134098
Change 134098 merged by jenkins-bot: Report pipeline name in build status message https://gerrit.wikimedia.org/r/134098
Change deployed and Zuul reloaded. We can tweak the message latter on since good placeholders are already in place.
