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

Running build disappears forever when changing job configuration

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None
    • Windows server, using built-in Winstone, perforce plugin installed.

      I have an application that needs to modify job configurations. I have tried both of these approaches:

      • POSTing the new configuration to /job/JOBNAME/config.xml
      • Editing config.xml in the filesystem and GETting /reload

      In both cases, the configuration change works successfully, no problem. Jenkins seems to be happy.

      BUT HERE'S THE BUG: If a build happens to be in progress at the time of the configuration change, it totally disappears out of UI existence. Gone from the build history. A subsequent build shows a gap in the build numbers (for example ...#27 #28 #30... no more #29). The build still seems to complete okay, and its directory under builds is there, but the UI shows nothing.

      Changing the configuration interactively using the web form does not show the same symptom.

          [JENKINS-12171] Running build disappears forever when changing job configuration

          Jeremy Frank added a comment -

          Note: If I completely restart Jenkins, by shutting down and starting up the service, the missing build re-appears. (Of course, doing that each time is unacceptable, just trying to help focus the debugging.)

          Jeremy Frank added a comment - Note: If I completely restart Jenkins, by shutting down and starting up the service, the missing build re-appears. (Of course, doing that each time is unacceptable, just trying to help focus the debugging.)

          kutzi added a comment -

          Sound like a duplicate of JENKINS-3265

          kutzi added a comment - Sound like a duplicate of JENKINS-3265

          Jeremy Frank added a comment -

          Thanks kutzi. I tried to search for an existing issue first, but had only found issues dealing with bad xml.
          I added my additional information into that issue. It has been open for almost two years now... ugh... I'm evaluating Jenkins right now and having a major bug open for that long doesn't look good at all!

          Jeremy Frank added a comment - Thanks kutzi. I tried to search for an existing issue first, but had only found issues dealing with bad xml. I added my additional information into that issue. It has been open for almost two years now... ugh... I'm evaluating Jenkins right now and having a major bug open for that long doesn't look good at all!

            Unassigned Unassigned
            jfrank Jeremy Frank
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: