[
https://issues.jenkins-ci.org/browse/JENKINS-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161531#comment-161531
]
marlene cote commented on JENKINS-13123:
----------------------------------------
yes, please fix this or add a big warning! I just had 3 builds sort of killed.
they remain listed in the main dashboard and look like they are running, but
when you click on them you get a 404 error. the error messages look like the
slave is restarted or something because there are lots of no such file or
directory type errors.
also, the build that was running actually disappears from the list of builds.
so if I was running build 4, then build 5 would get kicked off by the unshelve,
and build 4 would disappear from the list. however, the console log exists
because the build email shows the no such file or directory errors.
> 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
>
> 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
