AW: Integration tests running on Docker

[Pluem, Ruediger, Vodafone Group]

C2 General

> -----Ursprüngliche Nachricht-----
> Von: Joe Orton <jor...@redhat.com>
> Gesendet: Mittwoch, 6. November 2019 10:53
> An: Apache HTTP Server Development List <dev@httpd.apache.org>
> Betreff: Re: Integration tests running on Docker
> 
> On Tue, Nov 05, 2019 at 10:06:23AM +0100, Luca Toscano wrote:
> > Basically what Joe did, but following what the Apache Arrow Project
> > did. There is a little bit of repetition, but in theory with this
> > config people are free to add tests for other OSes (osx, windows) and
> > I will probably be able to add custom ones with Docker to see the
> > difference in execution timings etc.. (Apache Arrow's test do use
> > docker, I didn't see it a first).
> 
> I haven't tried to follow all of what the Arrow .yml is doing (too much
> Java ;) but moving some of the logic into the repo itself out of
> .travis.yml seems like a good idea.  e.g. moving all of script: into
> something like ./test/travis_script_linux.sh or something for the Linux
> based tests, does that make sense?
> 
> This is working now -
> 
> https://travis-ci.org/apache/httpd/builds
> 
> and I guess it will work for forks and PRs too, haven't tried yet.
> 
> Anybody feel free to extend, play, hack, whatever with the travis.yml, I
> am no expert so may be doing something non-standard/wrong, feel free to
> correct/improve ;)
> 
> The jobs are quite quick but the queue time for the "apache" repos is
> long (10+ minutes) before they get started.  I guess it is doing
> notifications to committers directly, but we won't find out until a job
> fails?  Maybe let's keep experimenting with this a bit longer and then
> start sending mail to dev@ for state changes (exactly as buildbot does)
> when it seems stable?

+1. Thanks for taking care.

Regards

Rüdiger