Dear developers, I just performed two maintenance tasks on our Jenkins system.
Task 1: Job configuration history. I installed the plugin "JobConfigHistory" [1] which keeps track of all changes to the configuration of Jenkins's jobs. From now on, we can view, compare, and restore older versions. I performed a "Save" on all jobs (without any changes, of course) in order create the first version of each configuration as a baseline for the next actual changes. Task 2: Jenkins scripts under version control. I created a new repository named "saros-ci-scripts" [2] which, as of now, contains Jenkins's "scripts" folder. Changes will go through Gerrit. There is also a new job called "CI-Script-Deploy" which monitors the Git repository for changes and replaces the scripts if need be. I used the two locks PLUGIN_BUILD and STF_RUN in this job to make sure that the scripts won't get changed while another job accesses them. Feel free to give feedback or take action. Everything is a bit safer from now on :) Best Regards, Franz [1] https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin [2] git clone http://saros-build.imp.fu-berlin.de/gerrit/saros-ci-scripts.git ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
