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

Status: RESOLVED FIXED

(Release Engineering :: Applications: Shipit, defect)

Description

[Justin Wood (:Callek)]

Attachment: [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.

Comment 1

[Justin Wood (:Callek)]

Attachment: [tools] make it a passed kwarg to releasetasks.

Comment 2

[Justin Wood (:Callek)]

Attachment: [shipit] minor fix

Missed one thing.

Comment 3

[Justin Wood (:Callek)]

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`)

Comment 4

[Rail Aliiev [:rail]]

Let's close this and address the releasetasks part in bug 1253361