Details
-
New Feature
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
During the hackathon we have created https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10 . Now it needs to be expanded to Java 11 and added to the common release flows
Acceptance:
- Create official Docker packaging for Java 11 which runs OOTB
- Update jenkins.io documentation to reflect the new repo: https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker
Approach 1:
- Promote https://github.com/oleg-nenashev/jenkins-blueocean-experimental to jenkinsci
- Setup new DockerHub repo with Automatic build, e.g. jenkins/blueocean which is unused
- Define naming strategy
- Create Java 8 and Java 11 branches there, similar to the source repo
Approach 2:
- We could replace https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10 by the new file and make it a part of the Default build by the Docker team
- Update scripts to do build/deployment of the second Dockerfile
It needs agreement with the BlueOcean team.
Attachments
Issue Links
- relates to
-
JENKINS-52069 SEVERE: Failed to install Email Extension when running on Docker Java 10
-
- Closed
-
-
JENKINS-52280 Create experimental Java 11 Docker Packaging for BlueOcean
-
- Resolved
-
As I've expressed elsewhere, I tend to think this image should be discontinued. I would say the experimental one is actually enough.
IMO, it's really not great that we're providing many variants of Jenkins images. I think the Jenkins Project already has enough work with providing quality-guaranteed and maintaining the jenkins/jenkins different tags/variants, to also have "plugins" specific images like jenkins/blueocean.
So, as such, my recommendation would be to close this as WONTFIX.