The Gatekeeper, or a project gating system
ce333845ea
Reacting on `change-merged` event definitely requires --force-message to be passed to `gerrit review` or Gerrit will complain the change is closed whenever it is also passed --verify X or --code-review Y. Added a simple example to setup a post-merge independant pipeline. Left a note about ``change-merged`` lacking the commit sha1. One should instead use the ``ref-updated`` when the commit sha1 is needed. Close #1067083 Change-Id: Ic402a0048651d10ac619010fdfd58725374368cd Reviewed-on: https://review.openstack.org/14476 Approved: James E. Blair <corvus@inaugust.com> Reviewed-by: James E. Blair <corvus@inaugust.com> Tested-by: Jenkins |
||
---|---|---|
doc | ||
etc | ||
tests | ||
tools | ||
zuul | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
AUTHORS | ||
LICENSE | ||
README | ||
setup.cfg | ||
setup.py | ||
tox.ini | ||
zuul-server |
# Zuul Zuul is a trunk gating system developed for the OpenStack Project. ## Contributing To get the latest code, see: https://github.com/openstack-ci/zuul Bugs are handled at: https://launchpad.net/zuul Code reviews are, as you might expect, handled by gerrit. The gerrit they use is http://review.openstack.org 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 promped