Hi folks, As this seems to be a hot topic as of late, I'll provide some information about our usage of external CI services.
Travis CI: The foundation has an agreement with Travis CI to provide our projects with external CI services through them. At current, we have approximately 40 executors there, half of which are currently (build-time-wise) being occupied by three projects; Flink (21%), Arrow (18%) and Airflow (13%). The foundation is currently not looking at increasing the number of executors there, as we are assessing long-term costs and benefits, and we advise projects that have higher immediate needs for CI to either use our Jenkins CI system or figure out a budget/plan (whether that be internal or external to the foundation) for other options, and to also assess whether the number of builds and their duration fit with the overall goal of the CI need and the resources available at our disposal. Currently, all projects have, as of this week, been capped at 5 concurrent builds with Travis. AppVeyor and CircleCI: The foundation makes use of the free tier of these, as we have not received any requests for an increase, nor assessed whether this is beneficial, and as there are, as things are right now, permission issues that go against our standard policies for repository access. With regards, Daniel on behalf of ASF Infra.
