moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-18 07:25:14 -05:00
Code Issues Releases Wiki Activity
9275c2be8c
curl/.travis.yml

442 lines
15 KiB
YAML
Raw Normal View History

travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
language: c
travis: install nghttp2 on linux builds Closes #1642
2017-07-04 17:03:49 -04:00
sudo: required
travis: build libpsl and make builds use it closes #2471
2018-04-08 18:11:04 -04:00
cache:
directories:
travis: bump the used wolfSSL version to 4.0.0 Test 311 is now fine, leaving only 313 (CRL) disabled. Test 313 details can be found here: https://github.com/wolfSSL/wolfssl/issues/1546 Closes #3697
2019-03-22 05:59:51 -04:00
- $HOME/wolfssl-4.0.0-stable
travis: upgrade the MesaLink TLS backend to v1.0.0 Closes #3823 Closes #3776
2019-04-30 18:46:46 -04:00
- $HOME/mesalink-1.0.0
travis: bump to using nghttp2 version 1.39.2 Closes #4252
2019-08-21 02:29:59 -04:00
- $HOME/nghttp2-1.39.2
travis: build libpsl and make builds use it closes #2471
2018-04-08 18:11:04 -04:00
env:
global:
- LD_LIBRARY_PATH=/usr/local/lib
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
addons:
apt:
travis: enable apt retry on fail This is a workaround for an unsolved travis issue that is causing CI instances to sporadically fail due to 'unable to connect' issues during apt stage. Ref: https://github.com/travis-ci/travis-ci/issues/8507 Ref: https://github.com/travis-ci/travis-ci/issues/9112#issuecomment-376305909
2018-03-26 18:29:30 -04:00
config:
retries: true
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
sources: &common_sources
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- ubuntu-toolchain-r-test
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages: &common_packages
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- cmake
travis: update to GCC 8 Closes https://github.com/curl/curl/pull/2869
2018-08-09 08:48:28 -04:00
- gcc-8
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- valgrind
travis: install nghttp2 on linux builds Closes #1642
2017-07-04 17:03:49 -04:00
- libev-dev
- libc-ares-dev
travis: update to GCC 8 Closes https://github.com/curl/curl/pull/2869
2018-08-09 08:48:28 -04:00
- g++-8
- libstdc++-8-dev
travis: install stunnel
2017-07-07 10:42:44 -04:00
- stunnel4
travis: install libidn2 Install libidn2 to increase test coverage (IDN tests) Closes https://github.com/curl/curl/pull/1673
2017-07-10 12:56:36 -04:00
- libidn2-0-dev
travis: install gnutls-bin package This is required for gnutls-serv, which enables a few more tests. Closes https://github.com/curl/curl/pull/2958
2018-09-08 16:44:16 -04:00
- gnutls-bin
travis: Upgrading to container based build http://docs.travis-ci.com/user/migrating-from-legacy Closes #388
2015-08-17 12:08:55 -04:00
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
matrix:
include:
- os: linux
compiler: gcc
travis: explicitly specify dist This makes the builds more reproducible as travis is currently rolling out trusty as default dist [1]. Specifically, this avoids coverage check failures when trusty is used as seen in [2] until we figure out what's wrong. [1] https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming [2] https://github.com/curl/curl/pull/1692 Closes https://github.com/curl/curl/pull/1725
2017-08-03 05:01:25 -04:00
dist: trusty
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=normal C="--with-gssapi --with-libssh2" CHECKSRC=1
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: install krb5-user only for --with-gssapi build Reduces the time needed for the other jobs a little. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:46:23 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- krb5-user
travis: install libssh2-dev only for --with-libssh2 build Reduces the time needed for the other jobs a little. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:56:18 -04:00
- libssh2-1-dev
.travis.yml: added build --with-libssh Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com>
2017-10-31 03:44:24 -04:00
- os: linux
compiler: gcc
dist: trusty
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=normal C=--with-libssh
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: install libssh-dev only for --with-libssh build Reduces the time needed for the other jobs a little. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:51:21 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libssh-dev
travis: add c-ares enabled builds linux + osx Closes #1868
2017-09-06 04:05:05 -04:00
- os: linux
compiler: gcc
dist: trusty
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=normal C="--enable-ares"
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: add build for "configure --disable-verbose" Closes #3144
2018-10-16 17:35:44 -04:00
- os: linux
compiler: gcc
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=normal C="--disable-verbose" CPPFLAGS="-Wno-variadic-macros" NOTESTS=1
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add boringssl build Uses a separate build without --enable-debug and no valgrind. The debug option causes far too many warnings in boringssl's headers (C++ comments, trailing commas etc). Valgrind triggers some false positive errors in thread-local data used by boringssl. Closes #2118
2017-11-27 13:55:25 -05:00
- os: linux
compiler: gcc
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: move the go install to linux-only ... to repair the build again Closes #4403
2019-09-25 08:34:31 -04:00
before_install:
# Install and use the current stable release of Go
- gimme --list
- eval "$(gimme stable)"
- gimme --list
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=novalgrind BORINGSSL=yes C="--with-ssl=$HOME/boringssl" LD_LIBRARY_PATH=/home/travis/boringssl/lib:/usr/local/lib
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
addons:
apt:
sources:
travis: use go master ... as the boringssl builds needs a very recent version Co-authored-by: Jat Satiro Closes #4361
2019-09-16 03:02:03 -04:00
- ppa:longsleep/golang-backports
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- *common_sources
packages:
- *common_packages
travis: add a quiche build Closes #4207
2019-08-10 17:28:57 -04:00
- os: linux
compiler: gcc
dist: xenial
travis: move the go install to linux-only ... to repair the build again Closes #4403
2019-09-25 08:34:31 -04:00
before_install:
# Install and use the current stable release of Go
- gimme --list
- eval "$(gimme stable)"
- gimme --list
travis: add a quiche build Closes #4207
2019-08-10 17:28:57 -04:00
env:
configure: use pkg-config to detect quiche This removes the need to hard-code the quiche target path in configure.ac. This depends on https://github.com/cloudflare/quiche/pull/128 Closes #4237
2019-08-18 10:03:51 -04:00
- T=novalgrind BORINGSSL=yes QUICHE="yes" C="--with-ssl=$HOME/boringssl --with-quiche=$HOME/quiche/target/release --enable-alt-svc" LD_LIBRARY_PATH=/home/travis/boringssl/lib:$HOME/quiche/target/release:/usr/local/lib
travis: add a quiche build Closes #4207
2019-08-10 17:28:57 -04:00
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
- libbrotli-dev
travis: enable ngtcp2 h3-23 builds
2019-09-21 09:47:07 -04:00
- os: linux
compiler: gcc
dist: xenial
env:
- T=novalgrind NGTCP2=yes C="--with-ssl=$HOME/ngbuild --with-ngtcp2=$HOME/ngbuild --with-nghttp3=$HOME/ngbuild --enable-alt-svc" NOTESTS=
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
- libbrotli-dev
travis: add a build using WolfSSL Assisted-by: Dan Fandrich Closes #2528
2018-04-24 10:16:25 -04:00
- os: linux
compiler: gcc
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug-wolfssl C="--with-wolfssl --without-ssl"
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: upgrade the MesaLink TLS backend to v1.0.0 Closes #3823 Closes #3776
2019-04-30 18:46:46 -04:00
- os: linux
compiler: gcc
travis: update mesalink build to xenial Closes https://github.com/curl/curl/pull/3842
2019-05-04 13:39:49 -04:00
dist: xenial
travis: upgrade the MesaLink TLS backend to v1.0.0 Closes #3823 Closes #3776
2019-04-30 18:46:46 -04:00
env:
- T=debug-mesalink C="--with-mesalink --without-ssl"
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
- libbrotli-dev
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
alt-svc: add a travis build
2019-03-03 05:17:52 -05:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug C="--enable-alt-svc"
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add an mbedtls build Closes #2531
2018-04-25 03:20:08 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug C="--with-mbedtls --without-ssl"
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: use mbedtls from Xenial No need to build it from source anymore. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:48:37 -04:00
- libmbedtls-dev
travis: add build using gnutls Closes #3637
2019-03-01 16:00:27 -05:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug C="--with-gnutls --without-ssl"
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: install libgnutls28-dev only for --with-gnutls build Reduces the time needed for the other jobs a little. Closes https://github.com/curl/curl/pull/3721
2019-04-02 09:06:47 -04:00
- libgnutls28-dev
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add build using NSS Closes #2558
2018-05-10 02:56:46 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug C="--with-nss --without-ssl" NOTESTS=1 CPPFLAGS="-isystem /usr/include/nss"
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: install libnss3-dev only for --with-nss build Reduces the time needed for the other jobs a little. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:58:33 -04:00
- libnss3-dev
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add build with iconv enabled ... to verify it builds and works fine. Ref: https://curl.haxx.se/mail/lib-2017-09/0031.html Closes #1872
2017-09-07 06:42:30 -04:00
- os: linux
compiler: gcc
dist: trusty
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=iconv
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: add an osx http-only build Closes #3887
2019-05-15 02:57:00 -04:00
- os: osx
compiler: gcc
env: T=debug C="--disable-dict --disable-file --disable-ftp --disable-gopher --disable-imap --disable-ldap --disable-pop3 --disable-rtmp --disable-rtsp --disable-scp --disable-sftp --disable-smb --disable-smtp --disable-telnet --disable-tftp --disable-unix-sockets --disable-shared --enable-debug --enable-maintainer-mode --without-brotli --without-gssapi --without-libidn2 --without-libmetalink --without-libpsl --without-librtmp --without-libssh2 --without-nghttp2 --without-ntlm-auth --without-ssl --without-zlib"
travis: add c-ares enabled builds linux + osx Closes #1868
2017-09-06 04:05:05 -04:00
- os: osx
compiler: gcc
env: T=debug C=--enable-ares
travis: build osx with openssl too
2017-08-02 04:28:00 -04:00
- os: osx
compiler: gcc
travis: add metalink to some osx builds Closes #1790
2017-08-16 05:37:07 -04:00
env: T=debug C="--with-ssl=/usr/local/opt/openssl --with-libmetalink"
travis: build osx with libressl too
2017-08-02 04:32:15 -04:00
- os: osx
compiler: gcc
travis: add metalink to some osx builds Closes #1790
2017-08-16 05:37:07 -04:00
env: T=debug C="--with-ssl=/usr/local/opt/libressl --with-libmetalink"
travis: add osx build with darwinssl Closes #1706
2017-08-03 18:04:39 -04:00
- os: osx
compiler: clang
travis: bump the Secure Transport build to use xcode 10 Due to an issue with travis (https://github.com/travis-ci/travis-ci/issues/9956) we've been using Xcode 9.2 for darwinssl builds for a while. Now xcode 10 is offered as an alternative and as it builds curl+darwinssl fine that seems like a better choice. Closes #3062
2018-09-29 05:19:47 -04:00
osx_image: xcode10
travis: add metalink to some osx builds Closes #1790
2017-08-16 05:37:07 -04:00
env: T=debug C="--without-ssl --with-darwinssl --with-libmetalink"
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- os: osx
compiler: clang
travis: BUILD_TYPE => T (to make the full line appear nicer on travis web UI)
2017-08-03 18:04:39 -04:00
env: T=normal
travis: added cmake build for osx
2019-01-14 10:14:48 -05:00
- os: osx
compiler: clang
env: T=cmake
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- os: linux
compiler: gcc
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=cmake
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=cmake
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- os: linux
compiler: gcc
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
travis: remove "coverage", make it "torture" The coveralls service and test coverage numbers are just too unreliable. Removed badge from README.md as well. Fixes #4694 Closes #4695
2019-12-10 03:36:46 -05:00
- T=torture
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: install lcov only for the coverage job Reduces the time needed for the other jobs a little. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:35:19 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- lcov
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: enable libssh2 for coverage build It was enabled by default before commit c92d2e14cfb. Disable torture tests 600 and 601 because of https://github.com/curl/curl/issues/1678. Closes
2019-06-12 14:59:12 -04:00
- libssh2-1-dev
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
- os: linux
compiler: gcc
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=distcheck
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
ossfuzz: moving towards the ideal integration - Start with the basic code from the ossfuzz project. - Rewrite fuzz corpora to be binary files full of Type-Length-Value data, and write a glue layer in the fuzzing function to convert corpora into CURL options. - Have supporting functions to generate corpora from existing tests - Integrate with Makefile.am
2017-08-27 10:57:05 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=fuzzer
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add a "make tidy" build that runs clang-tidy Closes #3182
2018-10-27 10:02:48 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=tidy
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
- clang-tidy-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: add scan-build Closes #3564
2017-11-20 17:31:05 -05:00
- os: linux
compiler: clang
travis: update scan-build job to xenial Closes https://github.com/curl/curl/pull/3999
2019-06-08 09:02:07 -04:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=scan-build
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: use xenial LLVM package for scan-build I missed that in commit 99a49d6.
2019-06-09 07:20:57 -04:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: update scan-build job to xenial Closes https://github.com/curl/curl/pull/3999
2019-06-08 09:02:07 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: build with sanitize=address,undefined,signed-integer-overflow ... using clang Closes #3190
2018-10-29 11:18:34 -04:00
- os: linux
compiler: clang
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
dist: xenial
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
env:
- T=debug CFLAGS="-fsanitize=address,undefined,signed-integer-overflow -fno-sanitize-recover=undefined,integer -Wformat -Werror=format-security -Werror=array-bounds -g" LDFLAGS="-fsanitize=address,undefined -fno-sanitize-recover=undefined,integer" LIBS="-ldl -lubsan"
- OVERRIDE_CC="CC=clang-7" OVERRIDE_CXX="CXX=clang++-7"
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
addons:
apt:
sources:
- *common_sources
travis: update some builds to xenial Xenial comes with more up-to-date software versions and more available packages, some of which we currently build from source. Unfortunately, some builds would fail with Xenial because of assertion failures in Valgrind when using OpenSSL, so leave these at Trusty. Closes https://github.com/curl/curl/pull/3777
2019-03-08 14:26:10 -05:00
- llvm-toolchain-xenial-7
travis: install clang only when needed This reduces the GCC job runtimes a little and it's needed to selectively update clang builds to xenial. Closes https://github.com/curl/curl/pull/3721
2019-04-02 08:31:06 -04:00
packages:
- *common_packages
- clang-7
travis: use libpsl from Xenial This makes building libpsl and libidn2 from source unnecessary and removes the need for the autopoint and libunistring-dev packages. Closes https://github.com/curl/curl/pull/3779
2019-04-14 08:42:23 -04:00
- libpsl-dev
travis: enable brotli for all xenial jobs There's no need for a separate job, and no need to build it from source with Xenial. Closes
2019-06-12 10:15:39 -04:00
- libbrotli-dev
travis: Add an ARM64 build Test 323 is failing for some reason, so disable it there for now.
2019-10-17 04:24:28 -04:00
- os: linux
arch: arm64
compiler: gcc
dist: xenial
env:
- T=debug C="--enable-alt-svc"
- OVERRIDE_CC="CC=gcc-8" OVERRIDE_CXX="CXX=g++-8"
addons:
apt:
sources:
- *common_sources
packages:
- *common_packages
- libpsl-dev
- libbrotli-dev
- libev-dev
- libssl-dev
- libtool
- pkg-config
- zlib1g-dev
travis: actually use updated compiler versions For the Linux builds, GCC 8 and 7 and clang 7 were installed, but the new GCC versions were only used for the coverage build and for building nghttp2, while the new clang version was not used at all. BoringSSL needs to use the default GCC as it respects CC, but not CXX, so it would otherwise pass gcc 8 options to g++ 4.8 and fail. Also remove GCC 7, it's not needed anymore. Ref: https://docs.travis-ci.com/user/languages/c/#c11c11-and-beyond-and-toolchain-versioning Closes https://github.com/curl/curl/pull/3670
2019-03-09 15:15:18 -05:00
before_install:
travis: do not use OVERRIDE_CC or OVERRIDE_CXX if empty Fixes the macOS builds where OVERRIDE_CC and OVERRIDE_CXX are not set. Reported-by: Jay Satiro Fixes #4659 Closes #4661 Closes #4664
2019-11-30 13:42:20 -05:00
- export "${OVERRIDE_CC-blank=}"
- export "${OVERRIDE_CXX-blank=}"
Adding a .travis.yml file to use the travis-ci.org From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).
2013-10-17 09:10:18 -04:00
travis.yml: Add OS X testbot.
2015-08-21 00:10:59 -04:00
install:
travis: use pip2 instead of pip .. since now mac osx image expects pip2 or pip3, and doesn't know pip: 0.01s$ pip install --user cpp-coveralls /Users/travis/.travis/job_stages: line 57: pip: command not found Ref: https://github.com/travis-ci/travis-ci/issues/8829 Closes https://github.com/curl/curl/pull/2133
2017-12-01 03:03:26 -05:00
- if [ "$T" = "coverage" ]; then pip2 install --user cpp-coveralls; fi
travis.yml: Add OS X testbot.
2015-08-21 00:10:59 -04:00
- if [ "$TRAVIS_OS_NAME" == "osx" ]; then brew update > /dev/null; fi
travis: removed option to rebuild autotool from source Fixes #943
2016-08-02 06:43:23 -04:00
- if [ "$TRAVIS_OS_NAME" == "osx" ]; then brew reinstall libtool > /dev/null; fi
travis: on mac, don't install openssl or libidn - openssl is already installed and causes warnings when trying to install again - libidn isn't used these days, and homebrew doesn't seem to have a libidn2 package to replace with easily Closes #1895
2017-09-18 04:49:38 -04:00
- if [ "$TRAVIS_OS_NAME" == "osx" ]; then brew install rtmpdump libssh2 c-ares libmetalink libressl nghttp2 libmetalink; fi
travis.yml: Add OS X testbot.
2015-08-21 00:10:59 -04:00
travis: Fix error detection - Stop using inline shell scripts for before_script and script sections. Prior to this change Travis could ignore errors from commands in inline scripts. I don't understand how or why it happens. This is a workaround. Assisted-by: Simon Warta Ref: https://github.com/travis-ci/travis-ci/issues/1066 Fixes https://github.com/curl/curl/issues/3730 Closes https://github.com/curl/curl/pull/3755
2019-12-28 01:56:05 -05:00
# before_script and script:
# Travis isn't reliable catching errors in inline script commands (#3730).
# Do not add anything here, instead add to the respective script.
Adding a .travis.yml file to use the travis-ci.org From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).
2013-10-17 09:10:18 -04:00
before_script:
travis: Fix error detection - Stop using inline shell scripts for before_script and script sections. Prior to this change Travis could ignore errors from commands in inline scripts. I don't understand how or why it happens. This is a workaround. Assisted-by: Simon Warta Ref: https://github.com/travis-ci/travis-ci/issues/1066 Fixes https://github.com/curl/curl/issues/3730 Closes https://github.com/curl/curl/pull/3755
2019-12-28 01:56:05 -05:00
- ./scripts/travis/before_script.sh || travis_terminate 1
travis: add coverage, distcheck and cmake builds Closes #1534
2017-06-03 17:27:13 -04:00
script:
travis: Fix error detection - Stop using inline shell scripts for before_script and script sections. Prior to this change Travis could ignore errors from commands in inline scripts. I don't understand how or why it happens. This is a workaround. Assisted-by: Simon Warta Ref: https://github.com/travis-ci/travis-ci/issues/1066 Fixes https://github.com/curl/curl/issues/3730 Closes https://github.com/curl/curl/pull/3755
2019-12-28 01:56:05 -05:00
- ./scripts/travis/script.sh || travis_terminate 1
Adding a .travis.yml file to use the travis-ci.org From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).
2013-10-17 09:10:18 -04:00
ci: whitelist branches to avoid testing feature branches twice
2017-06-20 17:00:49 -04:00
# whitelist branches to avoid testing feature branches twice (as branch and as pull request)
branches:
only:
- master
travis: allow builds on branches named "ci" This allows a way to test changes other than through PRs.
2019-03-15 09:38:48 -04:00
- /\/ci$/
ci: whitelist branches to avoid testing feature branches twice
2017-06-20 17:00:49 -04:00
Adding a .travis.yml file to use the travis-ci.org From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).
2013-10-17 09:10:18 -04:00
notifications:
email: false
Reference in New Issue Copy Permalink