> On 25 Dec 2015, at 23:02, Bastian Krol <bastian.k...@tu-dortmund.de> wrote: > >> So worth to extend this chain to: >> >> "./configure && make all check dist && tar -x >> apache-couchdb-2.0-some-hash.tar.gz && cd apache-couchdb-2.0-some-hash >> && ./configure && make all check" - not real command, but with fixing >> tar and cd part it will be close to. > > Wouldn't it be enough then to only `make dist` in the git repo (without make > all check) and leave the `make all check` part for the second make run, when > running in the directory where we extracted the tarball? Otherwise we are > duplicating the work of the all & check targets. Since we will be running on > builds.a.o we should try to minimize build times when possible, I think.
That sounds like a good idea! > >> If it's possible to test "make install" on CI into some fake root - >> that would be also helpful. > > make install should be possible whenever we run the build in a Docker > container (so, for all Linux flavors). We'll have to see for other OSes. How > would you verify that the make install was successful? Fauxton has a set of smoke tests for a set up node/cluster: https://github.com/apache/couchdb-fauxton/blob/master/app/addons/verifyinstall/resources.js (adapted from Futon, which might be a bit easier to follow: https://github.com/apache/couchdb/blob/1.x.x/share/www/verify_install.html#L47). These should be easy to adapt, or extracted, so we can run them as part of CI. Best Jan --
