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
-
Activity
Agreed. We should not have separate official images which merely preinstall some arbitrary plugin selection.
(A number of plugins build demo images showing the plugin being used in context on a sample project, which can be quite useful. Historically these have been uploaded to DockerHub, though I tend to regret this—in many cases you need special instructions to run the demo anyway, so it would be better to have people check out sources and make -C demo run.)
I think actually in the future, we can keep using Docker Hub, but on the new experimental Jenkins org there, cf. JEP-217 by Oleg. Because on this new home, people know already by design of the naming that things can be changed, breaking, etc. per its very experimental nature.
As commented in WEBSITE-474, I agree with deprecating the image. JENKINS-52069 is also a good justification for not advertising it
I also like the idea of retiring the image. We have a lot of people show up in gitter blueocean channel asking about general pipeline issues.
I think the docker image was great before blueocean made it cleanly into the update store, but its pretty stable these days, and can easily just get installed.
Not marking yet as WONTFIX, but I think this is where we are leaning towards.
Jenkins installation documentation for Docker guides the user to create their own Docker image that includes Blue Ocean and Pipeline plugins. The installation documentation does not refer to the blueocean Docker container.
Jenkins tutorials for build tools guide the user to create their own Docker image that includes Blue Ocean and Pipeline plugins. The tutorials do not refer to the blueocean Docker container. The tutorials are available for:
Jenkins documentation no longer references the blue ocean container, but the blue ocean container is currently delivering Java 11.0.13 running on Alpine 3.15.0. The blue ocean Docker container has been updated to use Java 11 as part of the August 2021 switch to use Java 11 in Docker images.
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.