# Infrastructure Team Meeting - December 17, 2024

**URL:** <https://community.jenkins.io/t/infrastructure-team-meeting-december-17-2024/24893>\
**Category:** Infrastructure\
**Tags:** meeting, sig-infra\
**Created:** [December 18, 2024, 10:12am UTC](https://community.jenkins.io/t/infrastructure-team-meeting-december-17-2024/24893 "2024-12-18T10:12:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dduportal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/dduportal/32/18_2.png) [@dduportal](https://community.jenkins.io/u/dduportal)\
**Post date:** [December 18, 2024, 10:12am UTC](https://community.jenkins.io/t/infrastructure-team-meeting-december-17-2024/24893/1 "2024-12-18T10:12:40Z")

</div>

[![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/0/01fd1a50e0e38a8a618ed4dc18c18d78a1242772.jpeg "2024 12 17 Jenkins Infra Meeting") ](https://www.youtube.com/watch?v=Q1cJSse9iYA)

## Attendees 👥

- @dduportal (Damien Duportal)
- @MarkEWaite (Mark Waite)
- @smerle33 (Stéphane Merle)
- @Stewi
- @kmartens27 (Kevin Martens)
- @poddingue (Bruno Verachten)
- @onenashev (Oleg Nenashev)

## Announcements 📢

1. Jenkins Weekly Releases
  - Last Week: 2.489 released with no hiccups
  - This Week: 2.490 started on time

2. Announcements:
  - 2 weeks breaks:
    - No Infra SIG meeting
    - No LTS release (next one: 08 Jan 2025)
    - (? No weekly releases)
      - Mark wants to continue weekly releases, accepting may not happen
      - Missing a weekly release might delay detection of issues
        - Testing and verification

      - Damien, Stephane, Oleg reply to the email thread that we’ve decided to not build weekly during break

    - Limited team availability (we are all off, Damien is the fallback in case of emergency)

## Upcoming Calendar 📆

- Next Weekly: 2.491, 7 Jan 2025
- Next LTS: 2.479.3, 8 Jan 2025
- Next Security Release as per [jenkinsci-advisories](https://groups.google.com/g/jenkinsci-advisories): N.A.
- Upcoming credentials expirations (~3 weeks):
  - 18 Dec. - [stats.jenkins.io](https://github.com/jenkins-infra/azure/pull/884) Azure SP for production deployment
  - 18 Dec. - [contributors.jio](https://github.com/jenkins-infra/azure/pull/883) Azure SP for production deployment
  - 18 Dec. - [infra.ci.jio](https://github.com/jenkins-infra/azure/pull/882) Azure SP for production deployment
  - 26 Dec. - All Terraform State Azure SP are expiring (8 projects, 8 credentials, automated PRs from [https://github.com/jenkins-infra/terraform-states/pull/38](https://github.com/jenkins-infra/terraform-states/pull/38) up to [https://github.com/jenkins-infra/terraform-states/pull/45](https://github.com/jenkins-infra/terraform-states/pull/45))

- Next major event:
  - [Contributor Summit](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-31-2025-call-for-topics-and-ideas/21678) and FOSDEM, in Brussels, 31 Jan. and 1/2 Feb. 2025
    - Mark has proposed prioritized list of attendees to Jenkins Board, more details this week
    - Invited attendees notified this week
      - Software in the Public Interest funding travel for some attendees
      - CloudBees funding travel for some attendees

## Cloud Budgets

- Azure CDF:
  - September: $3.8 (invoice)
  - October: $4.0k (invoice)
  - November: $4.3k (invoice)
  - December: $2.4k (forecast at $4.6k ⚠)
    - Increase due to outbound bandwidth (~$10 daily additionals)
    - Potential $266 monthly saving with the cert.ci, trusted.ci and puppet VM sizing (~$8 daily savings)
    - Potential savings by grouping file storages into a single NFS (get.jio + updates.jio + geoipupdate)

- Azure Sponsorship (Microsoft Credits) - Remaining: $35654 ($84346 consumed) until May 2025
  - September: $10.4k consumed
  - October: $12.9k consumed
  - November: $13k
  - December: $5.9k (forecast at $10.8k)

- DigitalOcean - Remaining $15,346 ($4k consumed) until January 02 🎉 2026 🎉 credits extended
  - September: $158 (invoice)
  - October: $195.67 (invoice)
  - November: $146 (invoice)
  - December: $101 (forecast at $185)

- AWS:
  - CloudBees:
    - August: $6.3k
    - September: $6.1k
    - October: $6.4k
    - November: $3.9k
    - December: $283 (forecast at $557)

  - Sponsored account (~$58k credits lefts)
    - October: $178
    - November: $482
    - December: $246 (forecast at $516)

## Additional Topics

- Quick not-so-off-topic - JCP meeting on Dec 17 and JEP-14 feedback
  - Java Community Process - caring for Java Enhancement Proposals
  - Working group that focuses on technical topics
  - Tip and Tail - how Java version things, how libraries version things
    - Mark to attend session and share Jenkins 2+2+2

- Jenkins and Develocity FOSS sponsorship - is there still potential interest -
  - [GitHub - gradle/develocity-oss-projects](https://github.com/gradle/develocity-oss-projects)
  - “Develocity open source sponsorship for Jenkins CI instances” - thread in [jenkins-infra@googlegroups.com](mailto:jenkins-infra@googlegroups.com) - [https://groups.google.com/g/jenkins-infra/c/KveP8\_0b3zk/m/FjlfcFm2BQAJ](https://groups.google.com/g/jenkins-infra/c/KveP8_0b3zk/m/FjlfcFm2BQAJ)
    - Develocity - distributed build caching, build scans, predictive test selection (might overlap with CloudBees’ offering being deployed), etc.
    - Some first metrics for Jenkins plugins are nice (4x build boost for a Maven based plugin), but a champion is needed to explore further. Oleg has a CoI as a Gradle employee
    - The opportunity is still there, not sure about the budget allocation. If there is no follow-up, Gradle will definitely move on.
    - Damien: interested in the infra part
    - Oleg to follow-up with Damien in January-ish. Some technical details would be needed

- AWS account use for AWS Java SDK v2 work - [JENKINS-73638](https://issues.jenkins.io/browse/JENKINS-73638)
  - Jenkins infra is very interested in the AWS improvements
    - Concerned about the EC2 plugin already

  - Can allocate one or more developers an IAM profile on a distinct region
    - Will need to predict the needed resources for that IAM profile
    - What is need to start that process?
      - Create a help desk ticket with the list of users and the use case
        - Infra will generate the credentials and share them securely with the contributors

      - May need a workshop session at Contributor Summit on AWS Java SDK v2

## Notes 📖

- [Done](https://github.com/jenkins-infra/helpdesk/milestone/140?closed=1):

- [Closed as not planned](https://github.com/jenkins-infra/helpdesk/milestone/140?closed=1):

- [Work in Progress](https://github.com/jenkins-infra/helpdesk/milestone/140):

- New Issues/to triage:

- ToDo (next milestones):