The Gatekeeper, or a project gating system
Go to file
James E. Blair b98fcdb499 Set merge result correctly on exceptions
If an exception was received during a report, _reportItem would
erroneously indicate that it had been reported without error.
If a merge was expected, isMerged would be called which may then
raise a further exception which would stop queue processing.

Instead, set the default return value for _reportItem to True
because returns a true value on error.  This will
cause the change to be marked as reported (with a value of ERROR),
the merge check skipped, and the change will be quickly removed
from the pipeline.

Change-Id: I08b7cee486111200ac9857644d478727c635908d
2013-08-27 09:01:32 -07:00
doc Use the 'resolve' merge strategy by default 2013-08-27 09:01:31 -07:00
etc Support multiple triggers 2013-08-01 11:56:52 -07:00
tests Re-launch a job if the worker fails to run it 2013-08-23 15:17:33 -07:00
tools Add manual job triggering script. 2013-07-08 22:16:11 +00:00
zuul Set merge result correctly on exceptions 2013-08-27 09:01:32 -07:00
.gitignore Migrate to testrepository. 2013-06-27 01:49:59 +00:00
.gitreview Updated .gitreview location 2012-12-16 20:34:13 +00:00
.mailmap Fix pep8 E127 violations 2012-09-26 14:23:10 +00:00
.testr.conf Add ability to skip log capture. 2013-07-02 17:47:23 +00:00
LICENSE Initial commit. 2012-05-29 14:49:32 -07:00 Migrate to pbr. 2013-06-25 19:04:30 +00:00
NEWS.rst Add a timer trigger 2013-08-01 11:57:19 -07:00
README.rst Drop Jenkins.getBestBuildURL() method 2013-05-05 21:58:29 +00:00
TESTING.rst Support multiple triggers 2013-08-01 11:56:52 -07:00
requirements.txt Require gear 0.4.0 2013-08-27 09:01:31 -07:00
setup.cfg Enable warnerrors for pbr to catch Sphinx warnings 2013-07-19 21:26:03 -04:00 Migrate to pbr. 2013-06-25 19:04:30 +00:00
test-requirements.txt Include discover in test requirements. 2013-07-18 14:19:20 -07:00
tox.ini Make E123 pep8 clean 2013-07-20 20:40:41 -04:00



Zuul is a trunk gating system developed for the OpenStack Project.


To get the latest code, see:

Bugs are handled at:

Code reviews are, as you might expect, handled by gerrit. The gerrit they use is

Use git review to submit patches (after creating a gerrit account that links to your launchpad account). Example:

# Do your commits
$ git review
# Enter your username if prompted