- @dduportal (Damien Duportal)
- @hlemeur (Hervé Le Meur)
- @MarkEWaite (Mark Waite)
- @kmartens27 (Kevin Martens)
Announcements 
- Weekly 2.430 in progress
- WAR, packages and container image tag is being built
- Include a regression fix, which will be backported to LTS (later today)
Upcoming Calendar 
- Next Weekly: 2.431
- Next LTS: 2.426.1 Nov 15, 2023, release candidate Nov 1, 2023 (tomorrow)
- Mark Waite is the release lead, see the checklist
- Next Security Release as per jenkinsci-advisories: N.A.
- Plugin advisory last week, Jenkins infra updated the same day
- Next major event:
- DevOps World London is coming (5 December 2023)
- Jenkins contributor summit prior to FOSDEM (Feb 2024)
Notes 
-
Done:
-
- [INFRA-3100] Migrate updates.jenkins.io to another Cloud
- update-center 2 script paralellization for JSON deployment works very well.
- WiP: triggering mirrorbit scan as last step of the script.
- WiP: mirrorbits ingress. Fixed issue, tuning of ingress rule as a next step.
- Mirrorbits sustainability: VLC’s creator, JB. Kempf gained ownership of the project for adoption. Good news for us and incoming mirrorbits update after a few years.
- Proposal for application in publick8s to migrate to arm64
- WiP on uplink
- Cleanup required to build and ship it one time after 4 years with no deployments while leveraging risks (
npm ci, etc.).- Done with success!
- Image is now built both for x86 and arm64 and deployed with success :party:
- Cleanup required to build and ship it one time after 4 years with no deployments while leveraging risks (
- Next steps:
- Migrating cert-manager and datadog-cluster agent to arm64
- Identify the 2-3 services requiring arm64 images
- Also: fix falco crashing on arm64 by upgrading it to latest version (or remove it)
- WiP on uplink
- Upgrade to Kubernetes 1.26
- DigitalOcean was succesfully upgraded last week
- WiP EKS upgrade. Need to check CNI plugin version as a requirement, otherwise ready to go.
- Impact: worst case, BOM builds will be delayed in the queue until operation is finished.
- TODO: AKS, but need falco upgrade before (so next week most probably)
- Matomo github/docker repos
- Nothing done (not enought time)
- Back to backlog for now
- Packer: GOSS version tracking and moving sanity check to goss
- Windows packer images are now using goss
- external contributor added playwright AND goss sanity check
- WiP: Covering all the Linux tests with goss
- Todo: add a “goss-common” harness
- track the new jdk21 version from adoptium
- WiP: JDK tool (and trusted build agent)
- s390x agent keep using EA (for tools)
- WiP: JDK tool (and trusted build agent)
- speed up the Docker image library to create/push tags at the same time for both GH and Docker (instead of running additional build)
- Nothing done (not enough time)
- Back to backlog for now
- “Mirror Status” link from get.jenkins.io returns a 404 error
- WiP: analysis
- Do we need it, or to update the link?
- Need to check requirement to have archives.jenkins.io as fallback (bandwidth in DigitalOcean)
- WiP: analysis
- ftp.belnet.be should be removed from mirrors or a fall-back offered
- WiP: Need to contact belnet admins
- Ensure removed jenkins.io pages aren’t accessible and indexed anymore
- WiP: plan it this week, most probably Thursday
- Backup OK
- Requirement OK
- One last “restore” test of the root folder file
- todo: merge PR and profit!
- WiP: plan it this week, most probably Thursday
- Planning for supported JDK versions in Jenkins Infrastructure
- JDK19 cleaned up
- Need one last check in GH
- 2+2+2 JEP: need ci.jenkins.io documentation update, then we’ll move to the JEP’s implementation part (with checklist \o/)
- JDK19 cleaned up
- [INFRA-3100] Migrate updates.jenkins.io to another Cloud
-
New items:
- Merging core PRs doesn’t cancel PR builds
- TBD
- Long term (unicorn world with rainbows): JobDSL-ization of ci.jenkins.io would avoid such configuration “shift”
- Start a new repo under jenkins-infra for the Jenkins Contributor Spotlight feature on jenkins.io
- Does it “increment” stories.jenkins.io (
/contributorsfor instance)? or does it a secondary website such as contributors.jenkins.io?- Already have a 2nd website with previe as per Kris work => secondary website looks easier
- Proposal: link in stories.jenkins.io to redirect to the new website
- contributors.stories.jenkins.io / users.stories.jenkins.io
- Hypothesis of “secondary website”
- Need to fork the repo to jenkins-infra
- WiP: Permission
- TODO:
- CI (preview website)
- Production (same as stories.jenkins.io most probably)
- CD (extend CI to production)
- Need to fork the repo to jenkins-infra
- Does it “increment” stories.jenkins.io (
- Add Bruno Verachten to the GSoC team
- Mirrorbits got pods restart on publick8s
- updatecli: track the kubectl version used on publicK8S to update the kubectl version on puppet
- good first issue, no milestone
- Merging core PRs doesn’t cancel PR builds
-
ToDo (next milestone) (infra-team-sync-2023-11-07 Milestone · GitHub)