• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: core, jobconfighistory-plugin
• Labels:

  None
• Environment:

  Jenkins: v2.73
  Job Configuration History Plugin: v2.16
  Master OS: Amazon Linux AMI release 2017.03
  Slave OS: Amazon Linux AMI release 2017.09

1. 

   Screen Shot 2018-01-31 at 10.28.24.png

   83 kB

   2018-01-31 10:43

2. 

   Screen Shot 2018-01-31 at 10.28.24.png

   116 kB

   2018-01-31 10:41

3. 

   Screen Shot 2018-01-31 at 10.28.45.png

   30 kB

   2018-01-31 10:34

[JENKINS-48755] Build environment not persisting for jobs on restart

Leo Brookes created issue - 2018-01-02 11:59

Leo Brookes made changes - 2018-01-02 11:59

Summary

Original: On restart, build environment is lost for jobs

New: Build environment not persisting for jobs on restart

Leo Brookes made changes - 2018-01-02 14:25

Description

Original: When I restart my Jenkins master server I have noticed that the Build Environment config for any jobs that have had that section updated since the last restart disappear, such as pre-SCM buildsteps and Artifactory dependency resolution. I am aware that Jenkins runs a "reload configuration from disk" on restart which may explain why the configuration isn't persisted. I've tagged the Job Config History plugin as I've been using it to track the history of the files and whether the lost config can be easily restored, but bizarrely the config in question is nowhere to be found in any of those previous versions despite it being added and saved successfully before the last restart. This appears to affect multiple project types; I've observed it in both Maven and Freestyle jobs.

New: When I restart my Jenkins master server I have noticed that the Build Environment config for any jobs that have had that section updated since the last restart disappear, such as pre-SCM buildsteps and Artifactory dependency resolution. I am aware that Jenkins runs a "reload configuration from disk" on restart which explains why the configuration isn't persisted. I've tagged the Job Config History plugin as I've been using it to track the history of the files and whether the lost config can be easily restored, but bizarrely the config in question is nowhere to be found in any of those previous versions despite it being added and saved successfully before the last restart. This leads me to believe that Jenkins is not saving  This appears to affect multiple project types; I've observed it in both Maven and Freestyle jobs.

Leo Brookes made changes - 2018-01-02 14:44

Description

Original: When I restart my Jenkins master server I have noticed that the Build Environment config for any jobs that have had that section updated since the last restart disappear, such as pre-SCM buildsteps and Artifactory dependency resolution. I am aware that Jenkins runs a "reload configuration from disk" on restart which explains why the configuration isn't persisted. I've tagged the Job Config History plugin as I've been using it to track the history of the files and whether the lost config can be easily restored, but bizarrely the config in question is nowhere to be found in any of those previous versions despite it being added and saved successfully before the last restart. This leads me to believe that Jenkins is not saving  This appears to affect multiple project types; I've observed it in both Maven and Freestyle jobs.

New: When I restart my Jenkins master server I have noticed that the Build Environment config for any jobs that have had that section updated since the last restart disappear, such as pre-SCM buildsteps and Artifactory dependency resolution. I am aware that Jenkins runs a "reload configuration from disk" on restart which explains why the configuration isn't persisted. -I've tagged the Job Config History plugin as I've been using it to track the history of the files and whether the lost config can be easily restored, but bizarrely the config in question is nowhere to be found in any of those previous versions despite it being added and saved successfully before the last restart.-  This appears to affect multiple project types; I've observed it in both Maven and Freestyle jobs.

Leo Brookes made changes - 2018-01-02 14:59

Description

Original: When I restart my Jenkins master server I have noticed that the Build Environment config for any jobs that have had that section updated since the last restart disappear, such as pre-SCM buildsteps and Artifactory dependency resolution. I am aware that Jenkins runs a "reload configuration from disk" on restart which explains why the configuration isn't persisted. -I've tagged the Job Config History plugin as I've been using it to track the history of the files and whether the lost config can be easily restored, but bizarrely the config in question is nowhere to be found in any of those previous versions despite it being added and saved successfully before the last restart.-  This appears to affect multiple project types; I've observed it in both Maven and Freestyle jobs.

New: When I restart my Jenkins master server I have noticed that the Build Environment config for any jobs that have had that section updated since the last restart disappear, such as pre-SCM buildsteps and Artifactory dependency resolution.  -I've tagged the Job Config History plugin as I've been using it to track the history of the files and whether the lost config can be easily restored, but bizarrely the config in question is nowhere to be found in any of those previous versions despite it being added and saved successfully before the last restart.-  This appears to affect multiple project types; I've observed it in both Maven and Freestyle jobs.

Leo Brookes made changes - 2018-01-31 10:34

Attachment

New: Screen Shot 2018-01-31 at 10.28.45.png [ 41298 ]

Leo Brookes made changes - 2018-01-31 10:41

Attachment

New: Screen Shot 2018-01-31 at 10.28.24.png [ 41299 ]

Leo Brookes made changes - 2018-01-31 10:43

Attachment

New: Screen Shot 2018-01-31 at 10.28.24.png [ 41300 ]