1533939 - clean up treeherder release symbols and bundle all tasks under a release identifier

Status: RESOLVED INCOMPLETE

(Release Engineering :: Release Automation: Other, enhancement)

Description

[Jordan Lund (:jlund)]

Currently we separate some release tasks. Examples: UV(), and langpack(), BM(), and BMcslang()

Some of them make sense, others like BMcslang are not intuitive. The other issue is that these are scattered among other per-checkin tasks.

In an effort to have sheriffs monitor and star release tasks, it would be good to help clean this up.

e.g. bundle all release tasks under release() and then clean up the symbols so we don't have stuff like (N1)[https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&fromchange=b15620c1831001bcd8db5b3dd678173beda0076c&selectedJob=232466785] which represents a macosx64 opt beetmover checksums for language packs release-beetmover-signed-langpacks-checksums-macosx64-1/opt job.

The other option is to bundle by graph. So relpro() relpush() relship().

Naming is hard. There is no perfect way but I think it's worth cleaning up a bit and making it clear what are release tasks vs per-checkin builds/tests

Comment 1

[Tom Prince [:tomprince]]

One option would be to move these all to separate platforms.

Or perhaps we could add a release tier to treeherder.

Comment 2

[Jordan Lund (:jlund)]

I think a separate tier has justification here. It would be the quickest way to highlight release tasks in Treeherder.

I think we would still want to clean up release grouping, job names, and symbols.

Comment 3

[Tom Prince [:tomprince]]

Attachment: Bug 1533939: [release] Move beta-channel RC tasks to release platform in treeherder; r?Callek

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/8c0a7e7ccb50
[release] Move beta-channel RC tasks to release platform in treeherder; r=Callek

Comment 5

[Andrei Ciure[:aciure]]

https://hg.mozilla.org/mozilla-central/rev/8c0a7e7ccb50

Comment 6

[Jordan Lund (:jlund)]

going to close this for now. we can fix up symbols and names in the future if we find it useful. the real priority to fix was comment 4