Closed
Bug 860588
Opened 13 years ago
Closed 13 years ago
reset birch and cypress twigs in advance of the b2g workweek
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Unassigned)
References
Details
Summary of lots of emails + inperson discussions.
In preparation for next week's b2g workweek, I've reserved the birch + cypress branches. Please:
1) reset both of these repos to tip of m-c
2) mark these trees closed on tbpl.m.o
3) configure birch to run all builds+tests that mozilla-inbound does.
4) configure cypress to run only linux, b2g builds+tests. If we find we are better served by running all like mozilla-inbound, we can revisit.
5) raise the priority of birch+cypress above all other branches, but still below releases.
Comment 1•13 years ago
|
||
Can we keep it to just birch? In the thread we did not want to use the multi inbound approach.
Comment 2•13 years ago
|
||
I hear rumors of wanting periodic PGO rather than on-push, too.
Comment 3•13 years ago
|
||
More suggestions:
Run debug builds only the ec2 builders (ie Linux/Linux64). We'll want some leak checking ability, but all platforms is probably redundant, especially with semi-frequent merges to m-c.
Don't run checktests on OSX and Windows (all builds) to speed up the turnaround time. Consider disabling checktests on Linux/Linux64 desktop B2G builds as well.
| Reporter | ||
Comment 4•13 years ago
|
||
(In reply to Armen Zambrano G. [:armenzg] from comment #1)
> Can we keep it to just birch? In the thread we did not want to use the multi
> inbound approach.
Discussions continue, but meanwhile, lets setup both, so we have both ready for Monday, regardless of what we decide in the meanwhile.
Comment 5•13 years ago
|
||
I think this is done.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 6•13 years ago
|
||
Just had a thought - do we want unagi engineering builds (ala bug 820594/bug 848282) on these branches?
Comment 7•13 years ago
|
||
I was thinking about that earlier today too, but I don't think it's necessary. My assumption is that people will continue to use builds off m-c or more likely b2g18 as usual next week, so we only need to maintain enough coverage on birch to make sure we don't merge any bustage over to m-c.
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
| Assignee | ||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•