Hi everyone,
I'm in receipt of Ilya's email on build challenges, and do want to
reply, but have been preoccupied with things at a Foundation level since
I was elected as a Director of the ASF. (Sorry about that.)
Here's a quick brain dump.
While I was making my rounds through lists, the forwarded email below
came up on the bui...@apache.org list today. Please read it. Perhaps
this will shed some light on the current slowness in the Travis CI
situation. The original thread is at [4].
Moving entirely to Jenkins CI - whether the build master is run by the
ASF as it is today, or we take on the effort to run our own build master
- will improve things, but we need to take into consideration more
challenges.
For instance, Jenkins has no integration with docker-compose[1]. And
various contributors continue to insist on pushing forward with
ppc64le[2] and aarch64[3] and think donating a single build box will
solve the problem. I don't want us to reintroducing new single points of
failure into the CI chain. Finally, the test suite is still fragile, and
while I see efforts to convert to ExUnit and Elixir, the fragility is
not being resolved at the same time, near as I can tell - nor is it
eliminating our dependence on test timeouts. (Removing those timeouts
entirely would make cross-platform building an easy way out of requiring
multiple CI build agents per target processor architecture.)
These challenges *are* solveable, but they deserve more than just "quick
fixes."
-Joan "so much work, so little time" Touzet
[1]:
https://lists.apache.org/thread.html/528962b6b1fe0e96277f5ebeb0e75ea5460061cf33bf9c2c796200a0@%3Cbuilds.apache.org%3E
[2]: https://github.com/apache/couchdb-docker/issues/68
[3]: https://github.com/apache/couchdb-docker/issues/85
[4]:
https://lists.apache.org/thread.html/af52e2a3e865c01596d46374e8b294f2740587dbd59d85e132429b6c@%3Cbuilds.apache.org%3E
-------- Forwarded Message --------
Subject: External CI Service Limitations
Date: Tue, 02 Jul 2019 21:50:51 -0000
From: Daniel Gruno <humbed...@apache.org>
Reply-To: bui...@apache.org
To: bui...@apache.org
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.
