The tar command used do get the versioninfo content does not just
return empty when versioninfo is absent: it fails, triggering
set -e protection and resulting in the whole script failing. Fix
makes sure the command is successful (by || true) even when it
returns nothing.
Fixes bug 1018820
Change-Id: I3605d070f1d8f5bb39f5751f7c9a8b4f78a7701b
Only run the checks when a patch is uploaded, for now.
We will turn them on as gating tests when we are sure
they pass.
Change-Id: Ieb8f16d3193179789c15b15def53b3c093011557
python-novaclient tarballs should be in nova/tarballs.
Add a project parameter to the tarball publisher to handle that,
and update the yaml accordingly.
Change-Id: I184bd4b43e7cc86574ec011e8b2cf0cd14569553
The version of node.js packaged by ubuntu does not seem to play nice
with require-kernel and etherpad-lite. Go back to compiling version
0.6.16 of node.js which is tested and appears to be working.
Change-Id: Ib9bda5d7acbda06561398a0c715b28e46edb531d
Switches gerrit to the new build which include the row-colours patch.
After this goes in I'll make the config changes to turn it on.
Change-Id: I62f38367d891c80e9a586dc83a298f7cf7e18702
Update node definition for etherpad.openstack.org to include bits
from the etherpad_lite module. This will install etherpad-lite
with nginx as a reverse proxy and mysql as the DB.
Change-Id: I5a2e3f45a24c7d1c4749b2201c58d0e1eb134f53
Set custom pad.js file to mode 0644. Add nginx config for Etherpad-Lite
to sites-available then symlink to that from sites-enabled. Use Ubuntu
packages for Node.js and NPM instead of building from source (Precise
appears to have fairly recent packages that work).
Change-Id: I752a10ea32b462ef0cc8a5a515dd44c9390a4776
This is the first in a series of changes to alter the way modules
are handled.
This change removes the module section from yaml. Instead, all files in
modules/ are imported, and a 'register' function is called if it exists.
The register function can add (any number of) module classes to a module
registry. The registry will also keep track of helper functions for use
by other modules, and the register function can add those.
This sets up the ability for a module other than the 'builders' module to
register builders. Eventually, we should be able to move all OpenStack
specific builders, publishers, etc outside of the base modules; instead
we would just register an 'openstack_pep8' builder in a module of our own
that the job filler would know to invoke.
The API for modules is slightly changed, adding a root_xml method to handle
the different project types, a handle_data method for modules that want
to modify the yaml data structure before any XML is generated, and a data
parameter is added to the generate_xml method. Ideally, we will migrate
those modules that count on having a centrally stored data object to using
the one passed into this method to allow maximum flexibility. I also
envision some project-level yaml attributes to be moved closer to the
handlers that use them.
This change does inadvertently alter the XML produced. Here is the result
of test.sh: http://paste.openstack.org/show/18585/
In all cases, those are inconsistencies in the YAML that are corrected
by this change. Some jobs included an empty triggers vector (due to
module trigger_none) while others did not, so there was no way to satisfy
both behaviors. The added postbuilder section in the gerrit maven job is
there because the job specified postbuilders, but did not include the
postbuilder module. I believe the resulting XML is more desirable.
Change-Id: Ib38222e6bfc9d5b55aa497669d7023c7aaf4b7bc
Move configuration of Zuul parameters to a job filler module.
Note: I've used "triggers:" instead of "trigger:"; I'd like to
move the other triggers to use that and be more like the
"builders:" section.
Change-Id: I28af1f795f4e304faaf0e687bc3fdc76949a7664
