Hi everyone,
I have just succeeded in making Jenkins all green again!
https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/375/
Moral of the story: don't ignore Jenkins. Please. At the very least, file
a new issue if you don't know what is going wrong.
We're still working on getting more hardware for Jenkins dedicated to
CouchDB. When this happens, we may move away from Travis to Jenkins to have
faster builds and more control over our environment. More news as it
happens.
-------------------------
Here's what happened, for posterity's sake:
First, adrienverge proposed an innocent-enough looking change:
https://github.com/apache/couchdb/pull/1622
This had the knock-on effect of breaking 3 Jenkins builds. Two of them,
ubuntu xenial (16.04) and debian jessie, failed in the .deb packaging stage
because they did not declare a specific enough dependency on python. (The
packaging tools are smart enough to see the shebang #!/usr/bin/python2
header in the file and complain.) The third, CentOS 6, failed because it
has Python 2.6, and some of the constructs in our Python scripts are 2.7
specific. In our CI Docker image, I attempted to work around this by
symlinking /usr/local/bin/python to python3.4, and putting it first in the
path, but explicitly changing the dependency to python2 worked around my
workaround.
This third problem was worked around by
https://github.com/apache/couchdb/pull/1673,
but the other two problems required multiple reworks of the debian control file
in the couchdb-ci repo, first to try doing things the right way (using
dh-python), then eventually to suppress false positive errors on platforms
where we are actually doing the right thing.
Then, we had the lovely adventure with hypothesis breaking the build last
night, so a further change was made to couchdb-ci to pin the version of
hypothesis in the Jenkins Docker images.
With this change, and a full re-build/re-upload of the Docker images, we
have an all-green Jenkins again.
-Joan
