[
https://issues.jenkins-ci.org/browse/JENKINS-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163234#comment-163234
]
Gary Sorhaindo commented on JENKINS-13239:
------------------------------------------
Many thanks for your prompt response Thomas. And I agree with what you say - a
different message, which is abortable would be great, if this is possible.
But in the mean time - you said that "you cannot fall in a situation where a
job modifies data while the backup is running".
With regard to that statement, what happens if I de-select the "Wait until
Jenkins/Hudson is idle to perform a backup" option that was introduced in Thin
backup 1.6? When using this option, do I risk making corrupt backups?
Thanks in advance.
Gary
> ThinBackup puts Jenkins into Shutdown (repeatedly) . . . revisited
> ------------------------------------------------------------------
>
> Key: JENKINS-13239
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13239
> Project: Jenkins
> Issue Type: Bug
> Components: thinBackup
> Affects Versions: current
> Environment: Win7, approx 100 Projects, incremental backups weekdays,
> full backup Sunday
> Reporter: Frank Merrow
> Assignee: Thomas Fürer
> Attachments: shutdown.log
>
>
> One of my fellow workers claimed thinBackup was taking Jenkins down, sure
> enough I found that the case myself this morning.
> Shutdown could not be cancelled (it would go down, but immediately be
> reasserted). ThinBackup had some messages about waiting for quiet mode, but
> there also seemed to be an exception related to cancelling shutdown, scanning
> with my non-Java eye, it wasn't clear it the exception was thinBackup related
> or not.
> End of Jenkins log provided
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
