Attendees
- @dduportal (Damien Duportal)
- @hlemeur (Hervé Le Meur)
- @MarkEWaite (Mark Waite)
- @smerle33 (Stéphane Merle)
- @poddingue (Bruno Verachten)
- @kmartens27 (Kevin Martens)
Announcements
- Weekly: 2.382 - weekly checklist in progress, new item added to checklist with Kevin Martens
- No team meeting the 27 Dec. 2022
- Sunday 18 December: repo.jenkins-ci.org dowtime for maintenance:
- No builds/ci.jenkins.io. See blog post.
- trusted.ci.jenkins.io => disable update_center? What is the impact if down for 6 hours? => check with Daniel Beck.
- No impact on Jenkins users = update center will be available (but not updated)
- Renewal of Jenkins DNS domains
- jenkins.io => renewed in the next 2 weeks
- jenkins-ci.org => renewed with success
- Thanks Tyler and Mark
Upcoming Calendar
- Next Weekly: 2.383, 20 Dec. 2022
- Next LTS: 2.375.2, 11 of Jan. 2023
- Next Security Release: N.A.
- Next major event: Devoxx, FOSDEM, December 20th: webinar for GSoC
Notes
-
Done (12):
- Cannot verify or login
- Add Java19 support for developers to pre-built and try
- Revert move and rename of jenkins-infra/governance-meetings
- Server 500 error when trying to sign up for Jenkins JIRA
- Azure Windows 2019 VMs agent are failing when starting the agent process
- Various plugin downloads fails with HTTP response 500
- Mitigate a couple of security warnings
- Certificate for
repo.jenkins-ci.org
(JFrog Artifactory) expires on the 18th of December 2022 - Not able to fork the Jenkins repository
- Unable to deploy .hpi file in artifactory (even with accepted permissions/plugin-zos-devops.yml)
- Azure: Cleanup of resource group
prodconfluence
- Jenkins
-
New items:
-
ci.jenkins.io outage today
- issue to open
- Bom builds peak
- no obious issue
- metrics and logs show a peak of network connections
- working hypothesis: peak of TCP inbound JNLP
- OSUOSL
- Checked with them
- Runbook to write: which OSUOSL resources, and where to open issues (email)
- They could provide PPC64 (but no interest for Jenkins project). RISC-V?
- JFrog Artifactory (repo.jenkins-ci.org) maintenance: Cloud migration from GCP to AWS by JFrog teams
- JDK depreciations
- JDK8 (in
buildPlugin()
): https://groups.google.com/g/jenkinsci-dev/c/pjfvsMw-EMM- batch of PRs to detect calls to
buildPlugin()
inJenkinsfile
of plugin to use explicit parameters (and avoid calling it with default). - Goal: being able to identify which JDK is used, and avoid “surprise” changes
- Automate jenkins.io to get thet latest archetype
Jenkinsfile
for plugin developers. - pipeline-library: same (+ README.md)
- Issue for us in helpdesk
- batch of PRs to detect calls to
- JDK19/20: Planning for supported JDK versions in Jenkins Infrastructure
- JDK non LTS: not failing the build (optional)
- JDK8 (in
-
Ubuntu 22.04 upgrade campaign
- VPN is using it, to validate
- Next: packer-image
- Azure in January
- Oracle, AWS to be checked
-
ci.jenkins.io outage today
-
Work In Progress (11):
-
Some Jenkins mirrors are using the wrong media type for plugin downloads causing proxy/checksum failures
- Last task: archives.jenkins.io
-
[INFRA-3080] Add Windows Server 2022
- WiP by @smerle
-
Javadoc build is failing (
zdevops.jar
is not a valid ZIP file)- Need help and/or diagnostic
- Mark could be able to assist
-
Prevent creation of new issues in the WEBSITE project on Jira
- @en3hD3iMRx6_6IXLNY0Rag and @kmartens27
- Work in progress to check and evaluate issues beforee taking decisions
- No action required (yet?) on the JIRA administration
-
New repo for jenkins board
- Board will discuss and decide (~January 2023)
- Gavin Mogan completed transformation from GDocs to Markdown
-
Azure: Cleanup of resource group
prod-communityfunctions
- To be deleted (no opposition)
-
Mirrorstats report wrong results
- Nothing done. Still to be done
-
[INFRA-2754] Realign repo.jenkins-ci.org mission
- tests in progress
- Will need help from doc. team
-
Windows agents on ci.jenkins.io disconnect prematurely
- damien to finish it
-
Azure: Re-create networks to fix overlap issues and support of IPv6
- New virtual networks are ready
- New VPN VM ready. Puppetziation in progress. (Current docker-openvpn was adapted to manage both current
vpn.jenkins.io
and new VPNs configuration with fullccd
support) - Why not using the current
vpn.jenkins.io
:- Clean state
- Network overlap to avoid (peering)
- Opportunity to validate Ubuntu 22.04
-
Some Jenkins mirrors are using the wrong media type for plugin downloads causing proxy/checksum failures
-
ToDo (next milestone) (infra-team-sync-2022-12-20 Milestone · GitHub)