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.
537 Commits
1 Branch
0 Tags
1.8 MiB
Tag: Branch: Tree: 01ebe27a82
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '01ebe27a82'
${ noResults }
libepoxy/.travis.yml

55 lines
1.2 KiB
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
ci: Enable builds on macOS Use Travis's macOS builder to check if Epoxy is building on that platform.
7 years ago
- osx
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
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
Build Epoxy with Clang on TravisCI We can test both GCC and Clang, so we can ensure Epoxy builds correctly with either.
8 years ago
- clang
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
ci: Enable builds on macOS Use Travis's macOS builder to check if Epoxy is building on that platform.
7 years ago
matrix:
exclude:
- os: osx
compiler: gcc
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:
ci: Enable builds on macOS Use Travis's macOS builder to check if Epoxy is building on that platform.
7 years ago
- |
if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
brew update
brew install python@3 meson
# Use a Ninja with QuLogic's patch: https://github.com/ninja-build/ninja/issues/1219
mkdir -p $HOME/tools; curl -L http://nirbheek.in/files/binaries/ninja/macos/ninja -o $HOME/tools/ninja; chmod +x $HOME/tools/ninja
fi
- 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
Restructure the TravisCI script 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.
8 years ago
before_script:
ci: Enable builds on macOS Use Travis's macOS builder to check if Epoxy is building on that platform.
7 years ago
- |
if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then
echo FROM ebassi/epoxyci > Dockerfile
echo ADD . /root >> Dockerfile
echo WORKDIR /root >> Dockerfile
docker build -t withgit .
fi
Restructure the TravisCI script 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.
8 years ago
ci: Use envvars to control the build options Instead of calling docker multiple times ourselves, use the `env` stanza to control the build options.
7 years ago
env:
- BUILD_OPTS=""
- BUILD_OPTS="-Dglx=no"
- BUILD_OPTS="-Degl=no"
- BUILD_OPTS="-Dx11=false"
Restructure the TravisCI script 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.
8 years ago
script:
ci: Enable builds on macOS Use Travis's macOS builder to check if Epoxy is building on that platform.
7 years ago
- if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then docker run withgit /bin/sh -c "CC=$CC .travis/epoxy-ci-linux.sh $BUILD_OPTS" ; fi
- if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then /bin/sh -c "CC=$CC .travis/epoxy-ci-osx.sh $BUILD_OPTS" ; fi