Account confirmers, Anti-spam team, Bureaucrats, canmove, Confirmed users, Module owners and peers, smwadministrator, smwcurator, Administrators, MozillaWiki team, Widget editors
731
edits
ReleaseEngineering/TryServer: Difference between revisions
Jump to navigation
Jump to search
→How to push to try: Try job from review phase I will add a screen shot
(Document the Add New Jobs (Search) option in Treeherder) |
(→How to push to try: Try job from review phase I will add a screen shot) Tags: Mobile edit Mobile web edit |
||
| Line 23: | Line 23: | ||
== How to push to try == | == How to push to try == | ||
There are a few ways to schedule jobs on try. | There are a few ways to schedule jobs on try. | ||
=== Attach new jobs from the review === | |||
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. | |||
=== Scheduling jobs with Mach Try === | === Scheduling jobs with Mach Try === | ||