|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-3265) Reload Configuratio... [email protected] (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... [email protected] (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... [email protected] (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... [email protected] (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... [email protected] (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... [email protected] (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... [email protected] (JIRA)

Any application can halt without warning, due to power out, hardware defect, OS bugs, malicious software, you-name-it, even well-intentioned code in the application itself. Therefore important state information must be persisted upon every change. Anything else risks losing that data. So by this logic, I agree that saving the state of running builds is "eminently reasonable" as you say. You have my vote
.