Expose the ability to set mozharness revision (as a distinct rev besides the used-build) in release promotion

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: Callek, Assigned: Callek)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Assignee)

Description

3 years ago
Created attachment 8723854 [details] [review]
[shipit] add mozharness_changeset

Rail expressed interest in having relman/us be able to set an alternate mozharness revision than what the CI build used for release promotion.

This allows us to change some of the automation without needing to change the actual CI build process. In cases of any config-change needs, etc.

This PR is based on rail's branch at https://github.com/rail/ship-it/tree/mozharness_changeset so r? to bhearsum.
Attachment #8723854 - Flags: review?(bhearsum)
(Assignee)

Comment 1

3 years ago
Created attachment 8723856 [details] [diff] [review]
[tools] make it a passed kwarg to releasetasks.
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #8723856 - Flags: review?(rail)
Attachment #8723856 - Flags: review?(rail) → review+
Attachment #8723854 - Flags: review?(bhearsum) → review+
(Assignee)

Comment 2

3 years ago
Created attachment 8724153 [details] [review]
[shipit] minor fix

Missed one thing.
Attachment #8724153 - Flags: review?(rail)
(Assignee)

Comment 3

3 years ago
fwiw deploying the code to ship-it dev required an apache restart, for the releaselists to expose the mh_changeset and thus not have broken UI.

(Theory is that we needed a new MySQL connection to expose the altered VIEW for `product_releases`)
Attachment #8724153 - Flags: review?(rail) → review+
Let's close this and address the releasetasks part in bug 1253361
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.