Attendees
- @dduportal (Damien Duportal)
- @hlemeur (Hervé Le Meur)
- @MarkEWaite (Mark Waite)
- @poddingue (Bruno Verachten)
Announcements
- Weekly 2.392 - in progress,
- mirrors, rpm, deb, msi all verified as OK, changelog
- docker container build failing
- Tracked in Jenkins Core Release: Unable to build the Linux Docker Images with `docker buildx create --use: unknown flag: --use` · Issue #3400 · jenkins-infra/helpdesk · GitHub
- Damien is OoO next week (28 of February)
- Mark drives the weekly meeting and run the meeting in Zoom
- Herve/Stephane will prepare notes in sync with Damien
Upcoming Calendar
- Next Weekly: 2.393, 28 of February
- Next LTS: 2.387.1 on 8 March 2023
- Next Security Release as per jenkinsci-advisories:
- Plugins advisory last week (15th of February) => went smoothly
- Next major events:
- Scale in Los Angeles (10-12 March 2023)
- Devoxx in Paris (12-14 April 2023)
- cdCon, Vancouver (8-9 May 2023)
Notes
-
Done:
- Ensure all GitHub action versions are pinned and tracked
- Maven 3.9.0
- Can no longer test PCT incrementals in
jenkinsci/bom
- Frequent PagerDuty Alerts
Disk space is below 1GB free win-xxx-yyyyyy
- Container images jenkins/jenkins:2.391 not published
- Archive jenkinsci/domain-discovery-module
- Archive jenkinsci/jna
- Null pointer exception on stable-2.387 CI job
-
- trusted.ci.jenkins.io: error regenerating certificate
- Jenkins Core Release: Unable to build the Linux Docker Images with
docker buildx create --use: unknown flag: --use
- Old email provider deleted
maven-17
label hanging on ci.jenkins.io- Terminate builds stuck in queue on infra.ci
- We can’t access our plugin account
- (2023-02-15) Azure Credential for cert.ci.jenkins.io is expired
- Upgrade to Kubernetes 1.24
- Document the code signing certificate renewal process
- AKS: add cluster
publick8s
- Renew the signer certificate for jenkins
-
AKS: add cluster
privatek8s
- Plan elaborated: to be written in issues
- PR for new nodepools to be review/merged/deployed
- Cleanup of
temp-privatek8s
resources
-
(Re) Introduce an artifact caching proxy for ci.jenkins.io
- Plugins, Core, BOM/PCT are using ACP :party:
- A lot of useful but hidden work on the pipeline-library (
runWithMaven()
, etc.) - backend-extensions-indexer (which has raw mentions repo.jenkins-ci.org)
- ATH uses
runMaven()
: should be also using ACP (to confirm) - We received JFrog last data. Did not had time to check in details: to be done to evaluate the effect
-
[INFRA-2754] Realign repo.jenkins-ci.org mission
- Discussion still in progress with JFrog on the “big” consumers we detected outside ourselves
- Nothing done (yet) on the HA for LDAP/authentication on mirrors on JFrog => on hold for now (ACP is priority)
-
Add NotMyFault to trusted.ci
- Go for it, given the issues we recently had on the Docker image
- Long term: migrate to release.ci
-
Redirect Chinese pages to English pages and shutdown the Chinese site
- Low priority : backlog
-
ToDo (next milestone) (infra-team-sync-2023-02-28 Milestone · GitHub)