2016-06-23 19:20:37 +00:00
|
|
|
language: c
|
2016-07-29 03:13:29 +00:00
|
|
|
sudo: false
|
2017-09-18 11:05:47 +00:00
|
|
|
branches:
|
|
|
|
only:
|
|
|
|
- master
|
2016-06-23 19:20:37 +00:00
|
|
|
matrix:
|
2016-06-29 03:35:16 +00:00
|
|
|
include:
|
|
|
|
###
|
|
|
|
## Linux builds using various versions of GCC.
|
|
|
|
###
|
|
|
|
- os: linux
|
2017-09-18 11:52:53 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=gcc-7 CXX_COMPILER=g++-7
|
2016-06-29 03:35:16 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-09-18 11:52:53 +00:00
|
|
|
- gcc-7
|
|
|
|
- g++-7
|
2016-06-29 03:35:16 +00:00
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=gcc-4.4 CXX_COMPILER=g++-4.4
|
2016-06-29 03:35:16 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- gcc-4.4
|
|
|
|
- g++-4.4
|
|
|
|
|
|
|
|
###
|
|
|
|
## Test that Autotools build works.
|
|
|
|
###
|
2016-06-29 03:35:16 +00:00
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=autotools C_COMPILER=gcc-5 CXX_COMPILER=g++-5
|
2016-06-29 03:35:16 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-09-18 11:52:53 +00:00
|
|
|
- gcc-5
|
|
|
|
- g++-5
|
2016-06-29 03:35:16 +00:00
|
|
|
|
2017-09-26 11:49:30 +00:00
|
|
|
###
|
|
|
|
## Test that fuzzer is compiling / working.
|
|
|
|
###
|
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=fuzz C_COMPILER=clang-5.0 CXX_COMPILER=clang++-5.0 ASAN_OPTIONS=detect_leaks=0
|
2017-09-26 11:49:30 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
2017-11-30 19:54:04 +00:00
|
|
|
- llvm-toolchain-trusty-5.0
|
2017-09-26 11:49:30 +00:00
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- clang-5.0
|
2017-09-26 11:49:30 +00:00
|
|
|
|
2016-06-29 03:35:16 +00:00
|
|
|
###
|
2016-07-23 02:14:29 +00:00
|
|
|
## clang on Linux
|
2016-06-29 03:35:16 +00:00
|
|
|
###
|
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=clang-5.0 CXX_COMPILER=clang++-5.0
|
2016-07-23 02:14:29 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
2017-11-30 19:54:04 +00:00
|
|
|
- llvm-toolchain-trusty-5.0
|
2016-07-23 02:14:29 +00:00
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- clang-5.0
|
2016-07-23 02:14:29 +00:00
|
|
|
- os: linux
|
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=clang-3.5 CXX_COMPILER=clang++-3.5
|
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
2017-09-18 11:52:53 +00:00
|
|
|
- llvm-toolchain-trusty-3.5
|
2016-07-23 02:14:29 +00:00
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
|
|
|
- clang-3.5
|
2016-06-29 03:35:16 +00:00
|
|
|
|
2018-09-27 09:00:33 +00:00
|
|
|
###
|
|
|
|
## testing arm via qemu on Linux
|
|
|
|
###
|
|
|
|
- os: linux
|
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=arm-linux-gnueabihf-gcc CXX_COMPILER=arm-linux-gnueabihf-g++
|
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
|
|
|
- qemu
|
|
|
|
- gcc-arm-linux-gnueabihf
|
|
|
|
- libc6-dev-armhf-cross
|
|
|
|
|
2017-02-19 09:06:13 +00:00
|
|
|
###
|
|
|
|
## PGI Community Edition on Linux
|
|
|
|
###
|
|
|
|
- os: linux
|
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=pgcc CXX_COMPILER=pgc++
|
|
|
|
|
2016-06-29 03:35:16 +00:00
|
|
|
###
|
disable buidling/deployment of python wheels (#583)
* [appveyor] remove 'deploy' stage; only test python 2.7 and 3.6
all the other python versions are being built and tested on
https://github.com/google/brotli-wheels/blob/d571d63/appveyor.yml
* remove terrify submodule as not needed any more
* [travis] just test py2.7 and 3.6 on linux; remove extra osx python builds
All the other python versions for OSX are being built/tested on:
https://github.com/google/brotli-wheels/blob/d571d63/.travis.yml
Also, there's no need to build and deploy wheels here, as that's done
in the separate repository.
* [setup.py] only rebuild if dependency are newer; fix typo in list of 'depends'
https://github.com/python/cpython/blob/v3.6.2/Lib/distutils/command/build_ext.py#L485-L500
* [ci] only run 'python setup.py test'
if we run 'python setup.py built test', the setuptools 'test' command will
forcibly re-run the build_ext subcommand because it wants to pass the --inplace
option (it ignores whether it's up to date, just re-runs it all the time).
with this we go from running built_ext twice, to running it only once per build
* [Makefile] run 'build_ext --inplace' instead of 'develop' as default target
The 'develop' command is like 'install' in the sense that it
modifies the user's python environment.
The default make target should be less intrusive, i.e. just building
the extension module in-place without modify anything in the user's
environment.
We don't need to tell make about the dependency between 'test' and
'build' target as that is baked in the `python setup.py test` command.
* [Makefile] add 'develop' target; remove unnecessary 'tests' target
`make test` is good enough
* [Makefile] `setup.py test` requires setuptools; run `python -m unittest`
This will work even if setuptools is not installed, which is unlikely
nowadays but still our `setup.py` works with plain distutils, so
we may well have our tests work without setuptools.
* [python/README.md] add ref to 'develop' target; remove 'tests', just 'make test'
* [setup.py] import modules as per nicksay's comment
https://github.com/google/brotli/pull/583#discussion_r131981049
* [Makefile] add 'develop' to .PHONY targets
remove 'tests' from .PHONY
* [appveyor] remove unused setup scripts
We don't need to install custom python versions, we are
using the pre-installed ones on Appveyor.
* [appveyor] remove unneeded setup code
2017-08-23 18:45:13 +00:00
|
|
|
## Python 2.7 and 3.6 builds on Linux
|
2016-06-29 03:35:16 +00:00
|
|
|
###
|
|
|
|
- os: linux
|
disable buidling/deployment of python wheels (#583)
* [appveyor] remove 'deploy' stage; only test python 2.7 and 3.6
all the other python versions are being built and tested on
https://github.com/google/brotli-wheels/blob/d571d63/appveyor.yml
* remove terrify submodule as not needed any more
* [travis] just test py2.7 and 3.6 on linux; remove extra osx python builds
All the other python versions for OSX are being built/tested on:
https://github.com/google/brotli-wheels/blob/d571d63/.travis.yml
Also, there's no need to build and deploy wheels here, as that's done
in the separate repository.
* [setup.py] only rebuild if dependency are newer; fix typo in list of 'depends'
https://github.com/python/cpython/blob/v3.6.2/Lib/distutils/command/build_ext.py#L485-L500
* [ci] only run 'python setup.py test'
if we run 'python setup.py built test', the setuptools 'test' command will
forcibly re-run the build_ext subcommand because it wants to pass the --inplace
option (it ignores whether it's up to date, just re-runs it all the time).
with this we go from running built_ext twice, to running it only once per build
* [Makefile] run 'build_ext --inplace' instead of 'develop' as default target
The 'develop' command is like 'install' in the sense that it
modifies the user's python environment.
The default make target should be less intrusive, i.e. just building
the extension module in-place without modify anything in the user's
environment.
We don't need to tell make about the dependency between 'test' and
'build' target as that is baked in the `python setup.py test` command.
* [Makefile] add 'develop' target; remove unnecessary 'tests' target
`make test` is good enough
* [Makefile] `setup.py test` requires setuptools; run `python -m unittest`
This will work even if setuptools is not installed, which is unlikely
nowadays but still our `setup.py` works with plain distutils, so
we may well have our tests work without setuptools.
* [python/README.md] add ref to 'develop' target; remove 'tests', just 'make test'
* [setup.py] import modules as per nicksay's comment
https://github.com/google/brotli/pull/583#discussion_r131981049
* [Makefile] add 'develop' to .PHONY targets
remove 'tests' from .PHONY
* [appveyor] remove unused setup scripts
We don't need to install custom python versions, we are
using the pre-installed ones on Appveyor.
* [appveyor] remove unneeded setup code
2017-08-23 18:45:13 +00:00
|
|
|
language: python
|
|
|
|
python: 2.7
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=python C_COMPILER=gcc-5 CXX_COMPILER=g++-5
|
disable buidling/deployment of python wheels (#583)
* [appveyor] remove 'deploy' stage; only test python 2.7 and 3.6
all the other python versions are being built and tested on
https://github.com/google/brotli-wheels/blob/d571d63/appveyor.yml
* remove terrify submodule as not needed any more
* [travis] just test py2.7 and 3.6 on linux; remove extra osx python builds
All the other python versions for OSX are being built/tested on:
https://github.com/google/brotli-wheels/blob/d571d63/.travis.yml
Also, there's no need to build and deploy wheels here, as that's done
in the separate repository.
* [setup.py] only rebuild if dependency are newer; fix typo in list of 'depends'
https://github.com/python/cpython/blob/v3.6.2/Lib/distutils/command/build_ext.py#L485-L500
* [ci] only run 'python setup.py test'
if we run 'python setup.py built test', the setuptools 'test' command will
forcibly re-run the build_ext subcommand because it wants to pass the --inplace
option (it ignores whether it's up to date, just re-runs it all the time).
with this we go from running built_ext twice, to running it only once per build
* [Makefile] run 'build_ext --inplace' instead of 'develop' as default target
The 'develop' command is like 'install' in the sense that it
modifies the user's python environment.
The default make target should be less intrusive, i.e. just building
the extension module in-place without modify anything in the user's
environment.
We don't need to tell make about the dependency between 'test' and
'build' target as that is baked in the `python setup.py test` command.
* [Makefile] add 'develop' target; remove unnecessary 'tests' target
`make test` is good enough
* [Makefile] `setup.py test` requires setuptools; run `python -m unittest`
This will work even if setuptools is not installed, which is unlikely
nowadays but still our `setup.py` works with plain distutils, so
we may well have our tests work without setuptools.
* [python/README.md] add ref to 'develop' target; remove 'tests', just 'make test'
* [setup.py] import modules as per nicksay's comment
https://github.com/google/brotli/pull/583#discussion_r131981049
* [Makefile] add 'develop' to .PHONY targets
remove 'tests' from .PHONY
* [appveyor] remove unused setup scripts
We don't need to install custom python versions, we are
using the pre-installed ones on Appveyor.
* [appveyor] remove unneeded setup code
2017-08-23 18:45:13 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- gcc-5
|
|
|
|
- g++-5
|
disable buidling/deployment of python wheels (#583)
* [appveyor] remove 'deploy' stage; only test python 2.7 and 3.6
all the other python versions are being built and tested on
https://github.com/google/brotli-wheels/blob/d571d63/appveyor.yml
* remove terrify submodule as not needed any more
* [travis] just test py2.7 and 3.6 on linux; remove extra osx python builds
All the other python versions for OSX are being built/tested on:
https://github.com/google/brotli-wheels/blob/d571d63/.travis.yml
Also, there's no need to build and deploy wheels here, as that's done
in the separate repository.
* [setup.py] only rebuild if dependency are newer; fix typo in list of 'depends'
https://github.com/python/cpython/blob/v3.6.2/Lib/distutils/command/build_ext.py#L485-L500
* [ci] only run 'python setup.py test'
if we run 'python setup.py built test', the setuptools 'test' command will
forcibly re-run the build_ext subcommand because it wants to pass the --inplace
option (it ignores whether it's up to date, just re-runs it all the time).
with this we go from running built_ext twice, to running it only once per build
* [Makefile] run 'build_ext --inplace' instead of 'develop' as default target
The 'develop' command is like 'install' in the sense that it
modifies the user's python environment.
The default make target should be less intrusive, i.e. just building
the extension module in-place without modify anything in the user's
environment.
We don't need to tell make about the dependency between 'test' and
'build' target as that is baked in the `python setup.py test` command.
* [Makefile] add 'develop' target; remove unnecessary 'tests' target
`make test` is good enough
* [Makefile] `setup.py test` requires setuptools; run `python -m unittest`
This will work even if setuptools is not installed, which is unlikely
nowadays but still our `setup.py` works with plain distutils, so
we may well have our tests work without setuptools.
* [python/README.md] add ref to 'develop' target; remove 'tests', just 'make test'
* [setup.py] import modules as per nicksay's comment
https://github.com/google/brotli/pull/583#discussion_r131981049
* [Makefile] add 'develop' to .PHONY targets
remove 'tests' from .PHONY
* [appveyor] remove unused setup scripts
We don't need to install custom python versions, we are
using the pre-installed ones on Appveyor.
* [appveyor] remove unneeded setup code
2017-08-23 18:45:13 +00:00
|
|
|
- os: linux
|
|
|
|
language: python
|
|
|
|
python: 3.6
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=python C_COMPILER=gcc-5 CXX_COMPILER=g++-5
|
2016-06-29 03:35:16 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- gcc-5
|
|
|
|
- g++-5
|
2016-06-29 03:35:16 +00:00
|
|
|
|
|
|
|
###
|
|
|
|
## CMake on OS X
|
|
|
|
##
|
|
|
|
## These all work, but it seems unnecessary to actually build them
|
|
|
|
## all since we already test all these versions of GCC on Linux.
|
|
|
|
## We'll just test 4.4 and the most recent version.
|
|
|
|
###
|
2017-09-18 11:52:53 +00:00
|
|
|
- os: osx
|
2018-09-13 12:09:32 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=gcc CXX_COMPILER=g++
|
2016-06-29 03:35:16 +00:00
|
|
|
- os: osx
|
2018-04-13 09:44:34 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=gcc-4.9 CXX_COMPILER=g++-4.9
|
|
|
|
- os: osx
|
|
|
|
env: BUILD_SYSTEM=cmake
|
2016-06-29 03:35:16 +00:00
|
|
|
|
|
|
|
###
|
disable buidling/deployment of python wheels (#583)
* [appveyor] remove 'deploy' stage; only test python 2.7 and 3.6
all the other python versions are being built and tested on
https://github.com/google/brotli-wheels/blob/d571d63/appveyor.yml
* remove terrify submodule as not needed any more
* [travis] just test py2.7 and 3.6 on linux; remove extra osx python builds
All the other python versions for OSX are being built/tested on:
https://github.com/google/brotli-wheels/blob/d571d63/.travis.yml
Also, there's no need to build and deploy wheels here, as that's done
in the separate repository.
* [setup.py] only rebuild if dependency are newer; fix typo in list of 'depends'
https://github.com/python/cpython/blob/v3.6.2/Lib/distutils/command/build_ext.py#L485-L500
* [ci] only run 'python setup.py test'
if we run 'python setup.py built test', the setuptools 'test' command will
forcibly re-run the build_ext subcommand because it wants to pass the --inplace
option (it ignores whether it's up to date, just re-runs it all the time).
with this we go from running built_ext twice, to running it only once per build
* [Makefile] run 'build_ext --inplace' instead of 'develop' as default target
The 'develop' command is like 'install' in the sense that it
modifies the user's python environment.
The default make target should be less intrusive, i.e. just building
the extension module in-place without modify anything in the user's
environment.
We don't need to tell make about the dependency between 'test' and
'build' target as that is baked in the `python setup.py test` command.
* [Makefile] add 'develop' target; remove unnecessary 'tests' target
`make test` is good enough
* [Makefile] `setup.py test` requires setuptools; run `python -m unittest`
This will work even if setuptools is not installed, which is unlikely
nowadays but still our `setup.py` works with plain distutils, so
we may well have our tests work without setuptools.
* [python/README.md] add ref to 'develop' target; remove 'tests', just 'make test'
* [setup.py] import modules as per nicksay's comment
https://github.com/google/brotli/pull/583#discussion_r131981049
* [Makefile] add 'develop' to .PHONY targets
remove 'tests' from .PHONY
* [appveyor] remove unused setup scripts
We don't need to install custom python versions, we are
using the pre-installed ones on Appveyor.
* [appveyor] remove unneeded setup code
2017-08-23 18:45:13 +00:00
|
|
|
## Python 2.7 OS X build (using the system /usr/bin/python)
|
2016-06-29 03:35:16 +00:00
|
|
|
###
|
|
|
|
- os: osx
|
disable buidling/deployment of python wheels (#583)
* [appveyor] remove 'deploy' stage; only test python 2.7 and 3.6
all the other python versions are being built and tested on
https://github.com/google/brotli-wheels/blob/d571d63/appveyor.yml
* remove terrify submodule as not needed any more
* [travis] just test py2.7 and 3.6 on linux; remove extra osx python builds
All the other python versions for OSX are being built/tested on:
https://github.com/google/brotli-wheels/blob/d571d63/.travis.yml
Also, there's no need to build and deploy wheels here, as that's done
in the separate repository.
* [setup.py] only rebuild if dependency are newer; fix typo in list of 'depends'
https://github.com/python/cpython/blob/v3.6.2/Lib/distutils/command/build_ext.py#L485-L500
* [ci] only run 'python setup.py test'
if we run 'python setup.py built test', the setuptools 'test' command will
forcibly re-run the build_ext subcommand because it wants to pass the --inplace
option (it ignores whether it's up to date, just re-runs it all the time).
with this we go from running built_ext twice, to running it only once per build
* [Makefile] run 'build_ext --inplace' instead of 'develop' as default target
The 'develop' command is like 'install' in the sense that it
modifies the user's python environment.
The default make target should be less intrusive, i.e. just building
the extension module in-place without modify anything in the user's
environment.
We don't need to tell make about the dependency between 'test' and
'build' target as that is baked in the `python setup.py test` command.
* [Makefile] add 'develop' target; remove unnecessary 'tests' target
`make test` is good enough
* [Makefile] `setup.py test` requires setuptools; run `python -m unittest`
This will work even if setuptools is not installed, which is unlikely
nowadays but still our `setup.py` works with plain distutils, so
we may well have our tests work without setuptools.
* [python/README.md] add ref to 'develop' target; remove 'tests', just 'make test'
* [setup.py] import modules as per nicksay's comment
https://github.com/google/brotli/pull/583#discussion_r131981049
* [Makefile] add 'develop' to .PHONY targets
remove 'tests' from .PHONY
* [appveyor] remove unused setup scripts
We don't need to install custom python versions, we are
using the pre-installed ones on Appveyor.
* [appveyor] remove unneeded setup code
2017-08-23 18:45:13 +00:00
|
|
|
env: BUILD_SYSTEM=python C_COMPILER=gcc CXX_COMPILER=g++
|
2016-06-29 03:35:16 +00:00
|
|
|
|
|
|
|
###
|
|
|
|
## Sanitizers
|
|
|
|
###
|
2016-07-23 03:09:09 +00:00
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=clang-5.0 CXX_COMPILER=clang++-5.0 SANITIZER=address ASAN_OPTIONS=detect_leaks=0
|
2016-07-23 03:09:09 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
2017-11-30 19:54:04 +00:00
|
|
|
- llvm-toolchain-trusty-5.0
|
2016-07-23 03:09:09 +00:00
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- clang-5.0
|
2016-07-26 15:22:58 +00:00
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=clang-5.0 CXX_COMPILER=clang++-5.0 SANITIZER=thread
|
2016-07-26 15:22:58 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
2017-11-30 19:54:04 +00:00
|
|
|
- llvm-toolchain-trusty-5.0
|
2016-07-26 15:22:58 +00:00
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- clang-5.0
|
2016-07-28 20:31:09 +00:00
|
|
|
- os: linux
|
2017-11-30 19:54:04 +00:00
|
|
|
env: BUILD_SYSTEM=cmake C_COMPILER=clang-5.0 CXX_COMPILER=clang++-5.0 SANITIZER=undefined CFLAGS="-fno-sanitize-recover=undefined,integer"
|
2016-07-28 20:31:09 +00:00
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
|
|
|
- ubuntu-toolchain-r-test
|
2017-11-30 19:54:04 +00:00
|
|
|
- llvm-toolchain-trusty-5.0
|
2016-07-28 20:31:09 +00:00
|
|
|
packages:
|
2017-11-30 19:54:04 +00:00
|
|
|
- clang-5.0
|
2016-07-28 20:31:09 +00:00
|
|
|
|
2017-03-22 18:13:59 +00:00
|
|
|
- os: linux
|
|
|
|
env: BUILD_SYSTEM=maven
|
|
|
|
language: java
|
|
|
|
|
2017-03-23 12:35:53 +00:00
|
|
|
- os: linux
|
|
|
|
sudo: required
|
2017-06-22 08:58:13 +00:00
|
|
|
language: java
|
2018-09-13 12:09:32 +00:00
|
|
|
jdk: oraclejdk9
|
2017-03-23 12:35:53 +00:00
|
|
|
env: BUILD_SYSTEM=bazel
|
|
|
|
addons:
|
|
|
|
apt:
|
|
|
|
sources:
|
2017-06-22 09:38:49 +00:00
|
|
|
- sourceline: "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8"
|
|
|
|
key_url: "https://storage.googleapis.com/bazel-apt/doc/apt-key.pub.gpg"
|
2017-03-23 12:35:53 +00:00
|
|
|
- ubuntu-toolchain-r-test
|
|
|
|
packages:
|
2017-06-22 09:38:49 +00:00
|
|
|
- bazel
|
2017-03-23 12:35:53 +00:00
|
|
|
|
|
|
|
- os: osx
|
|
|
|
env: BUILD_SYSTEM=bazel
|
2018-09-13 12:09:32 +00:00
|
|
|
# Latest image with Java 1.8 (required to install Bazel).
|
|
|
|
osx_image: xcode9.3
|
|
|
|
language: java
|
2017-03-23 12:35:53 +00:00
|
|
|
|
2016-06-29 03:35:16 +00:00
|
|
|
before_install:
|
|
|
|
###
|
2016-07-26 15:22:58 +00:00
|
|
|
## If we use the matrix to set CC/CXX Travis, overwrites the values,
|
2016-06-29 03:35:16 +00:00
|
|
|
## so instead we use C/CXX_COMPILER, then copy the values to CC/CXX
|
|
|
|
## here (after Travis has set CC/CXX).
|
|
|
|
###
|
|
|
|
- if [ -n "${C_COMPILER}" ]; then export CC="${C_COMPILER}"; fi
|
|
|
|
- if [ -n "${CXX_COMPILER}" ]; then export CXX="${CXX_COMPILER}"; fi
|
2017-04-23 12:07:08 +00:00
|
|
|
- scripts/.travis.sh before_install
|
2015-08-11 11:39:49 +00:00
|
|
|
install:
|
2017-04-23 12:07:08 +00:00
|
|
|
- scripts/.travis.sh install
|
2015-08-11 11:39:49 +00:00
|
|
|
script:
|
2017-04-23 12:07:08 +00:00
|
|
|
- scripts/.travis.sh script
|
2015-08-11 11:39:49 +00:00
|
|
|
after_success:
|
2017-04-23 12:07:08 +00:00
|
|
|
- scripts/.travis.sh after_success
|
2016-06-23 19:20:37 +00:00
|
|
|
|
2015-08-11 11:39:49 +00:00
|
|
|
before_deploy:
|
2017-04-23 12:07:08 +00:00
|
|
|
- scripts/.travis.sh before_deploy
|
2015-08-12 14:57:03 +00:00
|
|
|
|
2015-08-31 13:34:42 +00:00
|
|
|
deploy:
|
2017-03-24 11:54:20 +00:00
|
|
|
- provider: bintray
|
2017-04-23 12:07:08 +00:00
|
|
|
file: "scripts/.bintray.json"
|
2017-03-24 11:54:20 +00:00
|
|
|
user: "eustas"
|
|
|
|
key:
|
|
|
|
secure: "Kbam/lTAdz72fZivbs6riJT+Y4PbuKP7r6t5PAWxJxAAykjwnYTRe3zF472g9HCE14KYMsdB+KSYSgg6TGJnqGC9gL9xhhGU9U/WmA+vbMWS/MSnMWpK9IRpp77pM2i2NKZD4v33JuEwKFCBJP3Vj6QQ5Qd1NKdobuXJyznhgnw="
|
|
|
|
on:
|
|
|
|
condition: "${BUILD_SYSTEM} = bazel"
|
|
|
|
skip_cleanup: true
|