It was broken by 14ed8b12, resulting in:
$ jenkins-jobs delete-all
Traceback (most recent call last):
File "/Users/marca/python/virtualenvs/jenkins-job-builder/bin/jenkins-jobs", line 10, in <module>
sys.exit(main())
File "/Users/marca/dev/git-repos/jenkins-job-builder/jenkins_jobs/cmd.py", line 143, in main
if options.path == sys.stdin:
AttributeError: 'Namespace' object has no attribute 'path'
Change-Id: I42a3ef9f3cfca7b4667498009351e0027aa316d7
instead of using inline examples in docstrings. With literalinclude, we
know the examples are tested.
Change-Id: I95fbb4726bd6731d9687d09a3d6e7d4e5a445131
When ignore_cache was loaded from the config file (including the
default config) it was treated as a string, which evaluates to
true in boolean expressions. Therefore, unless ignore_cache was
set on the command line, it would always behave as if true.
Fix by asking configparser for a boolean value.
Change-Id: I63af8637671248fc1a6895d1eb82f1c2e24ce5c2
It's been quite some time since the author of the entire package
has been HP. Update the setup metadata to reflect this.
Change-Id: I239246eb1ac0ca659d1a118a0e009ab224bc6758
jenkins build-timeout plugin version 1.13 has a new option[1] to expose the
timeout value via an environment variable. Adding this option to the
equivalent jjb module. Also created tests for the examples.
[1] https://github.com/jenkinsci/build-timeout-plugin/pull/22
Partial-Bug: #1287883
Change-Id: Ia0d6570e9aae55ceadf076716fc8ad7688ff6214
This plugin allows the specification of critical blocks for builders.
Once a set of builders is "wrapped" by a critical block start/critical
block end pair, any resources (string) specified in the exclusion build
wrapper will cause any jobs with those same resources to block and allow
only one of those builds to proceed at a time.
Change-Id: I0bf4ab003709917aa7fe6ad57b31200f466658da
Since version 2.11.0 the Gerrit Trigger Plugin can be configured
to trigger on more than one server.
Change-Id: I2082c5cfd14cd2494e2a7192beeb4909552cb7f6
This makes it a little bit clearer that GitHub pull requests are not
accepted and will be automatically closed.
This is a small tweak to help with one of the issues mentioned here:
http://www.alexconrad.org/2014/04/the-painful-process-of-submitting-your.html
Change-Id: Ie4aa8297a75f00ddd9e6c0fce722aa7a6586d52d
E.g.:
jenkins-jobs test < config/jenkins.yml
This is convenient for demoing or implementing functional tests.
Change-Id: I4e3030e261d3b90f75e4a033ea074d18764d97bf
Allow to specify multiple branch patterns in a 'branches' block
within the 'project' block.
If no 'branches' block is present, fall back to using the single
branch specified directly in the 'project' section.
If a branch is specified both at the project level, and in the
'branches' section, ignore the one at project level.
Closes-Bug: #1302502
Change-Id: I1fb2ce0bb3776d365f2c0e98a703c6dfba5fac7f
Zuul 2.0 passes to jobs an additional parameter ZUUL_URL which instructs
workers from where to clone repositories.
This is NOT the same as the zuul-url defined by Jenkins Job Builder
which is the notification endpoint set on the jobs and is unrelated.
Change-Id: I4924a5b7ae99571efd70eeb188ddd3d821a4c61b
Solely for the transitive dependencies. Ignore errors from hacking
as do the other openstack-infra python projects.
Change-Id: Ib5953c31a5380f9f57c7f79e1ce0699aef5eb629
This change creates the output directory for the test subcommand if it
does not yet exist. If it exists, use it. Any other exceptions are
re-raised.
Change-Id: I487c69e70f9b6c475691ca4fef4669a0c318ab55
If any tests exercise code paths that emit logs, a warning is
displayed:
No handlers could be found for logger "jenkins_jobs.modules.NAME"
Set up a logger with default configuration in the base test
class. Now any logs will be displayed on the console.
Change-Id: Ib36afd5d96ff8e7fed110b6bedb6e281aac584f8
When you do not specify any description for a job, right now it creates a
new one overwriting whatever you had put there manually. Now when
setting the configuration option 'keep_descriptions' to True, it will
only overwrite the description if you specified one explicitly in the
yaml.
That way you can avoid specifying any description and it will not
overwrite the ones you put there manually through the jenkins ui.
Added a couple of tests for it also, and extended the tests to allow custom
configuration by adding a *.conf file for it
Change-Id: I408f5ee06a6939a8cb8f4f2e6c6e0d060462259c
Signed-off-by: David Caro <dcaroest@redhat.com>
for improved readability.
Manually clean up some hard-to-read XML code in
jenkins_jobs/modules/publishers.py that was trying to do a lot on one
line.
Change-Id: Ica0065aae6f2fbaf8755bd8b5d3dea8c7d5a9cb0