Continuous Integration Redux
Jan Lehnardt <jan@...
2015-06-29 21:21:46 GMT
last week I did a bit of outreach on Twitter, trying to grow our CI team. “What CI team?” you ask. — Exactly.
CouchDB needs world-class continuous integration in order to guarantee that we deliver quality software
across many platforms and configuration without wasting too much time.
In the past, I’ve handled the CI setup (http://ci.couchdb.org:8888 / rough docs at:
http://wiki.apache.org/couchdb/CI where you see that we are a little out of date ;) on a Mac Mini in my
home. It was meant as a temporary measure until a larger team could take over. This never happened and we are
trying to revive the effort now for the upcoming 2.0 release.
Before you ask: we are already using Travis CI, and it is really nice to do baseline checks for ongoing
development and Pull Requests, but it is inadequate to satisfy all our testing needs. In particular
testing on multiple operating systems, different operating system versions, dependency versions and
configurations (and Windows!) — I’m very good personal friends with the Travis team, and they want to
work towards supporting these things, but it’s nowhere near on their roadmap, and we need better CI now.
## There are a bunch of things to do
Before I go into details, I’d like to point out that the most important thing we need here is someone, or
better a group of people that are *interested in assuming ownership of the CouchDB Continuous
You’ll be part of a uniquely friendly community and would work on something, while sometimes thankless,
that would be of incredible benefit to the project. And we are here to hold your hands getting started. :)
Also, nothing here requires any specific Erlang knowledge. Any test suites are up to the Erlang devs in the
community and other than that, Erlang is just another Unix/Windows binary, nothing special required,
*and* you have a bunch of experts eager to help you at your disposal :)