summaryrefslogtreecommitdiff
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* ci: Enable builds on macOSEmmanuele Bassi2018-05-291-5/+23
| | | | | Use Travis's macOS builder to check if Epoxy is building on that platform.
* ci: Use envvars to control the build options1.5.1Emmanuele Bassi2018-04-251-4/+7
| | | | | Instead of calling docker multiple times ourselves, use the `env` stanza to control the build options.
* meson: Rename the configuration optionsEmmanuele Bassi2018-02-231-2/+3
| | | | | | | The `enable-` prefix is an Autotool-ism; idiomatic naming for Meson projects should just use the name of the option, and rely on the type to convey meaning, especially because Meson does not have `disable` aliases that avoid the explicit `enable-foo=no` cases.
* ci: Add Docker image filesEmmanuele Bassi2018-02-231-3/+3
| | | | | There's no real benefit in hosting the Dockerfile in an external repository.
* travis: Drop conditional on LinuxEmmanuele Bassi2018-02-231-7/+7
| | | | | | | We currently run CI on Linux only, given that the macOS builders in Travis are always fairly overwhelmed; thus, there's no need to complicate the Travis script with a conditional that is always going to be true.
* ci: Check build with EGL support disabledEmmanuele Bassi2017-06-061-0/+1
|
* Put the no-GLX build under CIEmmanuele Bassi2017-03-291-0/+1
| | | | CI is pointless if we don't test all the possible combinations.
* Restructure the TravisCI scriptEmmanuele Bassi2017-03-291-1/+3
| | | | | | The script should only run the tests; the base Docker image pull, as well as the CI image build, should be performed in the preparation stage.
* Build Epoxy with Clang on TravisCIEmmanuele Bassi2017-03-291-1/+2
| | | | | We can test both GCC and Clang, so we can ensure Epoxy builds correctly with either.
* Ignore non-build branches in TravisEmmanuele Bassi2017-02-091-0/+5
| | | | | | The khronos-registry branch contains only the registry XML files. The debian branch contains the Debian packaging files.
* Update the TravisCI environment to use DockerEmmanuele Bassi2017-02-091-20/+14
| | | | | | | | | | | | | | | | | The Travis environment is terribly outdated, and they are not really subtly pushing people to use Docker to set up their own containerised CI environments instead of pulling from Ubuntu 12.04 or 14.04. Let's try using this approach: - create a Docker image that pulls from Debian Stretch - set up a build and test environment - push the image to the Docker Hub - create a derived Docker image that copies the Epoxy repo when running under Travis - run the build and test script inside the derived image This is similar to what Meson does for its CI.
* Use container based CI on TravisEmmanuele Bassi2017-02-011-5/+20
| | | | | | We don't really use `sudo` anywhere, except for installing packages; this means we should be able to use the faster container-based environment on Travis, instead of the VM-based one.
* Revert "Use Trusty for Travis"Emmanuele Bassi2017-01-311-1/+0
| | | | | | This reverts commit a11c76e1faa63d6071556b097d7b1b88c05b37d6. Return to the default of Precise, and keep Epoxy under CI.
* Use Trusty for TravisEmmanuele Bassi2017-01-311-0/+1
| | | | | Trusty (14.04) is outdated, but at least not as terribly outdated as the Precise (12.04) default.
* Add a control file for Travis CI.Eric Anholt2014-06-131-0/+13
This isn't quite as good as I'd like -- the XVFB setup doesn't support a bunch of context creation extensions that we use, and I haven't looked into the multiplatform stuff for doing OS X testing yet. I think it's a good start, though.
View Lorry Controller Status