ReleaseEngineering/TryServer: Difference between revisions

added details on Action Tasks
(added details on Action Tasks)
Line 25: Line 25:


=== Scheduling jobs with Treeherder ===
=== Scheduling jobs with Treeherder ===
Note: This method does not currently support taskcluster jobs. See {{bug|1246167}}.
Note: This method won't work if the pushes are more than a week old. If this is a problem, please file a bug under '''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):
With this method, just push to try like you would to inbound (don't create any try syntax):
Line 31: Line 34:
  $ hg push -r . try
  $ 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 the drop-down arrow at the top right, and choose "Add new Jobs":
You should see a warning about no jobs being scheduled automatically, followed by a link to your push in treeherder. Open the link, select the drop-down arrow at the top right, 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
https://s3.amazonaws.com/media-p.slid.es/uploads/185196/images/2042414/TH_dropdown.png
Line 41: Line 44:
Finally, click "Trigger New Jobs" near the top right of your push.
Finally, click "Trigger New Jobs" near the top right of your push.


NOTE: The outcome of your request 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 the outcome of your request. If there are any issues you will be able to file it with that information.
NOTE: The outcome of your request 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 the outcome of your request. If there are any issues 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/034f72da.png
http://people.mozilla.org/~armenzg/sattap/034f72da.png