Confirmed users
571
edits
Sheriffing/How To/Beta simulations: Difference between revisions
Sheriffing/How To/Beta simulations (view source)
Revision as of 10:51, 14 March 2023
, 14 March 2023increased version numbers (Nightly = 113, Beta = 112)
m (increased version numbers (Nightly = 112, Beta = 111)) |
(increased version numbers (Nightly = 113, Beta = 112)) |
||
| 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 113.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 113.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. | ||
This changes the configuration to the beta simulation, pushes to the Try server and reverts the changes. | This changes the configuration to the beta simulation, pushes to the Try server and reverts the changes. | ||
Open the first Treeherder link in the console. It might take a few minutes for Treeherder to find that job, though. '''Add the link''' after you '''deselect''' the running and the green jobs and check that the classified jobs are visible, in the current date section at '''Run Links: Trunk as Early Beta in the Gdoc.''' | Open the first Treeherder link in the console. It might take a few minutes for Treeherder to find that job, though. '''Add the link''' after you '''deselect''' the running and the green jobs and check that the classified jobs are visible, in the current date section at '''Run Links: Trunk as Early Beta in the Gdoc.''' | ||
* To build locally, run <code>./mach try release -v | * To build locally, run <code>./mach try release -v 113.0b1 --tasks release-sim --migration central-to-beta --stage-changes && ./mach build</code> - do to not use artifact builds. | ||
== 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 113.0b12 --tasks release-sim --migration central-to-beta --migration early-to-late-beta</code> | ||
Note the different version number ''' | Note the different version number '''113.0b12''' compared to the early beta's '''113.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>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 112.0 --tasks release-sim --migration beta-to-release</code> | ||
''' | '''112.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. | ||