From f231fa2a736d94818c351f0d9a298eaef5c8217f Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Fri, 8 Feb 2013 12:28:53 -0800 Subject: [PATCH] Update zuul doc to cover SIGUSR1 behavior. Change-Id: I6dcd87a59d836dc22b67a2bee7c764e0b603a809 Reviewed-on: https://review.openstack.org/21543 Approved: Jeremy Stanley Reviewed-by: Jeremy Stanley Tested-by: Jenkins --- doc/source/zuul.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/source/zuul.rst b/doc/source/zuul.rst index 0c4d076a76..a971c8230a 100644 --- a/doc/source/zuul.rst +++ b/doc/source/zuul.rst @@ -516,3 +516,9 @@ stop executing new jobs, wait until all executing jobs are finished, reload its configuration, and resume. Any values in any of the configuration files may be changed, except the location of Zuul's PID file (a change to that will be ignored until Zuul is restarted). + +If you send a SIGUSR1 to the zuul-server process, Zuul will stop +executing new jobs, wait until all executing jobs are finished, +then exit. While waiting to exit Zuul will queue Gerrit events and +save these events prior to exiting. When Zuul starts again it will +read these saved events and act on them.