Closed Bug 1251468 Opened 4 years ago Closed 4 years ago

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

Categories

(Release Engineering :: Applications: Shipit (backend), defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: Callek)

References

Details

Attachments

(3 files)

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: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #8723856 - Flags: review?(rail)
Attachment #8723856 - Flags: review?(rail) → review+
Attachment #8723854 - Flags: review?(bhearsum) → review+
Attached file [shipit] minor fix
Missed one thing.
Attachment #8724153 - Flags: review?(rail)
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+
Blocks: 1253361
Let's close this and address the releasetasks part in bug 1253361
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.