Custom JJB templates are defined for projects that use Docker to
compile code and build DEB/RPM packages, then push the packages to
Custom JJB templates are defined for projects that use Docker to
compile code and build DEB/RPM packages, then push the packages to
- a) click on your user name (top right)
- b) click Configure (left menu)
- c) under API Token, click Add new Token (button)
- d) copy the token string
+a) click on your user name (top right)
+b) click Configure (left menu)
+c) under API Token, click Add new Token (button)
+d) copy the token string
Create a config file jenkins.ini using the following template and your
credentials (user name and API token from above)::
Create a config file jenkins.ini using the following template and your
credentials (user name and API token from above)::
### How to build from a Gerrit review branch
This explains how to launch a "verify" job in the Sandbox on an open
### How to build from a Gerrit review branch
This explains how to launch a "verify" job in the Sandbox on an open
-review. Most "verify" jobs accept parameters to build code in a
-review submitted to Gerrit. You must specify the change ref spec,
-which is a Git branch name. Get this by inspecting Gerrit's
-"download" links at the top right. The branch name will be something
+review. Most "verify" jobs accept parameters to build code in a
+review submitted to Gerrit. You must specify the change ref spec,
+which is a Git branch name. Get this by inspecting Gerrit's
+"download" links at the top right. The branch name will be something
The first number is a mystery to me; the second number is the Gerrit
change number; the third number is the patch set within the change.
The first number is a mystery to me; the second number is the Gerrit
change number; the third number is the patch set within the change.