On 12 Oct 2015, at 09:02, Junio C Hamano <gits...@pobox.com> wrote:
> Sebastian Schuberth <sschube...@gmail.com> writes:
>
>> Semantically, it does not seem correct to me that configuarion goes to
>> the install step. As "make test" will build git anyway, I'd instead
>> propose to get rid of "install" and just say:
>>
>> before_script: make configure && ./configure
>>
>> script: make --quiet test
>
> Very good point. Do we even need to do anything in the "install"
> target? We aim to be able to testable without any installed Git,
> and not running "make install" at all, ever, would be one way to
> make sure that works.
The Travis CI "install" stage is independent of "make install". AFAIK you can
use the Travis lifecycle stages pretty much as you want. However, I agree we
should not use the "install" stage to avoid confusion.
> This is a slightly related tangent, but we saw a few build issues
> reported recently on customized configurations like NO_PTHREAD. If
> we are to start using automated tests, I wonder if we want to build
> (and optionally test) with various combinations of the customization
> options (e.g. NO_CURL, NO_OPENSSL, NO_MMAP, NO_IPV6, NO_PERL etc.)
This easy to do. However, the more we environment settings we define the longer
the build runs. I created a test matrix that runs the following combinations:
{Linux | OSX} * {gcc | clang} * {Default, NO_PTHREAD, NO_CURL, NO_OPENSSL,
NO_MMAP, NO_IPV6, NO_PERL}
These result in 28 (= 2*2*7) combinations. I created a build without the
"Default" environment (=24 combination) here:
https://travis-ci.org/larsxschneider/git/builds/84978673
Should I add them them to the Travis CI patch?
Thanks,
Lars
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
