NSS:TryServer

This page describes how to use the NSS try server.

(You probably want to push to nss-try before pushing to the main NSS repository.)

Pushing to nss-try

Create a new entry in the [paths] section of your $nss-directory/.hg/hgrc file:

try = ssh://ldap.username@you.com@hg.mozilla.org/projects/nss-try

Now every time you want to push a patch to nss-try you can simply do:

$ cd $nss-directory/
$ hg push -f try

Your try job will show up on the nss-try dashboard in a second.

Using try syntax

This section describes how to use try syntax to push your patch to nss-try and run only a subset of all available Taskcluster tests.

try: -b do -p all -u all -t all

This will run all available Taskcluster builds and tests and is equivalent to not specifying any try syntax at all.

Overview

Available options are:

-b do (debug and opt)
   [default is "do" if omitted]

-p linux,linux64,linux64-asan,win64 (or "all" or "none")
   [default is "all" if omitted]

-u crmf,chains,cipher,db,ec,fips,gtest,lowhash,merge,sdr,
   smime,tools,ssl (or "all" or "none")
   [default is "none" if omitted]

-t clang-format,scan-build (or "all" or "none")
   [default is "none" if omitted]

Build types (-b / --build)

There are two available build types: debug and opt. If you want both use -b do, for only debug builds use -b d, and use -b o for only optimized builds.

Platforms (-p / --platform)

The currently available platforms are linux, linux64, linux64-asan (debug-only), and win64. Specify any combination of those, like -p linux,win64, to choose the platforms your patch should be tested on. If you want to test all platforms use -p all, if you want no platforms (which is only useful when you want only tools, see below) then use -p none.