Since 1.30, Copy Artifact supports specifing the projects that are allowed
to copy artifacts for a given project in the general job properties.
Change-Id: I5a9de21f449e98d08ec9303d55021d6a661257d4
Since the conversion to PBR it looks like there is an omission of
the [files] section in the setup.cfg. This means that the metadata
was installed for the jenkins-job-builder but the package with the
python code was not. This patchset adds the [files] section in to
correct this oversight.
Closes-Bug: 1292745
Change-Id: Ia1b8f022a66574ee371587d49bb46c43d80f01ba
Add support for the 'Clone Workspace SCM' plugin that allows to use the workspace
of a project as the SCM of an other project.
Change-Id: I8467ace24665855dab606d6e52a1c130cd2929af
I found out pbr to be a bit nicer when it comes to edit files. AFAIK
most OpenStack project are using it, so I guess Jenkins Job Builder can
be pbr based as well.o
Basically:
* moved everything from setup.py to setup.cfg
* sorted entries while at it
* require pbr module using the same version limits used by Zuul
* enable pbr.warnerrors
* testenv.usedevelop = True or build_sphinx can not find entry points
* move requirement files to root of repository (we had them in /tools/)
Change-Id: I44ee8910ad4fe4eebb7337951efa31baff4281fe
This is a Jenkins plugin that will publish Jenkins Job run events
(start, complete, finish) to a ZMQ PUB socket.
Change-Id: Id238033796e6905e18a777fc85c789ff6cf4f59d
python 2.6 ConfigParser has problems interpolating the None type so setting defaults to
empty string instead.
Closes-Bug: #1259631
Change-Id: Iceec1d8c3b77fd64ac54e02653800ad422778bdf
The email-ext publisher was always sending email using the default
content type which is server wide. This tiny patch let us overwrite the
content-type on a job basis.
The YAML possible values are 'html' or 'text' to force the content-type
to one of the two modes.
Change-Id: Id66bc3369332c389dfb6318113392694a4f98aad
The Sphinx documentation now make use of the `program-output` plugin
which would invoke commands to generate inline documentation. Ex:
program-output:: zuul --help
program-output:: zuul enqueue --help
We want the resulting output to correspond to Zuul source code, not the
command which is currently installed on the host running the doc. On my
setup sphinx would die out because it cant find the command 'zuul'.
The new tox environement 'doc' runs sphinx in a virtual env which will
have the proper zuul command.
The generated doc is not written under the /.tox directory but to
/doc/build/html for convenience.
Example usage:
tox -edoc && open doc/build/html/index.html
Change-Id: Ib0170f94bb2c09eb60e555a32e101e2e0959b18e