On Sun, Oct 27, 2019 at 06:42:58PM +0100, Luca Toscano wrote: > Some updates: > > - We have support for httpd in travis - https://travis-ci.org/apache/httpd
Nice, thanks Luca & infra! > - In order to configure automatic builds, a travis.yaml file is needed > in the base path of the repository, in every branch that needs to be > tested IIUC. > - My idea is currently to add in trunk a travis.yaml initial > configuration file, that builds a Docker image like [1] and runs the > perl test suite. > > - Building the Docker image in [1] takes quite a while now (between 9 > and 13 mins on my laptop, depending also on network bandwidth etc..) > so it will need more time before it could be as fast as we need, but > we have to start from somewhere :) > - In the travis.yaml file we'd need to put config options about what > Docker image to build and with what parameters. Ideally I'd like to > store the Docker images in the httpd-framework repository, and Do you mean Dockerfiles rather than images here? > reference them in the Travis config of the httpd branches, but not > sure if it will be possible. Worst case scenario we'll need to add the > Docker image in each httpd branch that we want to test (possibly in a > dedicated dir, like "docker" or "testing". I expected two goals for testing: 1. configure, build, and test using a variety of different configure options in the standard Ubuntu environment which Travis provides (enable different MPMs, different module sets, different --enable-foo/--with-foo, different gcc versions etc etc) 2. configure build and test in a variety of OS environments - this would make sense using container images. I don't have much experience testing inside containers from Travis, but if we can do both (1) and (2) inside containers that might make sense? Or can we do both separately? If you have a .travis.yml which works then I'd say go commit it and we can work from there. Regards, Joe > If you are strongly against the above or have more suggestions and > knowledge about Travis please let me know!
