![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
15/Nov/13 9:27 PM
|
|
Description:
|
To help unattended reocvery from startup failure, introduce the following functionalities:
- If Jenkins fails to complete the bootup sequence, produce a marker file that captures the failure. If the boot sequence succeeds, remove this file.
- If Jenkins fails to complete the bootup sequence, evaluate $JENKINS_HOME/boot-failures.groovy.d/* in the lexicological order
These user-supplied script can capture additional details, raise alerts, restart Jenkins (possibly after doing any other corrective actions.)
We should also count the repeated failures to boot, so that these scripts can try progressively aggressive measures.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Kohsuke Kawaguchi
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
