mirrors/openssl
0
0
Fork 0
mirror of https://github.com/openssl/openssl.git synced 2024-12-19 06:53:49 +08:00
Code Issues Packages Projects Releases Wiki Activity
5cdad22f3e
openssl/.travis.yml

124 lines
3.3 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-20 06:12:29 +08: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-07 07:33:35 +08: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-20 06:12:29 +08: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 21:29:21 +08:00
before_install:
- pip install --user cpp-coveralls
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-22 07:54:36 +08:00
addons:
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-13 04:15:43 +08: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-07 07:33:35 +08:00
- ccache
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 20:51:16 +08:00
- clang-3.6
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-13 04:15:43 +08:00
- gcc-5
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 19:59:40 +08:00
- binutils-mingw-w64
- gcc-mingw-w64
- wine
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-13 04:15:43 +08:00
sources:
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 20:51:16 +08:00
- llvm-toolchain-precise-3.6
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-13 04:15:43 +08:00
- ubuntu-toolchain-r-test
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-22 07:54:36 +08: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-20 06:12:29 +08: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-22 07:54:36 +08:00
- linux
- osx
Add initial Travis CI configuration Closes #63 Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Ben Laurie <ben@openssl.org>
2015-08-20 06:12:29 +08: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-22 07:54:36 +08: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-20 06:12:29 +08:00
env:
Try 'make install' with one of the Travis configurations Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-29 23:50:53 +08:00
- CONFIG_OPTS="" DESTDIR="_install"
Update Travis and Appveyor for change to shared by default Update the Travis and Appveyor builds to explicitly state no-shared where applicable. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-04-14 21:28:13 +08:00
- CONFIG_OPTS="--debug no-shared enable-crypto-mdebug enable-rc5 enable-md2"
Adjust --strict-warnings builds in Travis In Travis, do --strict-warnings on BUILDONLY configurations. This ensures that the tests run even if --strict-warnings fail, and avoids hiding unrelated test failures. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-04-05 21:11:02 +08:00
- CONFIG_OPTS="no-pic --strict-warnings" BUILDONLY="yes"
Update Travis and Appveyor for change to shared by default Update the Travis and Appveyor builds to explicitly state no-shared where applicable. Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-04-14 21:28:13 +08:00
- CONFIG_OPTS="no-engine no-shared --strict-warnings" BUILDONLY="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-22 07:54:36 +08:00
matrix:
GH429: Add clang to travis Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Andy Polyakov <appro@openssl.org>
2015-10-13 04:15:43 +08:00
include:
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 21:29:21 +08:00
- os: linux
compiler: gcc
env: CONFIG_OPTS="--debug --coverage no-asm enable-rc5 enable-md2 enable-ec_nistp_64_gcc_128 enable-ssl3 enable-ssl3-method enable-weak-ssl-ciphers" COVERALLS="yes"
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-07 02:27:50 +08:00
- os: linux
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 20:51:16 +08:00
compiler: clang-3.6
Travis: update sanitizer configs - Use the new enable-ubsan and enable-asan configuration options. - Separate ubsan and asan runs. - In addition, run shared ubsan tests to get more coverage. (Shared asan tests need a bit more thought to get them working.) Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-05-13 02:00:14 +08:00
env: CONFIG_OPTS="no-shared enable-asan"
Add memory sanitizer config, and run on travis. Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-07-29 02:24:28 +08:00
- os: linux
compiler: clang-3.6
env: CONFIG_OPTS="no-shared 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-07 02:27:50 +08:00
- os: linux
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 20:51:16 +08:00
compiler: clang-3.6
Ensure Travis tests SSLv3 Switch on Travis testing of SSLv3. Reviewed-by: Emilia Käsper <emilia@openssl.org>
2016-07-15 17:46:01 +08:00
env: CONFIG_OPTS="no-asm enable-ubsan enable-rc5 enable-md2 enable-ssl3 enable-ssl3-method -fno-sanitize=alignment"
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 20:51:16 +08:00
- os: linux
compiler: clang-3.6
env: CONFIG_OPTS="no-shared no-asm enable-asan enable-rc5 enable-md2"
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-07 02:27:50 +08:00
- os: linux
compiler: gcc-5
Restore clang builds in travis.yml Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-06-30 20:51:16 +08:00
env: CONFIG_OPTS="no-asm enable-ubsan enable-rc5 enable-md2 -DPEDANTIC"
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 19:59:40 +08:00
- os: linux
compiler: i686-w64-mingw32-gcc
env: CONFIG_OPTS="no-pic"
- os: linux
compiler: x86_64-w64-mingw32-gcc
env: CONFIG_OPTS="no-pic"
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-22 07:54:36 +08: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 22:15:20 +08: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 18:45:44 +08: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-22 07:54:36 +08:00
before_script:
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 17:50:39 +08: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-22 07:54:36 +08: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 17:50:39 +08: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-22 07:54:36 +08: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 17:50:39 +08: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-22 07:54:36 +08: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-13 00:18:25 +08: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 09:14:55 +08:00
CC="ccache $CC";
Travis - add missing semi-colon Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-03-10 15:36:57 +08: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 17:50:39 +08:00
$srcdir/config $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-22 07:54:36 +08: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 17:50:39 +08: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-20 06:12:29 +08:00
script:
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 17:50:39 +08:00
- if [ -n "$DESTDIR" ]; then
cd _build;
top=..;
else
top=.;
fi
Have the Travis builds do a "make update" Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-07-19 17:58:26 +08:00
- make update
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-22 07:54:36 +08: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-07 05:31:18 +08: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 19:59:40 +08:00
if [ -n "$CROSS_COMPILE" ]; then
export EXE_SHELL="wine" WINEPREFIX=`pwd`;
fi;
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-07 05:31:18 +08:00
HARNESS_VERBOSE=yes make test;
Travis: build tests in BUILDONLY mode Reviewed-by: Richard Levitte <levitte@openssl.org>
2016-03-14 19:47:47 +08:00
else
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 23:19:04 +08:00
fi
Try 'make install' with one of the Travis configurations Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-29 23:50:53 +08:00
- if [ -n "$DESTDIR" ]; then
mkdir "../$DESTDIR";
Travis: When testing install, install docs as well Reviewed-by: Matt Caswell <matt@openssl.org>
2016-06-02 23:37:03 +08:00
make install install_docs DESTDIR="../$DESTDIR";
Try 'make install' with one of the Travis configurations Reviewed-by: Matt Caswell <matt@openssl.org>
2016-03-29 23:50:53 +08: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 17:50:39 +08: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-20 06:12:29 +08: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 21:29:21 +08:00
after_success:
- if [ -n "$COVERALLS" ]; then
Add --gcov-options '\-lp' to coverage Should result in more accurate header file coverage, see https://github.com/eddyxu/cpp-coveralls/issues/54 Reviewed-by: Kurt Roeckx <kurt@openssl.org>
2016-08-05 17:33:48 +08:00
coveralls -b . --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 21:29:21 +08: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-20 06:12:29 +08: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-22 07:54:36 +08:00
email:
Fix travis builds on master -Allow mingw debug builds to fail on Travis CI -Fix Travis email notifications config -Rename a variable to avoid a bogus warning with old GCC error: declaration of ``dup'' shadows a global declaration [-Werror=shadow] -Disable pedantic ms-format warnings with mingw -Properly define const DH parameters -Restore --debug flag in Travis CI builds; -d would get incorrectly passed to ./Configure in mingw debug builds. Signed-off-by: Rich Salz <rsalz@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org>
2015-10-07 00:23:42 +08:00
- openssl-commits@openssl.org
Add some 'no-engine' builds to travis, for test Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Rich Salz <rsalz@openssl.org>
2016-02-26 03:54:40 +08:00
Reference in New Issue Copy Permalink