[CoT] Allow tasks with Github source to be mixed with their Mercurial equivalents
Categories
(Release Engineering :: Release Automation, defect)
Tracking
(Not tracked)
People
(Reporter: ahal, Assigned: ahal)
References
Details
Attachments
(2 external files)
There's a CoT check that requires that all tasks in the graph have the same metadata.source as the Decision task. This a good sensible check, but while we're migrating the Firefox repo to Github, this will no longer be the case. Some tasks will have a Mercurial metadata.source and others will have a Github one.
We need a way to allow certain Github repo + branch aliases to be allowed as a stand-in for their Mercurial counter-parts. E.g:
Task A -> hg.mozilla.org/integration/autoland
Task B -> github.com/mozilla-firefox/firefox/tree/autoland
Result -> Valid
Task A -> hg.mozilla.org/integration/autoland
Task B -> github.com/mozilla-firefox/firefox/tree/release
Result -> Invalid
We could query Lando to give us the real mapping, but then we add a runtime dependency on it. Anytime lando is down, signing tasks in pushes would fail for instance. Instead I propose we just add a temporary mapping in constants.py. We can remove it again once the migration is finished.
| Assignee | ||
Comment 1•1 month ago
|
||
Comment 2•1 month ago
|
||
Updated•1 month ago
|
Description
•