1568367 - Show partner & eme-free repack jobs on treeherder

Status: NEW

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

Description

[Nick Thomas [:nthomas] (UTC+12)]

Sometimes we have problems with partner repack tasks for releases but don't know because they are not shown on treeherder. mkaply has signed off on adding them the TH so that it is easier for releng/relman/sheriffs to notice failures.

For 68.0.1, the following kinds do not have a task.extra.treeherder dictionary:

release-eme-free-repack-beetmover
release-eme-free-repack-beetmover-checksums
release-eme-free-repack-repackage
release-eme-free-repack-repackage-signing
release-eme-free-repack-signing
release-partner-repack
release-partner-repack-beetmover
release-partner-repack-chunking-dummy
release-partner-repack-repackage
release-partner-repack-repackage-signing
release-partner-repack-signing

Bonus points for also including

release-early-tagging

and maybe

release-notify-promote
release-notify-started

but ignoring these

post-balrog-dummy
post-beetmover-checksums-dummy
post-beetmover-dummy
post-langpack-dummy

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

FTR, EME-free jobs are in the dependency tree for release-generate-checksums, but release-partner-* are not and do not block QA.

Comment 2

[Jordan Lund (:jlund)]

-> tag

I'll take a look at this during my releaseduty cycle. Probably next week.

Comment 3

[Tom Prince [:tomprince]]

Attachment: Bug 1568367: partner-treeherder

Comment 4

[Jordan Lund (:jlund)]

Tom has an initial patch here. It has likely bitrot'ed and it needs a bit more patching. This would be a good first bug for playing with release automation and taskgraph.

We need to verify that this captures all the partner eme tasks and includes treeherder metadata in the task definition.

Comment 5

[Jordan Lund (:jlund)]

Tom has an initial patch here. It has likely bitrot'ed and it needs a bit more patching. This would be a good first bug for playing with release automation and taskgraph.

We need to verify that this captures all the partner eme tasks and includes treeherder metadata in the task definition.

Comment 6

[Prashanth Pradeep]

Hi All, how do i get started to help resolve this task.

Comment 7

[Aki Sasaki (not active)]

Prashanth, sorry about the inactivity here.

Are you still looking at contributing? Most likely the first step would be to look at Tom's patch, learn how to run ./mach taskgraph (probably running taskgraph-gen and taskgraph-diff will help here), and start unbitrotting the patch.

Comment 8

[Leslie]

Hi my name is Leslie and I'm an Outreachy applicant. May I work on this bug?

Comment 9

[Aki Sasaki (not active)]

Hi Leslie,
Sure! Have you worked on any Firefox bugs before?
The steps in comment 7 are right. It looks like you've already contributed a phab patch, that's great!

Let me know if you want me to answer your questions here, or in Matrix #firefox-ci, or I can set up a Zoom call if you want to discuss the bug. I'm in the Pacific time zone.

Comment 10

[Mihai Tabara [:mtabara]⌚️GMT]

Hi Leslie - dropping a gentle touch-base here, are you still interested in working on this bug?

Comment 11

[Mihai Tabara [:mtabara]⌚️GMT]

Returning this to the pool. If still intersted, please let me know.

Comment 12

[Venkatesh Prabhu :vprabhu]

Hello. I would like to work on this. How can I get started?

Comment 13

[Aki Sasaki (not active)]

:vprabhu, most likely you want to grab https://bugzilla.mozilla.org/attachment.cgi?id=9123635 and unbitrot it, then push to try.
Have you worked with hg / mozilla-central / try before?

Comment 14

[Venkatesh Prabhu :vprabhu]

(In reply to Aki Sasaki [:aki] (he/him) (UTC-7) from comment #13)

:vprabhu, most likely you want to grab https://bugzilla.mozilla.org/attachment.cgi?id=9123635 and unbitrot it, then push to try.
Have you worked with hg / mozilla-central / try before?

I had worked long ago a bit but I don't remember much. Do you have any pointers to get started? (Sorry, I didn't get notified for this reply of yours. I will stay connected here. )

Comment 15

[Aki Sasaki (not active)]

https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html is a good quick start.

https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html , https://firefox-source-docs.mozilla.org/contributing/vcs/mercurial.html , and https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/ go a bit more in depth.

Once you get mozilla-unified cloned and set up with ./mach vcs-setup , you may be able to set up moz-phab and try moz-phab patch D61279 --apply-to here to download https://bugzilla.mozilla.org/attachment.cgi?id=9123635 and apply it to the tip of central. It will likely hit conflicts, which you can resolve. Alternately, you can look at the patch and edit the files it references directly. Afterwards, moz-phab submit will push that patch to phabricator.

Comment 16

[Venkatesh Prabhu :vprabhu]

Okay, working on it. Thanks.

Comment 17

[briannapatricia7]

hello, I am an outreachy applicant. kindly I request to work on this bug

Comment 18

[Geoff Brown [:gbrown]]

briannapatricia7 - Hi. Sorry for the lack of response here. Are you still interested in this bug? Let me know what you need to get started.