wbrawner/openssl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
openssl/.travis.yml

197 lines
6.9 KiB
YAML
Raw Normal View History

Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
language: c
Use ccache for the unified builds This may speed up our builds considerably Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-03-06 23:33:35 +00:00
cache: ccache
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
Add a coverage target Run tests with coverage and report to coveralls.io For simplicity, this currently only adds a single target in a configuration that attempts to maximize coverage. The true CI coverage from all the various builds may be a little larger. The coverage run has the following configuration: - no-asm: since we can't track asm coverage anyway, might as well measure the non-asm code coverage. - Enable various disabled-by-default options: - rc5 - md2 - ec_nistp_64_gcc_128 - ssl3 - ssl3-method - weak-ssl-ciphers Finally, observe that no-pic implies no-shared, and therefore running both builds in the matrix is redundant. Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
2016-08-03 13:29:21 +00:00
before_install:
.travis.yml: minor optimizations: - make 'pip install --user cpp-coveralls' conditional; - limit no-stdio to single build per operating environment; - omit enable-asan duplicate; Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-10-10 10:22:10 +00:00
- if [ -n "$COVERALLS" ]; then
pip install --user cpp-coveralls;
fi;
Add a coverage target Run tests with coverage and report to coveralls.io For simplicity, this currently only adds a single target in a configuration that attempts to maximize coverage. The true CI coverage from all the various builds may be a little larger. The coverage run has the following configuration: - no-asm: since we can't track asm coverage anyway, might as well measure the non-asm code coverage. - Enable various disabled-by-default options: - rc5 - md2 - ec_nistp_64_gcc_128 - ssl3 - ssl3-method - weak-ssl-ciphers Finally, observe that no-pic implies no-shared, and therefore running both builds in the matrix is redundant. Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
2016-08-03 13:29:21 +00:00
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
addons:
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-12 20:15:43 +00:00
apt:
packages:
Use ccache for the unified builds This may speed up our builds considerably Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-03-06 23:33:35 +00:00
- ccache
Run BoringSSL tests on Travis Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-11-09 16:25:35 +00:00
- golang
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
os:
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
- linux
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
compiler:
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
- clang
- gcc
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
env:
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
- CONFIG_OPTS="" DESTDIR="_install" TESTS="-test_fuzz"
- CONFIG_OPTS="no-asm -Werror --debug no-shared enable-crypto-mdebug enable-rc5 enable-md2" TESTS="-test_fuzz"
- CONFIG_OPTS="no-asm --strict-warnings" BUILDONLY="yes" CHECKDOCS="yes"
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
matrix:
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-12 20:15:43 +00:00
include:
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
- os: linux
addons:
apt:
packages:
- gcc-5
- g++-5
sources:
- ubuntu-toolchain-r-test
compiler: gcc-5
env: CONFIG_OPTS="--strict-warnings enable-tls1_3" TESTS="-test_fuzz" COMMENT="Move to the BORINGTEST build when interoperable"
Travis: add a strict build Clang on Linux seems to catch things that we might miss otherwise. Also, throw in 'no-deprecated' to make sure we test that as well. Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/1839)
2016-11-03 15:46:14 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- clang-3.6
sources:
- llvm-toolchain-precise-3.6
- ubuntu-toolchain-r-test
Travis: add a strict build Clang on Linux seems to catch things that we might miss otherwise. Also, throw in 'no-deprecated' to make sure we test that as well. Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/1839)
2016-11-03 15:46:14 +00:00
compiler: clang-3.6
env: CONFIG_OPTS="--strict-warnings no-deprecated" BUILDONLY="yes"
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
- os: linux
addons:
apt:
packages:
- binutils-mingw-w64
- gcc-mingw-w64
compiler: i686-w64-mingw32-gcc
env: CONFIG_OPTS="no-stdio" BUILDONLY="yes"
Add a coverage target Run tests with coverage and report to coveralls.io For simplicity, this currently only adds a single target in a configuration that attempts to maximize coverage. The true CI coverage from all the various builds may be a little larger. The coverage run has the following configuration: - no-asm: since we can't track asm coverage anyway, might as well measure the non-asm code coverage. - Enable various disabled-by-default options: - rc5 - md2 - ec_nistp_64_gcc_128 - ssl3 - ssl3-method - weak-ssl-ciphers Finally, observe that no-pic implies no-shared, and therefore running both builds in the matrix is redundant. Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
2016-08-03 13:29:21 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- gcc-5
- g++-5
sources:
- ubuntu-toolchain-r-test
Run BoringSSL tests on Travis Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-11-09 16:25:35 +00:00
compiler: gcc-5
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="--debug --coverage no-asm enable-rc5 enable-md2 enable-ec_nistp_64_gcc_128 enable-ssl3 enable-ssl3-method enable-nextprotoneg enable-weak-ssl-ciphers enable-external-tests no-shared -DPEDANTIC -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION" COVERALLS="yes" BORINGSSL_TESTS="yes" CXX="g++-5"
Add memory sanitizer config, and run on travis. Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-07-28 18:24:28 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- clang-3.6
sources:
- llvm-toolchain-precise-3.6
- ubuntu-toolchain-r-test
Add memory sanitizer config, and run on travis. Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-07-28 18:24:28 +00:00
compiler: clang-3.6
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="enable-msan"
Add Clang 3.6 and additional GCC 5 builds to travis Follow-up to f386742. Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-06 18:27:50 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- clang-3.6
sources:
- llvm-toolchain-precise-3.6
- ubuntu-toolchain-r-test
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 12:51:16 +00:00
compiler: clang-3.6
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="no-asm enable-ubsan enable-rc5 enable-md2 enable-ssl3 enable-ssl3-method enable-nextprotoneg -fno-sanitize=alignment no-shared -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION"
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 12:51:16 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- clang-3.6
sources:
- llvm-toolchain-precise-3.6
- ubuntu-toolchain-r-test
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 12:51:16 +00:00
compiler: clang-3.6
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="no-asm enable-asan enable-rc5 enable-md2 no-shared -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION"
Add Clang 3.6 and additional GCC 5 builds to travis Follow-up to f386742. Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-06 18:27:50 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- gcc-5
- g++-5
sources:
- ubuntu-toolchain-r-test
Add Clang 3.6 and additional GCC 5 builds to travis Follow-up to f386742. Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-06 18:27:50 +00:00
compiler: gcc-5
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="no-asm enable-ubsan enable-rc5 enable-md2 -DPEDANTIC"
Travis: add a build with no-stdio Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-08-04 22:48:44 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- binutils-mingw-w64
- gcc-mingw-w64
Travis: add a build with no-stdio Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-08-04 22:48:44 +00:00
compiler: i686-w64-mingw32-gcc
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="no-pic" TESTS="-test_fuzz"
Restore some mingw builds "no-pic" builds have in fact been green (and reasonably fast), so restore them while we figure out why tests without "no-pic" hang. Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-03-07 11:59:40 +00:00
- os: linux
.travis.yml: make package pulls conditional. Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-01-26 00:02:43 +00:00
addons:
apt:
packages:
- binutils-mingw-w64
- gcc-mingw-w64
Travis: add a build with no-stdio Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-08-04 22:48:44 +00:00
compiler: x86_64-w64-mingw32-gcc
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
env: EXTENDED_TEST="yes" CONFIG_OPTS="no-pic" TESTS="-test_fuzz"
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
exclude:
Trim Travis config part 3 - Only build & test two configurations. Make all the other build variants buildonly on gcc (clang on osx). - Don't build with default clang at all on linux. - Only use gcc-5 and clang-3.6 for the sanitizer builds. Re-running e.g. CONFIG_OPTS="shared" with them seems redundant. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-03-07 14:15:20 +00:00
- os: linux
compiler: clang
.travis.yml: exclude gcc from MacOS X CI builds. Contemporary Xcode gcc is a front-end to clang, so that explicit gcc build is actually redundant on MacOS X. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-02-12 10:45:44 +00:00
- os: osx
compiler: gcc
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
before_script:
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
- env
- if [ "$TRAVIS_EVENT_TYPE" == "pull_request" -a -n "$EXTENDED_TEST" ]; then
(git log -1 $TRAVIS_COMMIT_RANGE | grep '\[extended tests\]' > /dev/null) || exit 0;
fi
Travis: When testing installation, build in separate dir, otherwise in checkout The rationale is that installation from a tarball is a common task that everyone performs. For all other builds, we do specialised tests, and might as well build them directly in the checkout, which also gives us fuzz corpora. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-04 09:50:39 +00:00
- if [ -n "$DESTDIR" ]; then
sh .travis-create-release.sh $TRAVIS_OS_NAME;
tar -xvzf _srcdist.tar.gz;
mkdir _build;
cd _build;
srcdir=../_srcdist;
top=..;
else
srcdir=.;
top=.;
fi
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
- if [ "$CC" == i686-w64-mingw32-gcc ]; then
export CROSS_COMPILE=${CC%%gcc}; unset CC;
Travis: When testing installation, build in separate dir, otherwise in checkout The rationale is that installation from a tarball is a common task that everyone performs. For all other builds, we do specialised tests, and might as well build them directly in the checkout, which also gives us fuzz corpora. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-04 09:50:39 +00:00
$srcdir/Configure mingw $CONFIG_OPTS -Wno-pedantic-ms-format;
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
elif [ "$CC" == x86_64-w64-mingw32-gcc ]; then
export CROSS_COMPILE=${CC%%gcc}; unset CC;
Travis: When testing installation, build in separate dir, otherwise in checkout The rationale is that installation from a tarball is a common task that everyone performs. For all other builds, we do specialised tests, and might as well build them directly in the checkout, which also gives us fuzz corpora. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-04 09:50:39 +00:00
$srcdir/Configure mingw64 $CONFIG_OPTS -Wno-pedantic-ms-format;
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
else
Workaround for false -Warray-bounds in Travis ccache + clang produces a false strcmp warning, see https://llvm.org/bugs/show_bug.cgi?id=20144 Since this only happens with ccache and --strict-warnings, and only with certain versions of glibc / clang, disabling ccache is a reasonable short-term workaround. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-03-12 16:18:25 +00:00
if which ccache >/dev/null && [ "$CC" != clang-3.6 ]; then
Travis - don't use ccache with cross compiles Although theoretically possible, Configure doesn't treat CC variable set like this very well: CC="ccache i686-w64-mingw32-gcc" Also, this Travis script doesn't recognise the possibility either. Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-03-10 01:14:55 +00:00
CC="ccache $CC";
Travis - add missing semi-colon Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-03-10 07:36:57 +00:00
fi;
Add a "config" for verbosity and use it with Travis Modify VMS config.com to match Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-15 16:46:39 +00:00
$srcdir/config -v $CONFIG_OPTS;
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
fi
Travis: When testing installation, build in separate dir, otherwise in checkout The rationale is that installation from a tarball is a common task that everyone performs. For all other builds, we do specialised tests, and might as well build them directly in the checkout, which also gives us fuzz corpora. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-04 09:50:39 +00:00
- cd $top
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
script:
Make "make" less verbose in Travis, except for the build only case Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-15 16:45:22 +00:00
- if [ -z "$BUILDONLY" ]; then
make="make -s";
else
make="make";
fi
Run BoringSSL tests on Travis Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-11-09 16:25:35 +00:00
- top=${PWD}
Travis: When testing installation, build in separate dir, otherwise in checkout The rationale is that installation from a tarball is a common task that everyone performs. For all other builds, we do specialised tests, and might as well build them directly in the checkout, which also gives us fuzz corpora. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-04 09:50:39 +00:00
- if [ -n "$DESTDIR" ]; then
cd _build;
fi
Make "make" less verbose in Travis, except for the build only case Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-15 16:45:22 +00:00
- $make update
Run find-doc-nits in travis Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2202)
2017-01-10 03:41:26 +00:00
- if [ -n "$CHECKDOCS" ]; then
$make doc-nits;
fi
Make "make" less verbose in Travis, except for the build only case Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-15 16:45:22 +00:00
- $make
Trim Travis config part 2 - Remove Win builds (temporarily). They're slow, allowed to fail, and therefore not useful as they are. - Make the --unified part of the matrix build-only. (This can be swapped if --unified becomes the default) - Only build 'no-engine' once, don't run any tests, but don't allow it to fail. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-03-06 21:31:18 +00:00
- if [ -z "$BUILDONLY" ]; then
Restore some mingw builds "no-pic" builds have in fact been green (and reasonably fast), so restore them while we figure out why tests without "no-pic" hang. Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-03-07 11:59:40 +00:00
if [ -n "$CROSS_COMPILE" ]; then
.travis.yml: introduce concept of "extended tests" Since CI is engaged on per merge request basis, it can be wasteful to run each request through all the tests, especially those resource consuming. Idea is to mark most of tests as "extended" and provide a way to opt-in by marking last commit with [extended tests] tag. It's still not as optimal as one could wish, as decision to skip a test still requires machine time, and it's taken in configured environment, i.e. with updates and additional packages installed... Reviewed-by: Richard Levitte <levitte@openssl.org> (Merged from https://github.com/openssl/openssl/pull/2292)
2017-02-06 10:14:05 +00:00
sudo apt-get -yq --no-install-suggests --no-install-recommends --force-yes install wine;
Restore some mingw builds "no-pic" builds have in fact been green (and reasonably fast), so restore them while we figure out why tests without "no-pic" hang. Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-03-07 11:59:40 +00:00
export EXE_SHELL="wine" WINEPREFIX=`pwd`;
fi;
Run BoringSSL tests on Travis Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-11-09 16:25:35 +00:00
HARNESS_VERBOSE=yes BORING_RUNNER_DIR=$top/boringssl/ssl/test/runner make test;
Travis: build tests in BUILDONLY mode Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-03-14 11:47:47 +00:00
else
Make "make" less verbose in Travis, except for the build only case Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-15 16:45:22 +00:00
$make build_tests;
Run tests on Travis for mingw builds as well Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-16 15:19:04 +00:00
fi
Try 'make install' with one of the Travis configurations Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-29 15:50:53 +00:00
- if [ -n "$DESTDIR" ]; then
Run BoringSSL tests on Travis Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-11-09 16:25:35 +00:00
mkdir "$top/$DESTDIR";
$make install install_docs DESTDIR="$top/$DESTDIR";
Try 'make install' with one of the Travis configurations Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-29 15:50:53 +00:00
fi
Travis: When testing installation, build in separate dir, otherwise in checkout The rationale is that installation from a tarball is a common task that everyone performs. For all other builds, we do specialised tests, and might as well build them directly in the checkout, which also gives us fuzz corpora. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-08-04 09:50:39 +00:00
- cd $top
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
Add a coverage target Run tests with coverage and report to coveralls.io For simplicity, this currently only adds a single target in a configuration that attempts to maximize coverage. The true CI coverage from all the various builds may be a little larger. The coverage run has the following configuration: - no-asm: since we can't track asm coverage anyway, might as well measure the non-asm code coverage. - Enable various disabled-by-default options: - rc5 - md2 - ec_nistp_64_gcc_128 - ssl3 - ssl3-method - weak-ssl-ciphers Finally, observe that no-pic implies no-shared, and therefore running both builds in the matrix is redundant. Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
2016-08-03 13:29:21 +00:00
after_success:
- if [ -n "$COVERALLS" ]; then
coveralls: Use gcov-5 since we build it using gcc-5 Reviewed-by: Emilia Käsper <emilia@openssl.org> GH: #2003
2016-11-24 17:51:23 +00:00
coveralls -b . --gcov gcov-5 --gcov-options '\-lp';
Add a coverage target Run tests with coverage and report to coveralls.io For simplicity, this currently only adds a single target in a configuration that attempts to maximize coverage. The true CI coverage from all the various builds may be a little larger. The coverage run has the following configuration: - no-asm: since we can't track asm coverage anyway, might as well measure the non-asm code coverage. - Enable various disabled-by-default options: - rc5 - md2 - ec_nistp_64_gcc_128 - ssl3 - ssl3-method - weak-ssl-ciphers Finally, observe that no-pic implies no-shared, and therefore running both builds in the matrix is redundant. Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
2016-08-03 13:29:21 +00:00
fi;
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-19 22:12:29 +00:00
notifications:
GH398: Add mingw cross-compile, etc. For all release branches. It adds travis build support. If you don't have a config file it uses the default (because we enabled travis for the project), which uses ruby/rake/rakefiles, and you get confusing "build still failing" messages. Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-09-21 23:54:36 +00:00
email:
Secure our notification email. Forks will have to define their own Reviewed-by: Rich Salz <rsalz@openssl.org> (Merged from https://github.com/openssl/openssl/pull/1821)
2016-11-01 23:09:03 +00:00
secure: "xeGNgWO7aoaDgRvcZubposqMsj36aU8c6F0oHfw+rUqltCQ14IgYCUwzocmR2O+Pa7B3Cx5VjMfBFHbQaajZsfod8vu7g+aGq/zkjwbhsr/SR4dljJjFJXLGZjIalm9KgP6KInmVDuINfCqP+MHIY5lZkNI7DMcyHDhVc5nSKvCXV7xTDNgmstvh8rB/z51WfHDqGqfBtiuK5FDNxmvYK8OFJ5W94Lu9LDlizcxwK3GAj7arOui7Z5w8bQ6p4seUE3IvJL1Zbj0pZHxvNb6Zeb2Pn8QF1qLlN8YmBktD4aiw0ce4wYRiL87uLgcOxZY7SVXtv2XYFIYWapU/FKjCqa6vK93V/H9eZWEIYNMKnN3wXm2beqVdnKek3OeGJ8v0y7MbSfuLfRtBqbTSNYnpU1Zuo4MQAvHvEPuwCAYkYQajOSRplMH5sULFKptuVqNtOMfjL8jHb8AEoL1acYIk43ydxeYrzzas4fqgCDJ52573/u0RNdF1lkQBLkuM365OB8VRqtpnoxcdEIY/qBc/8TzZ24fxyrs5qdHFcxGSgpN2EP6cJMqpvkemnCNSdhxUqfzm22N7a3O8+4LFSBGOnHto/PwdsvF/01yGYL0LoZTnoO1i6x7AMJPBh+eyDU0ZjGhj/msjmqeb9C8vRqQ+1WjHrIS1iqCD0Czib8tUPD4="
Reference in a new issue Copy permalink