Sheriffing/How To/Beta simulations: Difference between revisions

m
increased version numbers (Nightly = 146, Beta = 145)
m (increased version numbers (Nightly = 145, Beta = 144))
m (increased version numbers (Nightly = 146, Beta = 145))
Line 29: Line 29:
**<code>git checkout main</code> - needed only if you didn't import/backout anything
**<code>git checkout main</code> - needed only if you didn't import/backout anything
**<code>git pull</code> - needed only if you didn't import/backout anything
**<code>git pull</code> - needed only if you didn't import/backout anything
**<code>./mach try release -v 145.0b1 --tasks release-sim --migration main-to-beta</code> <span style="color:#FF0000">'''If not all the jobs shall run (e.g. to verify a test fix), append <code>--stage-changes</code> to the command, <code>git commit -a -m "Early beta sim"</code> and select the jobs with <code>./mach try chooser --no-artifact</code>'''</span>
**<code>./mach try release -v 146.0b1 --tasks release-sim --migration main-to-beta</code> <span style="color:#FF0000">'''If not all the jobs shall run (e.g. to verify a test fix), append <code>--stage-changes</code> to the command, <code>git commit -a -m "Early beta sim"</code> and select the jobs with <code>./mach try chooser --no-artifact</code>'''</span>
***'''-v 145.0b1''': Sets the version number to use in the beta simulation. <span style="color:#FF0000">'''Replace "145" with the version number mention in the beta simulation document.'''</span>
***'''-v 146.0b1''': Sets the version number to use in the beta simulation. <span style="color:#FF0000">'''Replace "146" with the version number mention in the beta simulation document.'''</span>
***'''--tasks release-sim''': Activates the tasks which shall run for beta simulations to get scheduled.
***'''--tasks release-sim''': Activates the tasks which shall run for beta simulations to get scheduled.
***'''--migration main-to-beta''': Activates modification of the configuration to switch from central to beta.
***'''--migration main-to-beta''': Activates modification of the configuration to switch from central to beta.
Line 39: Line 39:
== TRUNK AS LATE BETA ==
== TRUNK AS LATE BETA ==
To create a central-as-late-beta simulation, go to the console and use the following commands:
To create a central-as-late-beta simulation, go to the console and use the following commands:
*<code>./mach try release -v 145.0b12 --tasks release-sim --migration main-to-beta --migration early-to-late-beta</code>
*<code>./mach try release -v 146.0b12 --tasks release-sim --migration main-to-beta --migration early-to-late-beta</code>
Note the different version number '''145.0b12''' compared to the early beta's '''145.0b1'''.
Note the different version number '''146.0b12''' compared to the early beta's '''146.0b1'''.
<br />
<br />
Add the link in the document after you deselect running and green jobs, in the current date section at RUN LINKS Trunk as Late Beta.<br />
Add the link in the document after you deselect running and green jobs, in the current date section at RUN LINKS Trunk as Late Beta.<br />
Line 68: Line 68:
*<code>git checkout beta</code>
*<code>git checkout beta</code>
*<code>git pull</code>
*<code>git pull</code>
*<code>./mach try release -v 144.0 --tasks release-sim --migration beta-to-release</code>
*<code>./mach try release -v 145.0 --tasks release-sim --migration beta-to-release</code>
'''144.0''' should be replaced with the current version in mozilla-beta (should be one version less than in mozilla-central which is mentioned in Gecko XX beta simulation document).
'''145.0''' should be replaced with the current version in mozilla-beta (should be one version less than in mozilla-central which is mentioned in Gecko XX beta simulation document).
Issues found should reported similar to bugs for beta. Differences:
Issues found should reported similar to bugs for beta. Differences:
* Set status-firefoxXX to '''affected''' for the two highest version numbers.
* Set status-firefoxXX to '''affected''' for the two highest version numbers.
Confirmed users
603

edits