This reverts commit 7100a7f225e60936f23d24c757c1b14c9b136ec4. The referenced commit, in addition to what it advertises, also filters the result of update_jobs to include only changed jobs. If there are no change jobs, then, if the user specifies --delete-old, there are no jobs in the list of jobs to keep which comes from the result of update_jobs. In that case, all jobs are deleted. Or in other words, the logic in this change is that all jobs not updated are deleted. Proposing as a revert because this is currently causing serious problems for continuously deployed JJB instances, and the very common --delete-old code path should be properly tested with this change before it lands again. Change-Id: I98443f0c085e27ed8dfece6409434015ac24b306
README
Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML 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:
$ sudo python setup.py install
Online documentation:
Developers
Bug report:
Repository:
Cloning:
git clone https://git.openstack.org/openstack-infra/jenkins-job-builder
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 libyaml
Then install the required python packages using pip:
$ sudo pip install PyYAML python-jenkins