Container startup does not allow plugin backups
Feature description
The ability to use a Docker Volume mounted at /var/jenkins_home, so that configurations and plugins can persist container lifespans.
Use cases
Docker volume mounted at /var/jenkins_home allows the persistence of Jenkins configurations and plugins. On premises deployments can make their pipelines more robust to interruption through use of Docker volumes. When we stop/start this container now, plugins are replaced with whatever is in /tmp/plugins, which is populated at image building then deleted on Jenkins.sh invocation (container entrypoint). Plugins added or updated break upon stop/start. It is not hard to re-download then reconfigure, but adds manual steps to recovery. Jenkins war file also set to location outside of /var/jenkins_home which is different than typical FOSS deployments. The Jenkins war file then either requires its own volume to persist, or requires Jenkins update upon opening the service.
Benefits
Removal of manuals steps for container/service recovery.
Requirements
Creation of Docker Volume(s)
Links / references
In /var/local/bin/jenkins.sh - This feature could be completed by moving the JENKINS_WAR location under /var/jenkins_home and changing/removing the Plugin backup on line's 12 & 13. The following image is behaving as expected in our local deployment of this container.
Definition of Done
-
Feature has been implemented
/cc @ironbank-notifications/feature