Closed Bug 1492485 Opened 6 years ago Closed 6 years ago

set up birch to follow mozilla-central to enable declarative artifacts testing

Categories

(Release Engineering :: Release Automation: Uploading, defect)

Product:
Release Engineering
Component:
Release Automation: Uploading
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mtabara, Assigned: bhearsum)

References

Details

Sounds like birch[1] is not used by anyone right now so we can steal it to develop declarative artifacts stuff. Reason for this is that beetmover in-tree transforms changes will be very disruptive at the beginning so we need a different project branch than maple, where various folks from RelEng still test stuff and expect rather green graphs. 

This bug is to track the reset of birch (formerly used for RC tcmigration? I think?) in order it to follow mozilla-central. Something like our formerly known "date" project branch.

[1]: https://hg.mozilla.org/projects/birch
Ben is taking care of this, thanks!
Assignee: nobody → bhearsum
I think this is done now. It was already most of the way set-up in https://bugzilla.mozilla.org/show_bug.cgi?id=1426132 - I just merged central and fixed a small bug that I found that caused the decision task to fail (https://phabricator.services.mozilla.com/D6274).
I'll just note for posterity that the decision task failing is probably only for that push, because it includes so many changesets, and the subsequent pushes probably would have worked even without the change. (But the fix is reasonable in any case).
As far as we can tell, this is done! It's difficult to be certain until we start running tests, but we can file new bugs for any follow-up issues.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
https://hg.mozilla.org/projects/birch and https://treeherder.mozilla.org/#/jobs?repo=birch look good, I think we're good here. Thanks :bhearsum!
You need to log in before you can comment on or make changes to this bug.