-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 1.647 installed as Windows Service
When Jenkins is installed as Windows Service the queue is not persisted on Safe Restart.
Steps to reproduce
- Fresh install Jenkins on Windows as a Windows Service
- Remove all available executors (set it to 0)
- Configure a job
- Run the job
- The job must be put in queue, and must not run because there are no available executors.
- Safe restart Jenkins
Expected result
- On safe restart the queue.xml file should be created for the queue to be restored on start
- Ultimately the queue should be restored on start
Actual result
- No queue.xml file is created
- The queue is not restored after restart
This works on Mac OS X, and works if running a Jenkins instance with Maven HPI Plugin or similar on Windows.
- is duplicated by
-
JENKINS-41775 Build Queue is cleared after restart
-
- Resolved
-
- is related to
-
JENKINS-30909 queue.xml only gets persisted on successful shutdown
-
- Resolved
-
- relates to
-
JENKINS-34281 Queue isn't saved on any shutdown
-
- Resolved
-
-
JENKINS-44589 Missing calls to Jenkins.cleanUp
-
- Resolved
-
This problem happens because Jenkins.cleanUp() method is not being called on WindowsServiceLifecycle.restart() method. It is only called in the restart implementation of UnixLifecycle and SolarisSMFLifecycle. It is also called inside WebAppMain.contextDestroyed().
Will create a pull request.