--- Meeting Purpose ---
The meeting is yours to discuss whatever you want to. Aim to discuss with 'each other' as
in others subscribed to the builds@ mailing list, from your project or from other projects. There will also be Infra representation for infra related discussion items.
This is an informal meeting arranged for the benefit of individuals and projects to talk about anything they like
in relation to the ASF Build services and related integrations, rather than an infra panel discussion.
Date & Time: UTC time 1630 hrs
Duration: 1 hour
Location: Meeting space: https://meet.google.com/drz-tszy-bxr
This event is open to all committers and guests
Add here anything you would like a chance to talk about this week.
| Topic | Speaker | Notes |
|---|---|---|
| Travis migrations update | Travis Migrations - Preference is to move jobs to Github Actions | |
| Github Runners update | Gavin McDonald | Increased concurrency to 900 |
| Github to Azure public runners project | Gavin McDonald | Gavin to get with Github and get this started. |
| Jenkins Ephemeral nodes update | Gavin to get with Cesar re AWS access and roles |
Drew gave an update of the exodus from Travis , with a preference to use either Github Actions, or our Jenkins instances.
Drew will follow up directly with affected projects to give a timeline and a plan, builds@ mailing list will also be updated.
After a recent meeting, Github very kindly increased our overall concurrency of runner jobs to 900! Mac runners were also increased as part
of this to 70 from 50.
We have already seen a huge impact in our workflow queues, as can be seen from the snapshot image below:
The number of queued workflows dropped after increased parallelism:
Another item discussed with Github was that of being able to host our own public runners, using our Azure account.
This would give us even more concurrency and also the opportunity to increase the instance flavours and specs.
We hope to be working on this soon; and will give an update at next months builds meeting.
Jarek asked the possibility of Github providing higher spec runners in their public runners pool, I said I would ask.
(32GB/64GB mem etc)
Jacob from Arrow notes that caching is not really working properly for Github Actions - Gavin notes that there is
a new tab in the Admin area of the Org account on Github dedicated to Caches , this displays usage but offers
no actions to reset or anything - Arrow for example are currently using 85GB of a 10GB cache allowance - at
least 30 projects are above this 10GB limit. Jacob will email Gavin with more details so that he may reach out
to Github and get more information about this.
Zach from Trafficcontrol project asks about availability of M1 chip runners, and ARM64 platform.
Needs further investigation.
At the previous meeting, folks from Tomitribe have kindly offered to help set up on demand Jenkins nodes and connect
them to our Jenkins instances. Gavin and Cesar to get together and get access sorted. Gavin to install the EC2 plugin
for this.