Customize a temporary branch for risky JS landing

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: bhackett, Assigned: jhford)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
Sometime in the next couple weeks the Jaegermonkey branch will merge to mozilla-central, and we will need a new repository which disables the JM branch features and pulls from mozilla-central regularly.  After the JM merge, this repository will need full tinderbox and nightly coverage, and will be used to ease pain and lower risk should we end up backing out the JM branch features in the next release cycle (more discussion in the 'Shipping Type Inference and Other "Irreversible" Changes' thread on moz-dev-planning).

After the JM merge we will not need tinderbox/nightly coverage for the JM branch, could maybe use those machines for the new repository.

Also, a generic name (mozilla-central-alternate or just mozilla-alternate) is good so that the repository can be used in the future in similar cases (testing m-c minus a large feature that may or may not end up getting backed out).
Brian, IMO, using one of the disposable branches for this might be your best and easiest options.

You can sign up for it for as long as you need it, and get RelEng to configure it differently if you need to. maple/cedar/birch/...etc

Though I have no strong standing in my opinion here, I just feel an additional repo setup for this is overkill.
(In reply to Brian Hackett from comment #0)
> Sometime in the next couple weeks the Jaegermonkey branch will merge to
> mozilla-central, and we will need a new repository which disables the JM
> branch features and pulls from mozilla-central regularly.  After the JM
> merge, this repository will need full tinderbox and nightly coverage, and
> will be used to ease pain and lower risk should we end up backing out the JM
> branch features in the next release cycle (more discussion in the 'Shipping
> Type Inference and Other "Irreversible" Changes' thread on moz-dev-planning).
> 
> After the JM merge we will not need tinderbox/nightly coverage for the JM
> branch, could maybe use those machines for the new repository.
 
Not sure what your understanding is of the infrastructure, but the machines are in a generic pool.  A machine that runs mozilla-central could also run jaegermonkey.

> Also, a generic name (mozilla-central-alternate or just mozilla-alternate)
> is good so that the repository can be used in the future in similar cases
> (testing m-c minus a large feature that may or may not end up getting backed
> out).

Lets follow Justin's suggestion in comment 1 and customize a temporary branch.  

https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches


When you have a list of requirements, please unassign yourself from the bug, which will cause this bug to go back into the triage queue and be triaged again.
Assignee: nobody → bhackett1024
Summary: Set up mozilla-central-alternate repository → Customize a temporary branch for risky JS landing
(Reporter)

Updated

7 years ago
Depends on: 679007
(Reporter)

Comment 3

7 years ago
OK, using a disposable branch sounds good.  I requested a reset on birch (bug 679007), once that is done the only additional requirement is that the branch get the same tinderbox coverage as the JaegerMonkey branch does now.
(Reporter)

Updated

7 years ago
Assignee: bhackett1024 → nobody
Created attachment 554221 [details] [diff] [review]
add the same coverage to birch that is on jaegermonkey
Assignee: nobody → jhford
Status: NEW → ASSIGNED
Attachment #554221 - Flags: review?(lsblakk)
Attachment #554221 - Flags: review?(aki)

Comment 5

7 years ago
Comment on attachment 554221 [details] [diff] [review]
add the same coverage to birch that is on jaegermonkey

birch already has remote-t* for talos on test-master01 :)
unneeded.
Attachment #554221 - Flags: review?(aki) → review-
Attachment #554221 - Flags: review?(lsblakk)
(In reply to Aki Sasaki [:aki] from comment #5)
> Comment on attachment 554221 [details] [diff] [review]
> add the same coverage to birch that is on jaegermonkey
> 
> birch already has remote-t* for talos on test-master01 :)
> unneeded.

This means that we have the same coverage on Jaegermonkey as birch

If you find something lacking, please reopen.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.