User:Lukasblakk/TryServerSyntax: Difference between revisions

Jump to navigation Jump to search
Line 78: Line 78:
talos (if not present default is '''none''') should be either comma-separated names with no spaces or 'none':
talos (if not present default is '''none''') should be either comma-separated names with no spaces or 'none':
  --t tp4,tscroll || --t all
  --t tp4,tscroll || --t all
==How do I know what test/talos suites I can list?==
'''Note''': we are using a flat file for right now, '''LINK TO VALID_BUILDERS''' but {{bug|589847}} has been filed and in the next iteration we will have a way to generate the lists of valid builder info dynamically from config.py which will keep it in sync with try's configs
==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.


==Tutorial==
==Tutorial==
Line 93: Line 86:
* Push to try
* Push to try
* 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'
* 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'
==Troubleshooting==
==What if I don't put try: in my commit comments?==
If you do not specify anything in your comments you will get the default set of builds for try.
==What if make a syntax error in my commit comments?==
If you do not specify anything in your comments you will get the default set of builds for try.
==How do I know what test/talos suites I can list?==
'''Note''': we are using a flat file for right now, '''LINK TO VALID_BUILDERS''' but {{bug|589847}} has been filed and in the next iteration we will have a way to generate the lists of valid builder info dynamically from config.py which will keep it in sync with try's configs
==What do I do if I need something run?==
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 missed on your changeset triggered. (or re-triggered)
Confirmed users
4,467

edits

Navigation menu