Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13123

Unshelving reloads entire configuration

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: shelve-project-plugin
    • Labels:
      None
    • Environment:
      Shelve Plugin 1.3
      Jenkins 1.446
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          mcote marlene cote added a comment -

          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.

          Show
          mcote marlene cote added a comment - 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.
          Hide
          mcote marlene cote added a comment -

          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

          Show
          mcote marlene cote added a comment - 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

            People

            • Assignee:
              ashlux ashlux
              Reporter:
              rpetti Rob Petti
            • Votes:
              7 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: