Confirmed users
333
edits
NSS:TryServer: Difference between revisions
Jump to navigation
Jump to search
adding impl details
(add tools) |
(adding impl details) |
||
| Line 62: | Line 62: | ||
The currently available tools are <code>clang-format</code>, <code>scan-build</code>. Specify any combination of those, like <code>-t clang-format,scan-build</code>, to choose the tools to run with your patch. If you want to run all tools use <code>-t all</code>, if you want no tools use <code>-t none</code>. | The currently available tools are <code>clang-format</code>, <code>scan-build</code>. Specify any combination of those, like <code>-t clang-format,scan-build</code>, to choose the tools to run with your patch. If you want to run all tools use <code>-t all</code>, if you want no tools use <code>-t none</code>. | ||
=Try syntax implementation= | |||
This section describes how the try syntax is implemented for nss-try. | |||
==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 small Node.JS script to do that: | |||
<code>https://hg.mozilla.org/projects/nss/file/default/automation/taskcluster/graph/build.js</code> | |||
==Task filter== | |||
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> | |||
==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. | |||