Sheriffing/Uplift-Sim: Difference between revisions

No edit summary
No edit summary
 
(7 intermediate revisions by the same user not shown)
Line 3: Line 3:
The steps how to do this Simulations are documented here :
The steps how to do this Simulations are documented here :


> Have a m-c unified repo somehere
-> hg import the patches that you want like Early Beta/Late Beta
-> for commit on the last changeset use the try synatx that philor suggested
for as beta pushes
try: -b do -p all -u all[-10.6,-Windows XP] -t none --no-retry


* [[Sheriffing/Uplift-Sim/Bump-Trunk|Bump Version Numbers on trunk]]
for as dev-edtion :
* [[Sheriffing/Uplift-Sim/Trunk-Aurora|Trunk-> Aurora]]
try: -b o -p linux-devedition-nightly,linux64-devedition-nightly,macosx64,win32,win64 -u all[-10.6,-Windows XP] -t all[-10.6,-Windows XP]
* [[Sheriffing/Uplift-Sim/Trunk-Aurora-Nightly|Simulate use Aurora update channel like Aurora nightlies]]
* [[Sheriffing/Uplift-Sim/Trunk-Beta|Trunk to Beta]]
* [[Sheriffing/Uplift-Sim/Beta-Release]]
* [[Sheriffing/Uplift-Sim/Aurora-Beta|Aurora-Beta]]


-> Push to try (if you are not familiar with the try server [[ReleaseEngineering/TryServer|here]] is a good link to read)


Results for the Try runs are here :
The patches that contain the configurations changes are in [https://bugzilla.mozilla.org/show_bug.cgi?id=1280663  Bug 1280663]


{| class="wikitable"
Using the the first 2 patches of that bug gets you late beta - when you include the 3rd patch -> Early Beta
|-
 
! Date  !! Bump Trunk Version !! Trunk Aurora !! Trunk Aurora Nightly !! Trunk to Beta !! Beta-Release !! Aurora-Beta
And the last patch from the bug gets you Dev Edition.
|-
| 26-Jul-2016 || [http://%20https://treeherder.mozilla.org/#/jobs?repo=try&revision=75e7855c3fdd Try Results] || [https://treeherder.mozilla.org/#/jobs?repo=try&revision=f1e9009d0405 Try result] || [https://treeherder.mozilla.org/#/jobs?repo=try&revision=647fdd5d6b4f Try result] || [https://treeherder.mozilla.org/#/jobs?repo=try&revision=a70f533f790d try result] || Example || [https://treeherder.mozilla.org/#/jobs?repo=try&revision=30b58e394d05 Try Result] ||
|-
| Example || Example || Example || Example || Example || Example || Example ||
|-
| Example || Example || Example || Example || Example || Example || Example ||
|-
| Example || Example || Example || Example || Example || Example || Example ||
|-
| Example || Example || Example || Example || Example || Example || Example ||
|}

Latest revision as of 14:12, 22 June 2017

In order to prevent long Tree-Closures after Release Merge Day, Sheriffs are now doing regular simulations of Code Merges from like Trunk -> Aurora, Aurora -> Beta and Trunk -> Beta

The steps how to do this Simulations are documented here :

> Have a m-c unified repo somehere -> hg import the patches that you want like Early Beta/Late Beta -> for commit on the last changeset use the try synatx that philor suggested

for as beta pushes
try: -b do -p all -u all[-10.6,-Windows XP] -t none --no-retry 
for as dev-edtion :
try: -b o -p linux-devedition-nightly,linux64-devedition-nightly,macosx64,win32,win64 -u all[-10.6,-Windows XP] -t all[-10.6,-Windows XP]

-> Push to try (if you are not familiar with the try server here is a good link to read)

The patches that contain the configurations changes are in Bug 1280663

Using the the first 2 patches of that bug gets you late beta - when you include the 3rd patch -> Early Beta

And the last patch from the bug gets you Dev Edition.