Hi All We are trying to improve our build server setup and are trying to solve the problem that users can change the configuration of their builds through the UI, but those changes are not stored in source control, so it is hard to determine what has changed and who made those changes. Additionally (and maybe even more importantly) it is hard to rebuild an old version of the software because that may require a different job configuration. I know there are several plugins to handle backing up configuration changes to VCS / etc. but those backup to their own repositories (if they work) and we want the configuration for a build job to be stored with the source code for that build job, not in a separate repository. Because if we store the definition for the build job and the source code in the same location we could easily recreate a build environment as it was for that specific commit.
One option would be to use the Job-DSL plugin to create the jobs from a configuration file that is in VCS. The only catch with that would be that editing the configuration would require users to update the configuration text file which I suspect would increase the chance of errors and also makes it harder for the users to test configuration changes. Ideally we would like to keep the UI as the way to edit configurations but then just have that write to the configuration file. I suspect this problem cannot be solved with our current version of jenkins (latest LTS 1.642.2) but I'm wondering if there are any plugins / combination of plugins / other apps that could make this possible? thanks Petrik -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/50ec9175-61a6-4189-8a94-71c082c89a8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
