Confirmed users
709
edits
ReleaseEngineering/TryServer: Difference between revisions
Add a screenshot
(→How to push to try: Try job from review phase I will add a screen shot) Tags: Mobile edit Mobile web edit |
(Add a screenshot) |
||
| Line 27: | Line 27: | ||
For every patch submitted for review in Phabricator, a new Try run is automatically created. This run is created for static analysis, linting and other tasks. | For every patch submitted for review in Phabricator, a new Try run is automatically created. This run is created for static analysis, linting and other tasks. | ||
As described below, attaching new jobs to the run is easy and doesn't require more actions from the developer. | As described below, attaching new jobs to the run is easy and doesn't require more actions from the developer. | ||
Just click on the ''Treeherder Jobs''. | |||
[[File:Screenshot 2019-10-07 ⚙ D48316 Bug 1585593 - Enable Fission for Raptor.png]] | |||
=== Scheduling jobs with Mach Try === | === Scheduling jobs with Mach Try === | ||