|
||||||||
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 Configuration from Disk (or POSTing config.xml) loses info on running builds
jeremy.fr...@psion.com (JIRA) Wed, 20 Jun 2012 06:05:25 -0700
- [JIRA] (JENKINS-3265) Reload Configuratio... m...@favoritemo.com (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... m...@favoritemo.com (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... jeremy.fr...@psion.com (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... m...@favoritemo.com (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... m...@favoritemo.com (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... jeremy.fr...@psion.com (JIRA)
- [JIRA] (JENKINS-3265) Reload Configu... martin.danjo...@gmail.com (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 .