X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Fjenkins.rst;h=2c0d629441ccd1272d188642a8cc0334a3d4e9a2;hb=3b634d60e3d2d3227e70427d34d21886738ffb2f;hp=d4b7eff6932909fd07251e0c97a9e34df6807df6;hpb=0dcb25cd9b142c67e1e1c28a2ae3ca32c7242066;p=releng%2Fbuilder.git diff --git a/docs/jenkins.rst b/docs/jenkins.rst index d4b7eff69..2c0d62944 100644 --- a/docs/jenkins.rst +++ b/docs/jenkins.rst @@ -36,6 +36,8 @@ Gerrit. So if your project is called "aaa" then create a new jjb/aaa directory. Next we will create .yaml as follows: +.. code-block:: yaml + - project: name: -carbon jobs: @@ -43,7 +45,6 @@ Next we will create .yaml as follows: - '{project-name}-distribution-{stream}' - '{project-name}-integration-{stream}' - '{project-name}-merge-{stream}' - - '{project-name}-periodic-{stream}' - '{project-name}-verify-{stream}-{maven}-{jdks}' project: '' @@ -55,7 +56,7 @@ Next we will create .yaml as follows: - openjdk8 maven: - mvn33: - mvn-version: '{mvn33}' + mvn-version: 'mvn33' mvn-settings: '-settings' mvn-goals: 'clean install -Dmaven.repo.local=/tmp/r -Dorg.ops4j.pax.url.mvn.localRepository=/tmp/r' mvn-opts: '-Xmx1024m -XX:MaxPermSize=256m' @@ -78,11 +79,14 @@ Next we will create .yaml as follows: Replace all instances of with the name of your project. This will create the jobs with the default job types we recommend for Java projects. If your project is participating in the simultanious-release and ultimately will -be included in the final distribution. We recommend adding the following job +be included in the final distribution, it is required to add the following job types into the job list for the release you are participating. - '{project-name}-distribution-check-{stream}' - '{project-name}-validate-autorelease-{stream}' + +.. code-block:: yaml + + - '{project-name}-distribution-check-{stream}' + - '{project-name}-validate-autorelease-{stream}' If you'd like to explore the additional tweaking options available please refer to the `Jenkins Job Templates`_ section. @@ -113,8 +117,7 @@ Build Minions The Jenkins jobs are run on build minions (executors) which are created on an as-needed basis. If no idle build minions are available a new VM is brought up. This process can take up to 2 minutes. Once the build minion has finished a -job, it will remain online for 45 minutes before shutting down. Subsequent -jobs will use an idle build minion if available. +job, it will be destroyed. Our Jenkins master supports many types of dynamic build minions. If you are creating custom jobs then you will need to have an idea of what type of minions @@ -126,99 +129,92 @@ label. Adding New Components to the Minions ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -If your project needs something added to one of the minions used during build -and test you can help us get things added faster by doing one of the following: +If your project needs something added to one of the minions, you can help us +get things added faster by doing one of the following: -* Submit a patch to RelEng/Builder for the `spinup-scripts`_ that - configures your new piece of software. -* Submit a patch to RelEng/Builder for the Vagrant template's bootstrap.sh in - the `vagrant-definitions`_ directory that configures your new piece of - software. +* Submit a patch to RelEng/Builder for the appropriate `jenkins-scripts` + definition which configure software during minion boot up. +* Submit a patch to RelEng/Builder for the `packer/provision` scripts that + configures software during minion instance imaging. +* Submit a patch to RelEng/Builder for the Packer's templates in + the `packer/templates` directory that configures a new instance definition + along with changes in `packer/provision`. Going the first route will be faster in the short term as we can inspect the changes and make test modifications in the sandbox to verify that it works. -The second route, however, is better for the community as a whole as it will -allow others that utilize our Vagrant setups to replicate our systems more +.. note:: + + The first route may add additional setup time considering this is run every + time the minion is booted. + +The second and third routes, however, is better for the community as a whole as +it will allow others to utilize our Packer setups to replicate our systems more closely. It is, however, more time consuming as an image snapshot needs to be -created based on the updated Vagrant definition before it can be attached to -the sandbox for validation testing. +created based on the updated Packer definitions before it can be attached to the +Jenkins configuration on sandbox for validation testing. In either case, the changes must be validated in the sandbox with tests to make sure that we don't break current jobs and that the new software features are operating as intended. Once this is done the changes will be merged and -the updates applied to the RelEng Jenkins production silo. - -Please note that the combination of a Vagrant minion snapshot and a Jenkins -spinup script is what defines a given minion. For instance, a minion may be -defined by the `vagrant-basic-java-node`_ Vagrant definition -and the `spinup-scripts-controller.sh`_ Jenkins spinup script -(as the dynamic\_controller minion is). The pair provides the full definition of -the realized minion. Jenkins starts a minion using the last-spun Vagrant snapshot -for the specified definition. Once the base Vagrant instance is online Jenkins -checks out the RelEng/Builder repo on it and executes two scripts. The first is -`spinup-scripts-basic_settings.sh`_, which is a baseline for all of the minions. -The second is -the specialized spinup script, which handles any system updates, new software -installs or extra environment tweaks that don't make sense in a snapshot. After -all of these scripts have executed Jenkins will finally attach the minion as an -actual minion and start handling jobs on it. +the updates applied to the RelEng Jenkins production silo. Any changes to +files under `releng/builder/packer` will be validated and images would be built +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 +definitions from `vars/centos.json`, Packer template definitions from +`templates/java-buidler.json` and spinup scripts from `provision/java-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 +Jenkins configuration. Once the base instance is online Jenkins checks out the +RelEng/Builder repo on it and executes two scripts. The first is +`provision/baseline.sh`, which is a baseline for all of the minions. + +The second is the specialized script, which handles any system updates, +new software installs or extra environment tweaks that don't make sense in a +snapshot. Examples could include installing new package or setting up a virtual +environment. Its imperative to ensure modifications to these spinup scripts have +considered time taken to install the packages, as this could increase the build +time for every job which runs on the image. After all of these scripts have +executed Jenkins will finally attach the minion as an actual minion and start +handling jobs on it. Pool: ODLRPC -^^^^^^^^^^^^^^^^^^^ +^^^^^^^^^^^^ .. raw:: html - - - - + + + + - - - - - - - - - - - - - - - - - - - - - - - + + + @@ -233,9 +229,10 @@ Pool: ODLRPC - - - + + + @@ -245,9 +242,10 @@ Pool: ODLRPC - - - + + + @@ -257,47 +255,22 @@ Pool: ODLRPC - - - - - - - - - - - - - - - - - - - - - - - - + + + + - - - + + + @@ -310,9 +283,9 @@ Pool: ODLRPC - - - + + + @@ -325,9 +298,9 @@ Pool: ODLRPC - - - + + + @@ -337,6 +310,21 @@ Pool: ODLRPC
Jenkins Label
dynamic_verify		Minion Template name
centos7-builder		Vagrant Definition
releng/builder/vagrant/basic-builder		Spinup Script
releng/builder/jenkins-scripts/builder.sh		Jenkins Labels
dynamic_controller, dynamic_verify, + dynamic_merge, centos7-java-builder-2c-4g, centos7-java-builder-2c-8g, + centos7-java-builder-4c-8g		Minion Template names
centos7-java-builder-2c-4g, + centos7-java-builder-2c-8g, centos7-java-builder-2c-8g, + centos7-java-builder-4c-8g, centos7-java-builder-8c-8g		Packer Template
+ releng/builder/packer/templates/java-builder.json		Spinup Script
+ releng/builder/jenkins-scripts/builder.sh
A CentOS 7 huild minion. This system has OpenJDK 1.7 (Java7) and OpenJDK 1.8 (Java8) installed on it along with all the other components and libraries needed for building any current OpenDaylight project. This is - the label that is used for all basic -verify and -daily- builds for + the label that is used for all basic verify, merge and daily builds for projects.
Jenkins Label
dynamic_merge		Minion Template name
centos7-builder		Vagrant Definition
releng/builder/vagrant/basic-builder		Spinup Script
releng/builder/jenkins-scripts/builder.sh
- See dynamic_verify (same image on the back side). This is the label that - is used for all basic -merge and -integration- builds for projects. -
Jenkins Label
matrix_master		Minion Template name
centos7-matrix		Vagrant Definition
releng/builder/vagrant/basic-java-node		Spinup Script
releng/builder/jenkins-scripts/matrix.sh
- This is a very minimal system that is designed to spin up with 2 build - instances on it. The purpose is to have a location that is not the - Jenkins master itself for jobs that are executing matrix operations - since they need a director location. This image should not be used for - anything but tying matrix jobs before the matrx defined label ties. -
Jenkins Label
dynamic_robot		Minion Template name
centos7-robot		Vagrant Definition
releng/builder/vagrant/integration-robotframework		Jenkins Labels
dynamic_robot, centos7-robot-2c-2g		Minion Template names
centos7-robot-2c-2g		Packer Template
+ releng/builder/packer/templates/robot.json		 Spinup Script
releng/builder/jenkins-scripts/robot.sh
Jenkins Label
ubuntu_mininet		Minion Template name
ubuntu-trusty-mininet		Vagrant Definition
releng/builder/vagrant/ubuntu-mininet		Jenkins Labels
ubuntu_mininet, ubuntu-trusty-mininet-2c-2g		Minion Template names
ubuntu-trusty-mininet-2c-2g		Packer Template
+ releng/builder/packer/teamplates/mininet.json		 Spinup Script
releng/builder/jenkins-scripts/mininet-ubuntu.sh
Jenkins Label
ubuntu_mininet_ovs_23		Minion Template name
ubuntu-trusty-mininet-ovs-23		Vagrant Definition
releng/builder/vagrant/ubuntu-mininet-ovs-23		Jenkins Labels
ubuntu_mininet_ovs_23, + ubuntu-trusty-mininet-ovs-23-2c-2g		Minion Template names
ubuntu-trusty-mininet-ovs-23-2c-2g		Packer Template
releng/builder/packer/templates/mininet-ovs-2.3.json		 Spinup Script
releng/builder/jenkins-scripts/mininet-ubuntu.sh
Jenkins Label
dynamic_controller		Minion Template name
centos7-java		Vagrant Definition
releng/builder/vagrant/basic-java-node		Spinup Script
releng/builder/jenkins-scripts/controller.sh
- A CentOS 7 minion that has the basic OpenJDK 1.7 (Java7) and OpenJDK - 1.8 (Java8) installed and is capable of running the controller, not - building. -
Jenkins Label
dynamic_java		Minion Template name
centos7-java		Vagrant Definition
releng/builder/vagrant/basic-java-node		Spinup Script
releng/builder/jenkins-scripts/controller.sh
- See dynamic_controller as it is currently the same image. -
Jenkins Label
dynamic_java_8g		Minion Template name
centos7-java-8g		Vagrant Definition
releng/builder/vagrant/basic-java-node		Spinup Script
releng/builder/jenkins-scripts/controller.sh		Jenkins Labels
ubuntu_mininet_ovs_25, + ubuntu-trusty-mininet-ovs-25-2c-2g		Minion Template names
ubuntu-trusty-mininet-ovs-25-2c-2g		Packer Template
releng/builder/packer/templates/mininet-ovs-2.5.json		Spinup Script
releng/builder/jenkins-scripts/mininet-ubuntu.sh
- See dynamic_controller as it is currently the same image but with 8G of RAM. + Basic Ubuntu system with ovs 2.5 and mininet 2.2.2
Jenkins Label
dynamic_devstack		Minion Template name
centos7-devstack		Vagrant Definition
releng/builder/vagrant/ovsdb-devstack		Jenkins Labels
dynamic_devstack, centos7-devstack-2c-4g		Minion Template names
centos7-devstack-2c-4g		Packer Template
releng/builder/packer/templates/devstack.json		 Spinup Script
releng/builder/jenkins-scripts/devstack.sh
Jenkins Label
dynamic_docker		Minion Template name
centos7-docker		Vagrant Definition
releng/builder/vagrant/ovsdb-docker		Jenkins Labels
dynamic_docker, centos7-docker-2c-4g		Minion Template names
centos7-docker-2c-4g		Packer Template
releng/builder/packer/templates/docker.json		 Spinup Script
releng/builder/jenkins-scripts/docker.sh
Jenkins Label
gbp_trusty		Minion Template name
gbp_trusty		Vagrant Definition
releng/builder/vagrant/gbp-ubuntu-docker-ovs-node		Jenkins Labels
gbp_trusty, ubuntu-trusty-gbp-2c-2g		Minion Template names
ubuntu-trusty-gbp-2c-2g		Packer Template
releng/builder/packer/templates/gbp.json		 Spinup Script
releng/builder/jenkins-scripts/ubuntu-docker-ovs.sh
+Pool: ODLPUB - HOT (Heat Orchestration Templates) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +HOT integration enables to spin up integration labs servers for CSIT jobs +using heat, rathar than using jclouds (deprecated). Image names are updated +on the project specific job templates using the variable +`{odl,docker,openstack,tools}_system_image` followed by image name in the +format ` -