Hi all, I agree that if we can cut all of the pain-points above and if ASF offers this option, there is no reason no to do it.
In a vote, I'd be +1 ;-) Den tirs. 7. jul. 2026 kl. 05.37 skrev James Daugherty < [email protected]>: > Hey Everyone, > > We've discussed how slow GitHub agents are in the past and how the > slowness has even led to increased flakiness in our tests (wait time > outs). I recently went digging in the ASF infra tickets, and noticed > tickets like these: https://issues.apache.org/jira/browse/INFRA-25990 > > I think it's time to have a serious discussion about using self-hosted > GitHub agents. Adopting them would have the following benefits: > 1. faster agents (builds take 10min locally, take 40min+ in GitHub) > 2. less flaky tests due to #1 > 3. dedicated IPs - we still see our runners get blocked every once in > a while due to the public ip space being shared with GitHub. We also > get random 403 / timeouts on maven central with our build due to the > shared IPs. > > I don't really see the downside of using self hosted, the shared IP > space has caused enough frustrations alone that I think we should > switch. Let's discuss this to see if people agree... > > -James > -- Best regards Søren Berg Glasius Apache Groovy™ and Apache Grails® PMC --- Press ESC once to quit - twice to save the changes.
