Status: Open (View Workflow)
A requested feature on Docker official jenkins image is ability to created derived images with custom plugins. But as jenkins_home is a volume the Docker image can't be built with custom plugins / hook scripts.
This feature request is about introducing, in addition to jenkins.war:/WEB-INF and JENKINS_HOME, a supported directory where jenkins would pick-up plugins and hook scripts.
- is related to
JENKINS-25153 Update ssh-slaves and ssh-credentials plugins in war file
Changing jenkins.war require to rebuild the war then generate a fresh new docker image with this custom binary, not relying on official one.
Assuming jenkins do support a "patch" directory in addition to bundled-in-war and jenkins_home, it's easier for end-user to create a Dockerfile like this :
run curl -L https://updates.jenkins-ci.org/latest/git.hpi -o /opt/jenkins_patch/plugins/git.hpi
Given that the original request in
JENKINS-25153, about creating a customized WAR with different bundled plugins, has been resolved, is this issue still valid for some other reason?
Creating a customized WAR? It is pretty easy to do and lets you precisely customize what is considered “bundled” by the Plugin Manager UI.
I'm confused about the status of this ticket. It seems to me that I'm deriving a custom docker image from the official one, installing plugins and hooks.
The only issue I faced was https://github.com/jenkinsci/docker/issues/563
"Docker image can't be built with custom plugins / hook scripts." sounds rather scary to me.
What's wrong with changing jenkins.war?