github.com/openstack-ci was moved to github.com/openstack-infra
homepage references should point to git.o.o/cgit/openstack-infra
This change updates the above references accordingly.
Change-Id: I4d3591f228b10de050a129ae7af99485f50edab5
pypi is not showing info from README.rst. This change adds a reference to the readme
so that it will appear on pypi.org upon a release of jjb.
Change-Id: I13b8d003d358bc1398058bbdbb5bb984ead2679b
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
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 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
Lets one execute a shell/groovy script or any builder AFTER the build
has complete.
https://wiki.jenkins-ci.org/display/JENKINS/PostBuildScript+Plugin
All existing builders should be supported since this patch call the
usual dispatcher.
Change-Id: Ide059ec9fd0e556f0c50ec992a6021eb5afb261c
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
With help from clarkb in #openstack-infra and openstack-ci/gerritbot,
I've manage to update our versioning to be inline with other openstack
projects. This is another step towards creating our OS packaging.
Change-Id: If3f44b939ee0a3c9c4dfa1d9f83ae14a8285ba5f
Signed-off-by: Paul Belanger <paul.belanger@polybeacon.com>
Reviewed-on: https://review.openstack.org/15335
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Tested-by: Jenkins
Move test.sh to the tools directory.
Move parameters and notifications to their own modules; even
though they are implemented as Jenkins properties, they make
more sense as separate entities in the job builder, because
that's they way they are specified in the YAML. All three
modules that touch the properties xml object know how to
create it if it's missing.
Change-Id: I4b42ff10a93fd3ed98f632b58e47f3e0e45086d6
Reviewed-on: https://review.openstack.org/12741
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins