Platform SIG - Apr 8, 2022

2022-04-08T15:00:00Z

Participants

Mark Waite (@MarkEWaite), Kevin Martens (@Kevin-CB), Afi Gbadago, Sophia Okito

Notes

Agenda:

  • Open action items
    • Plugin installation manager docs - PR-4373 (closed)
      • Docs team agrees with Tim that a simple use case will be described on www.jenkins.io and detailed documentation will be kept in the GitHub repository of the tool
  • Docker agent support additions under consideration
    • Docker on Windows Server 2022 LTSC requested
    • Kubernetes 1.23 is the first version that support Windows Server 2022 LTSC
      • Jenkins infra not yet using 1.23
      • Likely 3-6 months away from using it
    • Infra team is aware and they have put it into the backlog
  • Linux packages use systemd instead of System V init JENKINS-41218
    • Few minor fixes included in Jenkins 2.332.2
    • Looking good
  • Require Java 11 or newer for Jenkins core
    • Jira epics (Require Java 11) and backlog tracking by Basil Crow
    • Discuss Sep 2022 as the “Require Java 11” release
      • Mark to continue discussion in the mailing list and pull requests
  • Java 17 support in Jenkins
    • Build tooling improvement ready (thanks to Basil Crow)
    • Plugins need to update their parent pom
    • Preview available since 2.339 (currently at 2.342, so can test experiment)
  • Exit lifecycle change in the Docker images
    • Merged into Docker image master
    • Today, when the Jenkins process is asked to restart itself, today, it uses some complicated Linux specific logic to end the process and restart it
      • Next weekly release simplifies that for Docker images
      • Instead of the complicated logic, Jenkins will just exit
      • Rely on the Docker container runtime to restart the process
      • Behavior change that needs more explanation, may need a blog post
    • Does it need other documentation updates?
  • She Code Africa Pipeline Help project
    • Welcome to the Jenkins project
    • Sophia Okito - Java developer at Qabbly, a Nigerian startup
      • Java experience after spending time in an Engineering degree program
      • Hopes to explore other aspects of software
        • Engineering teams
        • Software architecture
      • First open source project contribution
    • Afi Gbadago - software engineer at Tentable, from Ghana
      • Spent time with Spring and Spring Boot
      • Python experience with flux
      • Has started experimenting with Jenkins
      • Hopes to use it in her working environment
    • Kevin Martens - technical writer at CloudBees in the community team
      • Updating and improving Jenkins documentation
      • Excited to help with the She Code Africa Contributhon
    • Getting started during the community onboarding period
    • Timeline
      • April 5 - April 19(?) - Community bonding
        • Get started, understand how we work together, submit sample pull requests, get development environments ready, learn more about Jenkins
      • April 19 (?) - May 19 (?) - Project work
        • Four weeks working on the tasks
      • Two week conclusion “wrap up”
        • Write final reports
        • Submit final details
    • Initial setup / Community bonding
      • Afi and Sophia get started
        • Contributhon folder
        • Create your own copy of the Pipeline Help document
          • Make that document public so that mentors can see it
          • When you encounter a question, note in the document and ask it in the Slack channel
        • Start taking notes in that copy as you make progress
    • Pipeline Help specifics
    • When do we meet next to talk about Pipeline Help
      • What are the best times to meet as a group
        • Afi better to meet 3:00 PM UTC or later
        • Sophia better to meet 6:00 PM UTC or later
        • Kevin 6:00 PM UTC
      • Thursday at 6:30 PM UTC
        • Mark schedule the session in the Jenkins calendar
          • Invite all to that session thru the Jenkins calendar