Changes

Jump to: navigation, search

ReleaseEngineering/TryServer

788 bytes removed, 20:07, 26 September 2017
m
Update notes
=== Scheduling jobs with Treeherder ===
Note: The "Add New Jobs" feature doesn't show TaskCluster jobs for non-try pushes. See {{bug|1286813}} With this method, just push to try like you would to inbound (don't create any try syntax):  $ hg push -r . try You should see a warning about no jobs being scheduled automatically, followed by a link to your push in treeherder. Open the link, select Select the drop-down arrow at the top rightof your push, and choose "Add new Jobs". It might take upto 6 seconds for the jobs to load ({{bug|1288028}}) :
https://s3.amazonaws.com/media-p.slid.es/uploads/185196/images/2042414/TH_dropdown.png
Finally, click "Trigger New Jobs" near the top right of your push.
NOTE: The outcome of your request An action task gets scheduled which will show up as a 'Sch' job ("Scheduling" request) or as an 'A' ("Action Task") job depending if you requested Buildbot (old CI) or TaskCluster (new CI) jobs. [https://armenzg.blogspot.ca/2016/06/adding-new-jobs-to-treeherder-is-now.html Blog post]. In the logs you can see schedule all the outcome of your request. If there are any issues tasks you will be able to file it with that information. A failed 'Sch' or 'A' job would mean "Add New Jobs" has failed. http://people.mozilla.org/~armenzg/sattap/034f72dachose.png
=== Scheduling jobs with Try Syntax ===
Confirm
3,990
edits

Navigation menu