Confirmed users
4,467
edits
User:Lukasblakk/TryServerSyntax: Difference between revisions
Jump to navigation
Jump to search
→What do I do if my commit comments don't get me what I want?
| Line 85: | Line 85: | ||
==What do I do if my commit comments don't get me what I want?== | ==What do I do if my commit comments don't get me what I want?== | ||
If you missed something in your commit comments you can ping whoever is on buildduty [link] and give them [details] to have the build/test/talos you've missed on your changeset triggered. | If you missed something in your commit comments you can ping whoever is on buildduty [link] and give them [details] to have the build/test/talos you've missed on your changeset triggered. | ||
==Tutorial== | |||
* You've got your mq patch ready to land | |||
* Set the commit comment to what you would like to run on try. In this case, let's say you want a linux opt build, no mobile, and only get talos tp4 results | |||
hg commit -m "Patch to fix a pixel placement try: --build o --p linux --m none --t tp4" | |||
* What happens? 'Linux tryserver build' builder is created and runs your opt linux build. If the build completes successfully then the talos tests are triggered and once the test-master gets the notice of the change it will read the hg commit comments and only kick off the one builder for tp4 'Rev3 Fedora 12 tryserver talos tp4' | |||