Hi, Currently, my Jenkins is used very frequently by teams and it's dangerous to update it directly in the production environment. Do you have a specific methodology to update Jenkins before apply updates in the production environment ?
I plan to run a Jenkins (with a specific user and http port) on the same machine of my Jenkins master which will allow me to easily import jobs configurations (at least the most representative) from my production environment to the 'pre-production' environment and test Jenkins and its plugins updates before apply them to production. However, I can't just copy them and start a build directly. Many have specific configuration to the production envionment (email notification, release configuration, number of build to preserve ...). So, I have to change them before run them. Automating this type of task seems difficult. Furthermore, once pre-production is up to date and representatives jobs has been tested, if I want to apply these updates to production, I must repeat the same actions on my production envionment which may be a potential source of problems. It seems easy for plugins (copy the $JENKINS_HOME/plugins directory from pre-production to production), but does not seems reliable for Jenkins itself. Has anyone ever looked for a strategy to create a pre-production environment for Jenkins ? Thanks in advance, Michaël Pailloncy
