https://bugzilla.wikimedia.org/show_bug.cgi?id=50327
Web browser: ---
Bug ID: 50327
Summary: Jenkins jobs in gerrit aren't named
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: Continuous integration
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
Classification: Unclassified
Mobile Platform: ---
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)
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
