Confirmed users
571
edits
Sheriffing/How To/Beta simulations: Difference between revisions
Jump to navigation
Jump to search
m
Sheriffing/How To/Beta simulations (view source)
Revision as of 16:27, 14 November 2022
, 14 November 2022increased version numbers (Nightly = 109, Beta = 108)
(increased version numbers (Nightly = 108, Beta = 107)) |
m (increased version numbers (Nightly = 109, Beta = 108)) |
||
| Line 29: | Line 29: | ||
**<code>hg pull central</code> - needed only if you didn't import/backout anything | **<code>hg pull central</code> - needed only if you didn't import/backout anything | ||
**<code>hg update central</code> - needed only if you didn't import/backout anything | **<code>hg update central</code> - needed only if you didn't import/backout anything | ||
**<code>./mach try release -v | **<code>./mach try release -v 109.0b1 --tasks release-sim --migration central-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>hg commit -m "Early beta sim"</code> and select the jobs with <code>./mach try chooser --no-artifact</code>'''</span> | ||
***'''-v | ***'''-v 109.0b1''': Sets the version number to use in the beta simulation. <span style="color:#FF0000">'''Replace "101" 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 central-to-beta''': Activates modification of the configuration to switch from central to beta. | ***'''--migration central-to-beta''': Activates modification of the configuration to switch from central to beta. | ||
| Line 38: | Line 38: | ||
== 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 | *<code>./mach try release -v 109.0b12 --tasks release-sim --migration central-to-beta --migration early-to-late-beta</code> | ||
Note the different version number ''' | Note the different version number '''109.0b12''' compared to the early beta's '''109.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 67: | Line 67: | ||
*<code>hg pull beta</code> | *<code>hg pull beta</code> | ||
*<code>hg update beta</code> | *<code>hg update beta</code> | ||
*<code>./mach try release -v | *<code>./mach try release -v 108.0 --tasks release-sim --migration beta-to-release</code> | ||
''' | '''108.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. | ||