ReleaseEngineering/TryServer: Difference between revisions

Jump to navigation Jump to search
Edited for clarity around getting try access.
m (add extending jobs on a push)
(Edited for clarity around getting try access.)
Line 2: Line 2:
The [https://treeherder.mozilla.org/#/jobs?repo=try try server] is an easy way to test a patch without actually checking the patch into the core repository. Your code will go through the same tests as a mozilla-central push, and you'll be able to download builds if you wish.
The [https://treeherder.mozilla.org/#/jobs?repo=try try server] is an easy way to test a patch without actually checking the patch into the core repository. Your code will go through the same tests as a mozilla-central push, and you'll be able to download builds if you wish.


To use try server, you need a [http://www.mozilla.org/hacking/committer/ Mozilla hg account] ([http://www.mozilla.org/hacking/commit-access-policy/ level 1] is sufficient).
== Getting access to the Try Server  ==
To use try server, you'll need [http://www.mozilla.org/hacking/commit-access-policy/ Level 1 Commit Access].
 
You can learn more about Mozilla's commit access policies and start the process of signing up for an account here: [http://www.mozilla.org/hacking/committer/ Becoming a Mozilla Contributor.]  


== How to push to try ==
== How to push to try ==
Confirmed users, Bureaucrats and Sysops emeriti
421

edits

Navigation menu