X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Fjenkins.rst;h=812f29b3412c85a1af62b30881f810b4d072824c;hb=b5479eb076ccd868105e9a0ba814005e93f9f7a2;hp=25e5370f922310a886152e8906f3009194590286;hpb=07568191388cf45a9525d473a9d59df7c177e78e;p=releng%2Fbuilder.git diff --git a/docs/jenkins.rst b/docs/jenkins.rst index 25e5370f9..812f29b34 100644 --- a/docs/jenkins.rst +++ b/docs/jenkins.rst @@ -880,6 +880,9 @@ example is provided by releng/builder at `example-jenkins.ini`_. # Edit jenkins.ini with your username, API token and ODL's sandbox URL $ cat jenkins.ini + [job_builder] + retain_anchors=True + [jenkins] user= password= @@ -937,6 +940,9 @@ Once you've `configured your \`jenkins.ini\` `_ and `verified yo JJB 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 @@ -956,7 +962,7 @@ can push them to the Jenkins sandbox. .. code-block:: bash # Don't push all jobs by omitting the final param! (ctrl+c to abort) - jenkins-jobs --conf jenkins.ini update jjb/ + jenkins-jobs --conf jenkins.ini update -j jjb/ 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