Attendees 
- @dduportal (Damien Duportal)
- @hlemeur (Hervé Le Meur)
- @MarkEWaite (Mark Waite)
- @smerle33 (Stéphane Merle)
- @kmartens27 (Kevin Martens)
Announcements 
- Weekly 2.418
- Failed during the “Push tag” step due to git
- Release process restarted as nothing was pushed
-
Next meeting (2023-08-15) Cancelled. We’ll meet the 22 August 2023 instead
-
Question: Jitsi for meetings?
- We tried Jitsi for visio. meetings inside Elements.io, both application and website
- We could run the infra meeting using Jisti instead of Zoom
- Recording can be done with a Youtube account (with the “live record” feature)
- Need to be enabled 24 hours before (1 time)
- Alternative with OBS studio (but local record)
- Let’s ask the board for the youtube liverecord
- Would avoid the “upload recording step”
Upcoming Calendar 
- Next Weekly: 2.419, the 15th August 2023
- Next LTS: 2.414.1 (RC 9th of August) the 23 of August (backports done, one last UI regression reported though)
- Next Security Release as per jenkinsci-advisories: N.A.
- Next major event:
- DevOps World in September
Notes 
-
Done:
-
- [HTTP/401 on repo.jenkins-ci.org] Fix LDAP user configurations in Artifactory to avoid unexpected HTTP/401 when logging in
- Contacted JFrog, they need a live session with us to debug
- Not able to login to artifactory
- Waiting from user to share their username or email to fix their problem
- [INFRA-3100] Migrate updates.jenkins.io to another Cloud
- Added Redis and Azurefile share resources
- Work in progress: deployment of the initial installation mirrorbits + Apache in
publick8s
- Kubernetes clusters: define
infraciadmin
SVC account as code- DigitalOcean: doctl to be added to Terraform environment
- Azure: Work in progress
- AWS: todo
- [pkg.jenkins.io] migrate the pkg.origin.jenkins.io service from AWS VM to Azure
publick8s
- Use mirrorbits but only the apache “file” service at first
- Proposal for application in publick8s to migrate to arm64
- www.jenkins.io is now running in ARM64 machine (including the ZH service) \o/
- Work in progress: building our own arm64 Docker images (for wiki as example)
- Q: is there any plugins.jenkins.io service that could be migrated as for today?
- Putting on hold until JDK 21 deployment is done
- Matomo github/docker repos
- Hervé: MySQL flexible instance to create
- Damien: Docker image and helm chart
- plugin-site build commonly fails on infra.ci when accessing https://plugins.jenkins.io resulting in a 502
- Checked in Fastly: every 3 hours this error appears. Gotta check if it is Fastly serving this error
- Continue to diagnose
- Improvement: integrating Fastly with Datadog
- Assess Artifactory bandwidth reduction options
- Assess Artifactory bandwidth reduction options · Issue #3599 · jenkins-infra/helpdesk · GitHub Good news and bad news
- Bad news still need to be diagnosed
- ATH builds commonly become unresponsive
- Stephane to propose a PR in ATH
- VMs: improve command prompts to avoid confusion between services
- Still todo
- AWS: decrease cost for Summer 2023
- Considered EPIC, moving ut of milestones (like the ubuntu 22.04 campaign)
- LF status page redirect may be cached for too long
- Still to be investigated with LF
- Remove IP restriction on bounce or migrate to VPN
- Still to be done
- [HTTP/401 on repo.jenkins-ci.org] Fix LDAP user configurations in Artifactory to avoid unexpected HTTP/401 when logging in
-
New issues:
- Important: October 2023 we want Jenkins to support JDK21 (new LTS). It Mean
- Official release in septemebr: only prereleases until then
- Mark used OpenJDK
amd64
Linux distribution - Temurin provides from here: Release jdk21-2023-08-08-10-16-beta · adoptium/temurin21-binaries · GitHub (prerelease)
- Mark used OpenJDK
- Issue to be created in helpdesk!
- Packer image (VMs all and linux container)
- Windows container image
- Tool
- JDK19?
- We keep them as some builds are referencing it
- need to be deprecated as it’s not patched anymore
- Stephane takes it!
- Official release in septemebr: only prereleases until then
- JDK17 for controller + agents: [infra.ci.jenkins.io] Start using JDK17 · Issue #3072 · jenkins-infra/helpdesk · GitHub
- Migrate Blue Ocean remaining jobs from ci.blueocean.io to the OSS Infra
- Top level folder on ci.jenkins.io (or Org. Scan)
- No deployment on ci.jenkins.io: we have to challenge any deployment of any artifact done on ci.blueocean.io (let’s ask Olivier Lamy)
- Important: October 2023 we want Jenkins to support JDK21 (new LTS). It Mean
-
ToDo (next milestone) (infra-team-sync-2023-08-22 Milestone · GitHub)