Closed
Bug 854460
Opened 12 years ago
Closed 12 years ago
Turn on Jetpack tests on all trees that can feed into m-c
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mossop, Assigned: armenzg)
References
Details
Attachments
(1 file)
2.29 KB,
patch
|
mozilla
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
We want to unhide jetpack tests everywhere that can be used for Firefox development, but some of those trees don't even have it turned on yet. fx-team and services-central definitely don't have it. Looks like the disposable project branches don't have it either. I'm hoping releng have a more definitive list on what trees this actually should cover.
Comment 1•12 years ago
|
||
What you actually want to do is give them the list of trees where you don't want it, which is probably something much shorter, like "not mozilla-beta, mozilla-release, mozilla-b2g* or mozilla-esr17," unless it's actually "not mozilla-b2g* or mozilla-esr17, and ride the 21 train down to beta and release."
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → armenzg
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: catlee
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #729618 -
Flags: review?(aki)
Updated•12 years ago
|
Attachment #729618 -
Flags: review?(aki) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Comment on attachment 729618 [details] [diff] [review]
add jetpack to all branches except m-b, m-r and older stable trees
6b4c6e297707
This change will be live on our next reconfiguration (which should happen this week). Depends on when buildduty runs it.
Attachment #729618 -
Flags: checked-in+
Assignee | ||
Updated•12 years ago
|
Priority: -- → P3
Whiteboard: waiting on reconfiguration of masters
Assignee | ||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: waiting on reconfiguration of masters
Comment 5•12 years ago
|
||
Armen, the patch from this bug marked as "MERGE DAY once FF21 merges into a branch remove it from this list", but it's not enabled for betas. Should I proceed with uplifting it or there is a reason why it's not enabled on beta?
Blocks: 842864
Flags: needinfo?(armenzg)
Assignee | ||
Comment 6•12 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #5)
> Armen, the patch from this bug marked as "MERGE DAY once FF21 merges into a
> branch remove it from this list", but it's not enabled for betas. Should I
> proceed with uplifting it or there is a reason why it's not enabled on beta?
With the new model we need to enable it as it gets into each different release tree.
Thanks rail!
Flags: needinfo?(armenzg)
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•