Build pipeline and package build tasks

[wohali]

These are all stretch goals for the 2.1 RC timeline.

• if tests succeed, build packages in same job
• archive .debs/.rpms at end of build phase
• Nightly: build repository directory given a pile of .debs/.rpms
• Nightly: push repos to couchdb-vm2
• Release: push 2.0 deb/rpm binaries to bintray as validation
• Release: build 2.0 snaps, push 2.0 snaps to snapstore
• Release: Complete Include pointers to alternative installation mechanisms couchdb-documentation#141
• Release: add GPG signing key to bintray and sign 2.0 packages
• Release: update release process docs with pointers on deb/rpm/win/mac/docker/snap upload process
• Release: for 2.1, build convenience binaries, test, publish!
• Release: docker - relocate 2.0 image to apache/couchdb namespace (INFRA-14586) tracked as Migrate klaemo/couchdb to apache/couchdb couchdb-docker#20
• Release: Add Debian 9 (stretch) to the list of supported releases Add debian9 (stretch) images William-Yeh/docker-ansible#31 this has to land first :(

[wohali]

We're auto-building repos/dist-type source tarballs on master now.

[wohali]

2.0 packages are on bintray and have been tested (though couchup is missing.)

EL6/7

Repo file (place at /etc/yum.repos.d/bintray-apache-couchdb-rpm.repo):

[bintray--apache-couchdb-rpm]
name=bintray--apache-couchdb-rpm
baseurl=http://apache.bintray.com/couchdb-rpm/el$releasever/$basearch/
gpgcheck=0
repo_gpgcheck=0
enabled=1

This needs to be moved to somewhere in the couchdb-www repo on the asf-site branch for convenience.

Then:

yum -y install epel-release && yum install couchdb

Debian/Ubuntu

echo "deb https://apache.bintray.com/couchdb-deb {distribution} main" | sudo tee -a /etc/apt/sources.list where {distribution} is one of:

• jessie - Debian 8
• trusty - Ubuntu 14.04
• xenial - Ubuntu 16.04

Then:

apt-get update && apt-get install couchdb

[wohali]

Docs are updated, snaps are pushed.

[wohali]

Debian packages are signed. RPMs, well, are ugly. See https://serverfault.com/questions/624888/bad-signatures-or-nokey-errors-on-rpms-i-just-signed . Just ugh. We're not going to bother signing RPM packages for now.