[
https://issues.jenkins-ci.org/browse/JENKINS-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161532#comment-161532
]
marlene cote commented on JENKINS-13123:
----------------------------------------
the slave log shows nothing interesting from what I can tell, but I include it
in case you see something. the unshelve was done at 11:18:xx. as you can see
fwd_red_int_ci build 8 was running. It got killed and build 9 got kicked off
which then had trouble communicating with the git repositories. The clone step
failed.
Apr 12, 2012 6:33:38 AM hudson.plugins.logparser.LogParserThread getLineStatuses
INFO: LogParserThread: Start parsing log part 0
Apr 12, 2012 6:33:38 AM hudson.plugins.logparser.LogParserThread getLineStatuses
INFO: LogParserThread: Done parsing log part 0
Apr 12, 2012 11:18:47 AM hudson.plugins.logparser.LogParserStatusComputer
computeStatusMatches
INFO: Local temp file:/tmp/log-parser_fwd_red_int_ci_build_8
Apr 12, 2012 11:18:47 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Start reading log part 0 in thread #0
Apr 12, 2012 11:18:47 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Done reading log part 0
Apr 12, 2012 11:18:47 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Start parsing log part 0
Apr 12, 2012 11:18:47 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Done parsing log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserStatusComputer
computeStatusMatches
INFO: Local temp file:/tmp/log-parser_fwd_red_int_ci_build_9
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Start reading log part 0 in thread #0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Done reading log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Start parsing log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Done parsing log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserStatusComputer
computeStatusMatches
INFO: Local temp file:/tmp/log-parser_fwd_red_int_ci_build_9
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Start reading log part 0 in thread #0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Done reading log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Start parsing log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Done parsing log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserStatusComputer
computeStatusMatches
INFO: Local temp file:/tmp/log-parser_main_int-opt_ci_build_21
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Start reading log part 0 in thread #0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserReader readLogPart
INFO: Done reading log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Start parsing log part 0
Apr 12, 2012 11:19:39 AM hudson.plugins.logparser.LogParserThread
getLineStatuses
INFO: LogParserThread: Done parsing log part 0
Pa
> Unshelving reloads entire configuration
> ---------------------------------------
>
> Key: JENKINS-13123
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13123
> Project: Jenkins
> Issue Type: Bug
> Components: shelve-project-plugin
> Environment: Shelve Plugin 1.3
> Jenkins 1.446
> Reporter: Rob Petti
> Assignee: ashlux
> Priority: Critical
>
> Unshelving projects appears to cause the entire Jenkins configuration to be
> reloaded from disk, which can break any currently running builds. Ideally,
> the unshelving action should load ONLY the project that's being unshelved,
> and nothing else.
> I know the Jenkins API supports loading specific project configurations, but
> I'm not sure if the same can be done for it's builds and changelogs. If it
> can't, then the user should be warned that unshelving is dangerous while
> builds are running.
--
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
