cherry-pick 59/60259/17 and build netvirt, finally it will checkout latest distribution
code and build a distribution. The resulting distribution is stored in Nexus and the URL
is stored in a variable called BUNDLE_URL visible in the job console.
+ This job also accepts a gerrit topic, for example: multipatch-build:topic=binding-tlc-rpc,
+ in this case the job will find all patches in the topic binding-tlc-rpc for the projects
+ specified in the BUILD_ORDER parameter and will build all projects from the first a patch
+ has been found, for successive projects the branch HEAD is used if no patch is found.
+ The job uses patch numbers to sort patches in the same project.
Use multipatch-build-fast (vs multipatch-build) for building projects fast (-Pq).
This job should not alter Gerrit votes for a given patch, nor will do anything with the
given patch unless the patch is added to the build list.
# Edit jenkins.ini with your username, API token and ODL's sandbox URL
$ cat jenkins.ini
<snip>
+ [job_builder]
+ retain_anchors=True
+
[jenkins]
user=<your ODL username>
password=<your ODL Jenkins sandbox API token>
JJB jobs <Testing Jobs_>`_ produce valid XML descriptions of Jenkins jobs you
can push them to the Jenkins sandbox.
+Add the --jobs-only (-j) option to push only jobs to Jenkins sandbox. Pushing
+views to Jenkins sandbox requires admin access.
+
.. important::
When pushing with `jenkins-jobs`, a log message with the number
.. code-block:: bash
# Don't push all jobs by omitting the final param! (ctrl+c to abort)
- jenkins-jobs --conf jenkins.ini update jjb/ <job-name>
+ jenkins-jobs --conf jenkins.ini update -j jjb/ <job-name>
Alternatively, you can push a job to the Jenkins sandbox with a special comment in a
releng/builder gerrit patch. The job will be based off of the code your patch is