X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Fjenkins.rst;h=812f29b3412c85a1af62b30881f810b4d072824c;hb=744126aea2e7eb0417db904ba026223738c86e8b;hp=12a699fd2778216e52edf707da47bd44dd4bc506;hpb=ce8c93af3b25f5716fe5aaf26a4a87e43bb18fba;p=releng%2Fbuilder.git diff --git a/docs/jenkins.rst b/docs/jenkins.rst index 12a699fd2..812f29b34 100644 --- a/docs/jenkins.rst +++ b/docs/jenkins.rst @@ -1,3 +1,5 @@ +.. _odl-jenkins: + Jenkins ======= @@ -169,9 +171,9 @@ triggered by verify-packer and merge-packer jobs. Please note that the combination of a Packer definitions from `vars`, `templates` and the `provision` scripts is what defines a given minion. For instance, a minion -may be defined as `centos7-java-builder` which is a combination of Packer OS image +may be defined as `centos7-builder` which is a combination of Packer OS image definitions from `vars/centos.json`, Packer template definitions from -`templates/java-buidler.json` and spinup scripts from `provision/java-builder.sh`. +`templates/builder.json` and spinup scripts from `provision/builder.sh`. This combination provides the full definition of the realized minion. Jenkins starts a minion using the latest image which is built and linked into the @@ -195,33 +197,45 @@ Performance flavors come with dedicated CPUs and are not shared with other accounts in the cloud so should ensure consistent performance. .. list-table:: Flavors - :widths: auto" - :header-rows: 1" + :widths: auto + :header-rows: 1 * - Instance Type - CPUs - Memory - * - v1-performance-1 + * - odl-standard-1 - 1 - 4 - * - v1-performance-2 + * - odl-standard-2 - 2 - 8 - * - v1-performance-4 + * - odl-standard-4 - 4 - 16 - * - v1-performance-8 + * - odl-standard-8 - 8 - 32 - * - v1-performance-16 + * - odl-standard-16 - 16 - 64 + * - odl-highcpu-2 + - 2 + - 2 + + * - odl-highcpu-4 + - 4 + - 4 + + * - odl-highcpu-8 + - 8 + - 8 + Pool: ODLVEX ^^^^^^^^^^^^ @@ -229,15 +243,23 @@ Pool: ODLVEX
Jenkins Labels centos7-java-builder-2c-4g, - centos7-java-builder-2c-8g, centos7-java-builder-4c-8g, - centos7-java-builder-8c-8g, centos7-java-builder-4c-16g |
- Minion Template names centos7-java-builder-2c-4g, - centos7-java-builder-2c-4g, centos7-java-builder-2c-8g, - centos7-java-builder-4c-8g, centos7-java-builder-8c-8g, - centos7-java-builder-4c-16g |
+ Jenkins Labels + centos7-builder-2c-1g, + centos7-builder-2c-2g, + centos7-builder-2c-8g, + centos7-builder-4c-4g, + centos7-builder-8c-8g, + centos7-autorelease-4c-16g + |
+ Minion Template names + prd-centos7-builder-2c-1g, + prd-centos7-builder-2c-2g, + prd-centos7-builder-2c-8g, + prd-centos7-builder-4c-4g, + prd-centos7-builder-8c-8g, + prd-centos7-autorelease-4c-16g | Packer Template - releng/builder/packer/templates/java-builder.json |
+ releng/builder/packer/templates/builder.json
Spinup Script releng/builder/jenkins-scripts/builder.sh |
Job Template integration-patch-test-{stream} |
- Gerrit Trigger test-integration |
- ||||
- | -|||||
Job Template integration-patch-test-{stream} |
Gerrit Trigger test-integration |
@@ -753,6 +789,33 @@ TODO: Document test-{project}-{feature} and test-{project}-all.
||||
Job Template integration-multipatch-test-{stream} |
+ Gerrit Trigger multipatch-build |
+ ||||
+ This job builds a list of patches provided in an specific order, and finally builds + a distribution from either provided patch or latest code in branch. + For example if someone leaves the following comment in a patch: + multipatch-build:controller=61/29761/5:45/29645/6,neutron=51/65551/4,netvirt:59/60259/17 + the job will checkout controller patch 61/29761/5, cherry-pick 45/29645/6 and build controller, + checkout neutron patch 51/65551/4 and build neutron, checkout latest netvirt code, + 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. + | +