Platform SIG November 18, 2022

Community
,
1

Nov 18, 2022 Docker agents status and near future

Attending:

Agenda:

  • Open action items:
    • Mark Waite to write a “support page” for web containers similar to windows and linux support pages
      • WildFly, Tomcat, Glassfish, …
    • 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
      • Fix docker agents deployment issues (old tags rebuilt randomly overriding the latest tags)
      • Open issue for “merging” docker agent repositories into a single one
    • Stephane Merle:
      • Open issue on jenkins-infra/helpdesk about adding JDK19 to ci.jenkins.io
  • Docker agents:
    • Status update: jenkins/agent and jenkins/inbound-agent
      • Both updated this week
      • Automatic agent for JDKs and remoting
      • Still Deployment errors (old tag rebuilt) sometimes, randomly. That is our next focus
      • JDK17 for ARM 32 is now working \o/
      • Thanks to @poddingue, SSH dependency for git is back to the menu
      • Archlinux: check statistics on DockerHub to decide whether we keep it or not
    • Proposal to merge the 3 agent repos into a single one (see below)
    • Moving the Jenkins default WORKDIR into docker ssh agent repo
  • Java 19 exploration with Jenkins core
  • Container image deprecation for the blueocean container (jenkinsci:blueocean)
    • Damien proposes 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
    • Not likely to make progress until November
    • Repository: blueocean-plugin/Dockerfile at 099bbff6a13ec7709a22049c7c4b0f99bc9ec83d · jenkinsci/blueocean-plugin · GitHub
  • 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
  • Require Java 11 or newer for Jenkins core
  • Java 17 support in Jenkins
    • Jenkins infra plan to do it in December for there controllers, and try ci.jenkins.io in January 2023 if no objection
  • Contributor Summit remix / rework 13th and 14th of December
    • Planned for an all day in-person event, not happening
    • All-day event online event not effective
    • Break it into 3 segments, two hours with specific topics
      • Document has started to discuss topics and themes for the segments
      • Mark to share the document, discussion
        • Segment 1 - SIG reports and User experience
        • Segment 2 - Security and supply chain
        • Segment 3 - User presentations and other topics

Bruno received the RISC-V board - not yet booted the board, can run Ubuntu 22.10 and OpenJDK is available from 11.0.16+8 to 20~17ea-2