Platform SIG December 16, 2022

Attending:

Agenda:

  • Open action items:

    • Revisit the platform support containers
      • Add Windows 2022
      • Fix Windows 2019
      • We have to maintain the 2 architectures at the same time, as they are not compatible. 2022 is the new “LTS”
      • What about our support? Is it worth our time? Windows container support is not going to disappear, even if not as popular as Linux containers.
        We should maybe ask the community about it. Is anyone using them? It is required for build agents nonetheless, so we have to use them anyway.
        We already have the fraction of the controllers running on Windows… We should have the look at it. It may not be published, but may exist somewhere.
    • 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
      • There is strong interest in gathering and exploiting statistics.Adrien Lecharpentier and Jean-Marc Meessen are working on this subject.
        Infra could offer that kind of tool: Grafana connected to PostegreSQL could be useful. Why Grafana? Anyone can authenticate through LDAP account.
        Basil Crow made a tool that converts the jenkins update center data to a database so that we can search in it thanks to SQL sentences.
      • Open issue for “merging” docker agent repositories into a single one
      • Some tags for inbound-agent still sport the “-preview” label for JDK17
  • Docker Images

    • New platforms:
      • Experiments with Windows 2022: working with Jenkins Infrastructure to build these images
      • Add Wolfie?
      • Deprecate ArchLinux?
      • Experiments with RISC-V agents with JDK17
    • 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 e278d36a6278c4ec981cf9038314834a9eed3591 · jenkinsci/blueocean-plugin · GitHub
    • Container repository management for Jenkins agents
      • Merge all repositories into a single repository
    • Windows: 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?
  • JDK Support for Jenkins

    • 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
        • The story of WMI Windows Agents plugin and implied dependencies
          • Old Jenkins minimum version
          • See JENKINS-70148 for an example
          • Tracking sheet for implied dependencies
          • Bruno should add a sentence in the controller container image documentation regarding his experience with the removal.
    • 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
    • JDK 19 support in Jenkins
      • Installed on CI, discussion on the mailing list about Edge and future LTS versions
  • Dec 30, 2022 meeting is canceledhttps://youtu.be/8wzQPVbQ15s

Attending:

  • Mark Waite
  • Damien Duportal
  • Bruno Verachten

Agenda:

  • Open action items:

    • Revisit the platform support containers
      • Add Windows 2022
      • Fix Windows 2019
      • We have to maintain the 2 architectures at the same time, as they are not compatible. 2022 is the new “LTS”
      • What about our support? Is it worth our time? Windows container support is not going to disappear, even if not as popular as Linux containers.
        We should maybe ask the community about it. Is anyone using them? It is required for build agents nonetheless, so we have to use them anyway.
        We already have the fraction of the controllers running on Windows… We should have the look at it. It may not be published, but may exist somewhere.
    • 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
      • There is strong interest in gathering and exploiting statistics.Adrien Lecharpentier and Jean-Marc Meessen are working on this subject.
        Infra could offer that kind of tool: Grafana connected to PostegreSQL could be useful. Why Grafana? Anyone can authenticate through LDAP account.
        Basil Crow made a tool that converts the jenkins update center data to a database so that we can search in it thanks to SQL sentences.
      • Open issue for “merging” docker agent repositories into a single one
  • Docker Images

    • New platforms:
      • Experiments with Windows 2022: working with Jenkins Infrastructure to build these images
      • Add Wolfie?
      • Deprecate ArchLinux?
      • Experiments with RISC-V agents with JDK17
    • 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 e278d36a6278c4ec981cf9038314834a9eed3591 · jenkinsci/blueocean-plugin · GitHub
    • Container repository management for Jenkins agents
      • Merge all repositories into a single repository
    • Windows: 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?
  • JDK Support for Jenkins

    • 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
        • The story of WMI Windows Agents plugin and implied dependencies
          • Old Jenkins minimum version
          • See JENKINS-70148 for an example
          • Tracking sheet for implied dependencies
          • Bruno should add a sentence in the controller container image documentation regarding his experience with the removal.
    • 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
    • JDK 19 support in Jenkins
      • Installed on CI, discussion on the mailing list about Edge and future LTS versions
  • Dec 30, 2022 meeting is canceled