Confirmed users
656
edits
User:Ahal/Try: Difference between revisions
Jump to navigation
Jump to search
→How to push to try
| Line 8: | Line 8: | ||
== How to push to try == | == How to push to try == | ||
There are two ways to schedule jobs on try. You can either push like normal, and select which jobs you want using [https://wiki.mozilla.org/EngineeringProductivity/Projects/Treeherder treeherder], or you can specify a try syntax in your commit message to schedule jobs automatically. Whichever method you choose, | There are two ways to schedule jobs on try. You can either push like normal, and select which jobs you want using [https://wiki.mozilla.org/EngineeringProductivity/Projects/Treeherder treeherder], or you can specify a try syntax in your commit message to schedule jobs automatically. Whichever method you choose, you should first setup mercurial by running: | ||
$ ./mach mercurial-setup | |||
Be sure to at least enable the [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/firefoxtree.html firefoxtree extension]. Among other things, this will give you a handy 'try' alias you can use for pushing. If for some reason you prefer not to use firefoxtree, you can set the same alias up manually in your hgrc: | |||
[paths] | [paths] | ||
| Line 14: | Line 18: | ||
Note: Never pull from try. You'll end up with hundreds of heads containing everyone's half baked and broken pushes. | Note: Never pull from try. You'll end up with hundreds of heads containing everyone's half baked and broken pushes. | ||
For more information, see [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html mercurial for mozillians]. | |||
| Line 62: | Line 68: | ||
$ hg qref --message "try: <your-computed-syntax-here>" | $ hg qref --message "try: <your-computed-syntax-here>" | ||
$ hg push -f try | $ hg push -f try | ||
== Viewing the results == | == Viewing the results == | ||