third_party
/
libepoxy
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
383 Commits
1 Branch
0 Tags
1.8 MiB
Tag: Branch: Tree: f7d3671a0f
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f7d3671a0f'
${ noResults }
libepoxy/.travis.yml

28 lines
648 B
Raw Normal View History Unescape

Update the TravisCI environment to use Docker 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.
8 years ago
sudo: false
Ignore non-build branches in Travis The khronos-registry branch contains only the registry XML files. The debian branch contains the Debian packaging files.
8 years ago
branches:
except:
- debian
- khronos-registry
Update the TravisCI environment to use Docker 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.
8 years ago
os:
- linux
Add a control file for Travis CI. 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.
11 years ago
compiler:
- gcc
Use container based CI on Travis 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.
8 years ago
Update the TravisCI environment to use Docker 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.
8 years ago
language:
- c
Use container based CI on Travis 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.
8 years ago
Update the TravisCI environment to use Docker 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.
8 years ago
services:
- docker
Use container based CI on Travis 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.
8 years ago
Add a control file for Travis CI. 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.
11 years ago
before_install:
Update the TravisCI environment to use Docker 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.
8 years ago
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then docker pull ebassi/epoxyci ; fi
Use container based CI on Travis 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.
8 years ago
Add a control file for Travis CI. 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.
11 years ago
script:
Update the TravisCI environment to use Docker 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.
8 years ago
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then echo FROM ebassi/epoxyci > Dockerfile ; fi
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then echo ADD . /root >> Dockerfile ; fi
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then docker build -t withgit . ; fi
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then docker run withgit /bin/sh -c "cd /root && TRAVIS=true CC=$CC CXX=$CXX ./epoxy-run-tests.sh" ; fi