Dec 2, 2022 WebContainers Support page
Attending:
- @MarkEWaite Mark Waite
- @smerle33 Stéphane Merle
- @dduportal Damien Duportal
- @poddingue Bruno Verachten
- @hlemeur Hervé Lemeur
Agenda:
-
Open action items:
- Revisit the platform support containers => Damien, Mark, everyone?
- Mark Waite to write a “support page” for web containers similar to windows and linux support pages
- WildFly, Tomcat, Glassfish, …
- Done by Basil Crow, visible on jenkins.io
- Damien Duportal:
- Check Docker image download statistics per platform/version
- Check statistics for the archlinux Docker image to check if needed or not for agents. Only a few downloads compared to 10+ millions downloads for others. We’ll need to communicate on the future of this image. It only exists as a basic docker agent, even not in the form of the inbound-agent.
Could we get more information from the Docker hub?
We could announce the deprecation in a blog post - What about Centos 7? No support from June 2024.
- Fix docker agents deployment issues (old tags rebuilt randomly overriding the latest tags) => done, fixed, finally, congratulations Damien!
- Open issue for “merging” docker agent repositories into a single one
- Some tags for inbound-agent still sport the “-preview” label for JDK17
- Stephane Merle:
- Open issue on jenkins-infra/helpdesk about adding JDK19 to ci.jenkins.io => almost done : add java19 support for developpers to pre-built and try · Issue #3243 · jenkins-infra/helpdesk · GitHub
- Container image deprecation for the blueocean container (jenkinsci:blueocean)
- Damien proposed in last meeting to update the image a very last time, with a 10 seconds sleep at the very beginning in the entrypoint, then a very informative message giving the status, and then another round of 10 seconds waiting
- Need to announce the deprecation of the image
- Update the page on Dockerhub
- Add to a Jenkins LTS changelog or upgrade guide?
- Add a disclaimer to one or more pages on www.jenkins.io?
- Update the 2017 Blue Ocean blog post with deprecation notice?
- content/blog/2017/01/2017-01-13-blueocean-dev-log-jan.adoc
- Find a way to communicate the deprecation to users and admins
- Jenkins administrative monitor that checks for specific container content?
- Report it on it regularly in Platform SIG meetings
- Create an issue that proposes the deprecation and the needed steps => who?
- Not likely to make progress until end of December
- Repository: blueocean-plugin/Dockerfile at 099bbff6a13ec7709a22049c7c4b0f99bc9ec83d · jenkinsci/blueocean-plugin · GitHub
-
Docker Images for Jenkins changes:
- Monthly Base OS updates and autumn cleanup
- Huge work (not finished yet) to ensure “latest” version being overridden by older releases
- Automatic tracking of remoting and JDK versions implemented: we will get faster updates
- A LOT of fixes (missing packages such as curl, ssh, git, less, patch, timezones supports)
- ssh-agent is now using correct volume for agent workspace
-
New platforms:
- Experiments with Windows 2022: working with Jenkins Infrastructure to build these images
-
Container repository management for Jenkins agents
- Progress to report - Damien Duportal progressing towards unifying repositories
- Simplifying the release process
- Multiple repositories and multiple images from those repositories
- Releases are complicated unnecessarily
- Adding arm64 for docker images was too complicated
- Combining the repositories to simplify image management
- Need more detailed plan and design
- Cannot drop support for the existing containers
- Retain the container structure, but remain compatible
- Separate repository for Jenkins agents with tools installed
- Not actively maintained, many of the containers are still using Java 8, won’t work with most recent LTS, they need to be upgraded
- Download metrics are available from Dockerhub, could use those measure to prioritize the effort
- Not actively maintained, many of the containers are still using Java 8, won’t work with most recent LTS, they need to be upgraded
-
Require Java 11 or newer for Jenkins core
- Build toolchain changes arrived in parent pom 4.52
- Jenkins 2.361.x is minimum version in order to use that parent pom
- Java 11 for the win…
- Jenkins 2.361.4 is now one of the recommended Jenkins minimum versions for plugin dependencies
- Why a recommended minimum?
- The story of WMI Windows Agents plugin and implied dependencies
- Old Jenkins minimum version
- See JENKINS-70148 for an example
- Build toolchain changes arrived in parent pom 4.52
-
Java 17 support in Jenkins
- Jenkins infra plan to do it in December for their controllers, and try ci.jenkins.io in January 2023 if no objection
- Should we delay that in favor of JFrog work?
- No need to hurry that up
- Jenkins infra plan to do it in December for their controllers, and try ci.jenkins.io in January 2023 if no objection
-
It’s been one year that the controller docker images are not up to date (both LTS and the other one) for Windows (we supply the 2.356 version).
- One person volunteered to help with this issue
- Should we propose to end this image?
- We have to investigate. Is it valuable enough for the community to keep updating it?
-
Dec 30, 2022 meeting is canceled