Antoine Musso ce333845ea doc about a post-merge pipeline ... 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		2012-10-24 16:40:06 +00:00
..
conf.py	Add documentation.	2012-06-08 19:17:28 -07:00
gating.rst	Move terminology from "queue" to "pipeline".	2012-09-20 20:37:54 +00:00
index.rst	Add documentation.	2012-06-08 19:17:28 -07:00
launchers.rst	honor ZUUL_UUID where UUID is used	2012-10-12 16:09:04 +00:00
triggers.rst	Add documentation about serving Zuul refs.	2012-10-05 16:49:41 +00:00
zuul.rst	doc about a post-merge pipeline	2012-10-24 16:40:06 +00:00