When some of the tests are run, pbr is installed in the
current directory leaving a pbr*.egg directory. We never
want to check that into git, so ignore it.
Change-Id: I6e8f6bc838e0afa77dd7dce351e603f0b5f8ea76
This commit fixes bug 1182154
The maven workflow for versioning and deployment is at odds with how
we like to do it. For versioning, our convention is to get info
from SCM to set the project build versions. For deployments
to remote repositories we prefer to use curl instead of mvn deploy
due to maven security vulnerabilities. Our python builds
have already been setup to set package versions from SCM and
deploy to pypi using curl so this commit is to make
maven versioning and deployments similiar our python
versioning and deployment workflow.
This commit does the following:
Setup a project version string as an environement variable
so we can pass it to maven builds. The version string is
retrieved from information in git. This makes the build versioning
workflow similar to how we build python packages.
This setup expects a variable called '$project-version' in
the root 'version' element (i.e. <version>${project-version}</version>)
of the maven project's pom.xml file.
For general (throw away CI) builds we do the following:
1. generate a package 'myplugin.hpi' with version '1.3.0.4.a0bc21f'
in the MANIFEST.MF file. The '4' is the number of commits since
last tag.
2. publish 'myplugin-1.3.0.4.a0bc21f.hpi' to tarballs.o.o
For release builds we do the following:
1. generate a package 'myplugin.hpi' with version '1.3.1'
in the MANIFEST.MF file.
2. publish 'myplugin-1.3.1.hpi' to tarballs.o.o
3. publish 'myplugin-1.3.1.hpi' to repo.jenkins-ci.org
Passes the jenkins credentials from hiera to the pypi slave so
we can use it to deploy released plugins to repo.jenkins-ci.org
Creates a generic jenkinsci-upload job that will deploy
released jenkins plugin artifacts to a remote repository with
user credentials from hiera. It will use the same curl deployment
method as the pypi-upload job.
Change-Id: If1306523a28da94ee970d96b7a788ca116348de7
Reviewed-on: https://review.openstack.org/31875
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
This commit adds a post job to deploy the gearman-plugin
artifact (gearman-plugin.hpi) to tarball.o.o
.gitignore
ignore auto generated eclipse project file
modules/openstack_project/files/jenkins_job_builder/config/gearman-plugin.yaml
the new gearman-plugin-tarball job (copied from gerrit.yaml)
modules/openstack_project/files/zuul/layout.yaml
hook job into build system
Change-Id: I59d9e3b446646fd879d827fd0aeb35356865f4d0
Reviewed-on: https://review.openstack.org/24663
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
* .gitignore: This adds the .test directory created by some config
testing commands, and also updates the egg info directory to
reflect the recent project rename.
Change-Id: Id0e4ea46bc90b37b9c427007a540e0485e640aad
Reviewed-on: https://review.openstack.org/22221
Reviewed-by: Anita Kuno <akuno@lavabit.com>
Reviewed-by: Khai Do <zaro0508@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Task list is at https://etherpad.openstack.org/api-site-structure.
Patchset updates the ftp copy in the publishing portion of the
api-quick-start build.
Patchset addresses comments, also indicates
doc-publisher-site: api.openstack.org
Patchset adds build for the api reference page.
Rebase against master.
Fixes the list of jobs and changes the name of the old api-site job
to ensure no duplication and clarity of which job is which.
Fixes errant tab.
Change-Id: Ifbefa75ba9bf63ca36e53dfda668fa9831203c06
Reviewed-on: https://review.openstack.org/15111
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
The existing ci-docs job is a one off job that was configured by hand.
Define the ci-docs job as a Jenkins Job Builder job using the existing
project-docs utilities.
To make the existing utilities work within the puppet repo the doc files
have been moved to doc/source, setup.cfg added to build docs in the new
dir, setup.py builds openstack-ci-puppet (instead of nova), tox now has
a venv virtualenv, and the .gitignore has been updated appropriately.
Change-Id: Ic0f291af181b4ef8eff62c5ec7cf3ccfa5b79800
Reviewed-on: https://review.openstack.org/13729
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
A trivial fix to keep git happy
Change-Id: I112bb133fb24657403aac584e2d5bb9d84ac6c2b
Signed-off-by: Paul Belanger <paul.belanger@polybeacon.com>
Reviewed-on: https://review.openstack.org/13602
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Update to reflect recent changes to Jenkins Jobs Filler
Also add .gitignore entry to ignore the sphinx html output
Change-Id: Id18ac09197f3449e5843bc97cf234dd7d3c51034
This uses a python script with modules for parts of the XML. The parameters for the projects are provided using YAML scripts.
It also includes a Jenkins API module to directly inject jobs into Jenkins without requiring a restart/reload as well as a memory of which jobs have been pushed to Jenkins.
It is currently configured to replace the original Jenkins Jobs in StackForge.
What it won't yet do:
1. Delete jobs (although it isn't far off being able to)
2. check-* jobs (need to modify the trigger_gerrit module to support that)
Documentation to follow
Fixes bug #995599
Change-Id: I2a67ee2d9e8f43cbced56425ef7f80dc6a30a814
Ramy Asselin