[
https://issues.jenkins-ci.org/browse/JENKINS-13239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163041#comment-163041
]
Thomas Fürer commented on JENKINS-13239:
----------------------------------------
hi Gary,
this the expected behavior of the current implementation. currently you cannot
fall in a situation where a job modifies data while the backup is running,
because the backup is only done in the quiet mode.
maybe i should work on a solution where a bring up another text message which
midge be abortable, which means no backup of you abort the quite mode. I need
to research how it can be done...
thomas
> 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
