Confirmed users
333
edits
NSS:TryServer: Difference between revisions
Merge of Linux x64 and ASan
Franziskus (talk | contribs) No edit summary |
(Merge of Linux x64 and ASan) |
||
| Line 37: | Line 37: | ||
[default is "do" if omitted] | [default is "do" if omitted] | ||
-p linux,linux64 | -p linux,linux64,win64,arm (or "all" or "none") | ||
[default is "all" if omitted] | [default is "all" if omitted] | ||
| Line 56: | Line 56: | ||
==Platforms (-p / --platform)== | ==Platforms (-p / --platform)== | ||
The currently available platforms are <code>linux</code>, <code>linux64</code> | The currently available platforms are <code>linux</code>, <code>linux64</code>, <code>win64</code>, and <code>arm</code>. Specify any combination of those, like <code>-p linux,win64</code>, to choose the platforms your patch should be tested on. If you want to test all platforms use <code>-p all</code>, if you want no platforms (which is only useful when you want only tools, see below) then use <code>-p none</code>. | ||
==Unit tests (-u / --unittests)== | ==Unit tests (-u / --unittests)== | ||
| Line 76: | Line 76: | ||
==Decision task== | ==Decision task== | ||
After pushing a new changeset to nss-try or the main NSS repository, Taskcluster will spawn a new decision task <code>D</code> that may then extend the task graph, i.e. decide what to build and which tests to run. NSS uses a | After pushing a new changeset to nss-try or the main NSS repository, Taskcluster will spawn a new decision task <code>D</code> that may then extend the task graph, i.e. decide what to build and which tests to run. NSS uses a Node.JS app to do that: | ||
<code>https://hg.mozilla.org/projects/nss/file/default/automation/taskcluster/graph/ | <code>https://hg.mozilla.org/projects/nss/file/default/automation/taskcluster/graph/src/</code> | ||
==Task filter== | ==Task filter== | ||
| Line 84: | Line 84: | ||
The file above will build the complete task graph, for all build types, platforms, test suites, and tools. Before this is sent back to Taskcluster however, we will filter all tasks by the given try syntax, if any. The code for that filter can be found at: | The file above will build the complete task graph, for all build types, platforms, test suites, and tools. Before this is sent back to Taskcluster however, we will filter all tasks by the given try syntax, if any. The code for that filter can be found at: | ||
<code>https://hg.mozilla.org/projects/nss/file/default/automation/taskcluster/graph/try_syntax.js</code> | <code>https://hg.mozilla.org/projects/nss/file/default/automation/taskcluster/graph/src/try_syntax.js</code> | ||
==Making changes== | ==Making changes== | ||
Whenever you're adding or changing some piece of code in the try syntax filter, please push to nss-try before landing to ensure it's all working as expected. All changes to the NSS Taskcluster CI can be tested on nss-try before landing on the main repository. | Whenever you're adding or changing some piece of code in the try syntax filter, please push to nss-try before landing to ensure it's all working as expected. All changes to the NSS Taskcluster CI can be tested on nss-try before landing on the main repository. | ||