-
Bug
-
Resolution: Duplicate
-
Critical
-
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.
- duplicates
-
JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
-
- Resolved
-
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.)