f74501e781
This patch adds support for the Maven release build wrapper. The Maven release plugin makes use of the concept of jenkins Actions to trigger the actual release - https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes The actual code for the action - https://github.com/jenkinsci/m2release-plugin/blob/master/ src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java, seems to put together all the required parameters and makes a call to scheduleBuild2 and passes an Action object with it. Afaik, JJB doesn't support the concept of Actions. If the M2ReleaseAction was an instance of Builder, instead of Action it would work with this. Currently, I don't see how the actual build (release) can be triggered from JJB config, and it seems like we can define the build wrapper alone as part of the job definition, and would still have to trigger the release from the UI for the job like - <jobname>/m2release Change-Id: Ifc979cdb8e40ad31debff04f745649f23f7ef91a
README
Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML or JSON format and uses them to configure Jenkins. You can keep your job descriptions in human readable text format in a version control system to make changes and auditing easier. It also has a flexible template system, so creating many similarly configured jobs is easy.
To install:
$ pip install --user jenkins-job-builderOnline documentation:
Developers
Bug report:
Repository:
Cloning:
git clone https://git.openstack.org/openstack-infra/jenkins-job-builderA virtual environment is recommended for development. For example, Jenkins Job Builder may be installed from the top level directory:
$ virtualenv .venv
$ source .venv/bin/activate
$ pip install -r test-requirements.txt -e .Patches are submitted via Gerrit at:
Please do not submit GitHub pull requests, they will be automatically closed.
More details on how you can contribute is available on our wiki at:
Writing a patch
We ask that all code submissions be pep8 and pyflakes clean. The
easiest way to do that is to run tox before submitting code for review
in Gerrit. It will run pep8 and pyflakes in
the same manner as the automated test suite that will run on proposed
patchsets.
When creating new YAML components, please observe the following style conventions:
- All YAML identifiers (including component names and arguments) should be lower-case and multiple word identifiers should use hyphens. E.g., "build-trigger".
- The Python functions that implement components should have the same name as the YAML keyword, but should use underscores instead of hyphens. E.g., "build_trigger".
This consistency will help users avoid simple mistakes when writing YAML, as well as developers when matching YAML components to Python implementation.
Installing without setup.py
For YAML support, you will need libyaml installed.
Mac OS X:
$ brew install libyamlThen install the required python packages using pip:
$ sudo pip install PyYAML python-jenkins