search

timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-30480] documentation of any change in build configuration #7491

Open timja opened 9 years ago

timja commented 9 years ago

In our case, we want to know every change. Because if you change the build config, you can not back to an older version of build configuration. This would it make easier to understand why older build are failed. This would allow to move back to an older build configuration. I am not sure, but this could also be good for a "EN ISO 9001" certification.

Originally reported by arbeita, imported from: documentation of any change in build configuration
  • status: Open
  • priority: Minor
  • resolution: Unresolved
  • imported: 2022/01/10
timja commented 9 years ago

cobexer:

Should be possible with: https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin

timja commented 9 years ago

arbeita:

I use now the line:
copy %JENKINS_HOME%jobs%JOB_NAME%\config.xml %JENKINS_HOME%\jobs%JOB_NAME%\builds%BUILD_NUMBER%\

but you have no ability to reactivate or view it.

timja commented 9 years ago

cobexer:

I just noticed that there is a plug-in that does exactly that: https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin plus it allows to view the difference and revert to a specific version.

timja commented 9 years ago

arbeita:

I installed the plugin, and will try it. thx for this information