Hi all, As a part of Jenkins & Java 10+ work, I have created a simple CD flow for Docker images so that we were able to quickly deliver patches in java10-support and java11-support branches. I have just added multi-stage Dockerfile <https://github.com/jenkinsci/jenkins/blob/java11-support/Dockerfile> build directly to the Jenkins core repository and then created an automatic build on DockerHub: jenkins/jenkins-experimental <https://hub.docker.com/r/jenkins/jenkins-experimental/> .
With such approach, the DockerHub build is triggered on any merge/push to the branch, so users get a new image within 30 minutes. It may be useful for trying fixes in Docker. There are 3 serious limitations: 1. Build happens before ci.jenkins.io completes the build/test cycle, so it is not 100% fine. Ideally it would be preferable to trigger the build after the incrementals (via webhook) or to build the image directly on ci.jenkins.io (package incrementals to Docker as a part of the build). 2. The build uses a base image from `jenkins/jenkins` "latest" or "stable" tags. So it uses the current release instead of the current Docker packaging which is about to go to the next release 3. There is no versioning, just latest tags. This is okay, but it may complicate analysis of issues reported for such images But I think that even such primitive CD flow could be useful. I propose to upstream the current simple Dockerfile to the master and stable-* branches so that experimental builds become available there. Then we could update the flow later. What do you think? Thanks in advance, Oleg -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDmk%2BVmop%2BhteQ_dxpiVW%3DXgjhcYpFyi1NbPQH2ZHd5pg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
