The content of this article has moved to the new documentation site.
Backup and Store Jenkins Jobs and Configuration in Source Control such as GIT or SVN
The content of this article has moved to the new documentation site.
Comments
2 comments
Two questions:
1) Why the "multibranch" pipeline? Wouldn't the plain pipeline work?
2) Where is the list of files that need to be saved? If the pipeline job is going to collect the files, we need information on which files.
Perhaps the strategy is to take the latest zip or tar.gz file created by the backup job and update those in the scm. If so, it would store all the hpi and jpi files for plugin AND why would you need a list of plugins with versions. Further, hpi, jpi and war files aren't really good subjects for inclusion in an scm (as aren't most binary files). So, if the strategy is to use the backup zip/tar.gz, which files should be left out.
I think this article needs some more detail so everyone doesn't have to duplicate the efforts.
shouldn't have to setup a bunch of stuff to get an undo / history of the jobs configuration. I just lost a full job that I have been working hours on. Yes I have backups but they are nightly so all of today's work is lost not just the last changes, also dont want to restore everything just 1 job config. This was due to a bad VPN link messing up on the save call. I dont understand how a bad save deletes all contents from the config.
I hope that CB or Jenkins teams work out a more integrated solution to save job versions and revert.
Please sign in to leave a comment.