stop tagging mozharness repo for releases

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: bhearsum, Assigned: bhearsum)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Once all of the release jobs use in-tree Mozharness we can stop tagging the old repo.
Created attachment 8639282 [details] [diff] [review]
stop tagging mozharness as part of release automation

I did some grepping and the only reference to it are in tagging, and erroneous ones caused by bug 1187894.
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #8639282 - Flags: review?(rail)
Comment on attachment 8639282 [details] [diff] [review]
stop tagging mozharness as part of release automation

\o/
Attachment #8639282 - Flags: review?(rail) → review+
(Assignee)

Updated

3 years ago
Attachment #8639282 - Flags: checked-in+
(Assignee)

Updated

3 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
How does this work with releases ? I see the likes of 'hg update -r FENNEC_40_0b4_RELEASE' in slightly old Android 'en-US' and l10n jobs. In more recent jobs we've switched to the mozharness bundles ?

bash -c 'python archiver_client.py mozharness --repo releases/mozilla-beta --tag FENNEC_40_0b8_RELEASE --destination scripts --debug'

IIRC desktop jobs are doing that too, even if almost all or all of them don't need it.

No bustage in 40.0b8 build1, but the change was only on default then.

Comment 4

3 years ago
(In reply to Nick Thomas [:nthomas] from comment #3)
> How does this work with releases ? I see the likes of 'hg update -r
> FENNEC_40_0b4_RELEASE' in slightly old Android 'en-US' and l10n jobs. In
> more recent jobs we've switched to the mozharness bundles ?

in the old way, we would tag the mozharness repo *and* the gecko repo with the same tag. Now in-tree mh just uses the gecko tag.

> 
> bash -c 'python archiver_client.py mozharness --repo releases/mozilla-beta
> --tag FENNEC_40_0b8_RELEASE --destination scripts --debug'

in the above example, archiver will look up the m-b rev based on the tag and grab a copy of mh that way.

so that is why we don't need any additional new tags with in-tree mh and also why we can stop tagging the old mh repo.

Does that clear up your question? Or did I misunderstand what you were asking?
Thanks for the explanation. I must have swapped places with a me from an alternate universe, and they'd forgotten everything about this change.
You need to log in before you can comment on or make changes to this bug.