generic-library/libzmq
1
0
Fork 0
mirror of https://github.com/zeromq/libzmq.git synced 2024-12-12 10:33:52 +01:00
Code Issues Projects Releases Wiki Activity
8fe620901f
libzmq/ci_build.sh

83 lines
2.5 KiB
Bash
Raw Normal View History

Problem: No builtin way to build for qt-android Solution: Add qt-android build system and add to travis-ci
2014-11-03 02:33:23 +01:00
#!/usr/bin/env bash
Set -x in ci_build.sh to show commands in log
2015-08-16 19:56:24 +02:00
set -x
Problem: Deploying release artifacts is a manual process Solution: Use travis to deploy these artifacts automatically. The deployment is triggered by tagging on the zeromq/libzmq repository. Of the many builds travis is checking only the default one with libsodium and drafts disabled is used for deployment. For now the results of `make distcheck` are deployed as well as their md5 and sha1 hash sums. Further changes may upload a generated Changelog as well.
2016-05-04 22:05:40 +02:00
set -e
Set -x in ci_build.sh to show commands in log
2015-08-16 19:56:24 +02:00
Problem: No builtin way to build for qt-android Solution: Add qt-android build system and add to travis-ci
2014-11-03 02:33:23 +01:00
if [ $BUILD_TYPE == "default" ]; then
CI build/install in local directory
2015-08-16 19:46:03 +02:00
mkdir tmp
BUILD_PREFIX=$PWD/tmp
CONFIG_OPTS=()
Problem: CI doesn't build with debugging symbols Solution: pass -g so that valgrind/asan can print useful backtraces
2017-05-01 17:11:16 +02:00
CONFIG_OPTS+=("CFLAGS=-g")
CI build/install in local directory
2015-08-16 19:46:03 +02:00
CONFIG_OPTS+=("CPPFLAGS=-I${BUILD_PREFIX}/include")
Problem: CI doesn't build with debugging symbols Solution: pass -g so that valgrind/asan can print useful backtraces
2017-05-01 17:11:16 +02:00
CONFIG_OPTS+=("CXXFLAGS=-g")
CI build/install in local directory
2015-08-16 19:46:03 +02:00
CONFIG_OPTS+=("LDFLAGS=-L${BUILD_PREFIX}/lib")
CONFIG_OPTS+=("PKG_CONFIG_PATH=${BUILD_PREFIX}/lib/pkgconfig")
CONFIG_OPTS+=("--prefix=${BUILD_PREFIX}")
Problem: lack of out-of-bound memory checks in tests Solution: add a CI build run with GCC's Address Sanitizer enabled. This compiler flag will make the unit test programs abort if it detects errors such as out-of-bound memory access or use-after-free.
2017-03-30 16:22:50 +02:00
if [ -n "$ADDRESS_SANITIZER" ] && [ "$ADDRESS_SANITIZER" == "enabled" ]; then
Problem: address sanitizer support in CI is hacky Solution: import better solution from zproject and add a new autoconf option
2017-05-01 19:06:45 +02:00
CONFIG_OPTS+=("--enable-address-sanitizer=yes")
Problem: ASAN test doesn't print good traces with GCC 4.8 Solution: add Ubuntu toolchain PPA and use GCC 6
2017-05-01 19:44:26 +02:00
CONFIG_OPTS+=("CXX=g++-6")
CONFIG_OPTS+=("CC=gcc-6")
# workaround for linker problem with ASAN options in GCC
# http://stackoverflow.com/questions/37603238/fsanitize-not-using-gold-linker-in-gcc-6-1
CONFIG_OPTS+=("LDFLAGS=-fuse-ld=gold")
Problem: lack of out-of-bound memory checks in tests Solution: add a CI build run with GCC's Address Sanitizer enabled. This compiler flag will make the unit test programs abort if it detects errors such as out-of-bound memory access or use-after-free.
2017-03-30 16:22:50 +02:00
fi
problem: ci doesn't build with nss Solution: add an nss build to CI
2019-09-11 12:21:36 +02:00
if [ $USE_NSS == "yes" ]; then
CONFIG_OPTS+=("--with-nss")
fi
Problem: CI use of sodium or nacl is confusing Solution: establish a matrix of CI options. On one axis we have the build system (autotools, cmake, android) and on the other axis we have the encryption options (tweetnacl, libsodium or none).
2016-02-11 23:06:33 +01:00
if [ -z $CURVE ]; then
CONFIG_OPTS+=("--disable-curve")
elif [ $CURVE == "libsodium" ]; then
CONFIG_OPTS+=("--with-libsodium=yes")
Problem: dpkg-query might fail in CI build and fail the build Solution: rework the bash test to avoid build failures as intended and make it an easier one-liner
2016-12-27 14:45:45 +01:00
if ! ((command -v dpkg-query >/dev/null 2>&1 && dpkg-query --list libsodium-dev >/dev/null 2>&1) || \
(command -v brew >/dev/null 2>&1 && brew ls --versions libsodium >/dev/null 2>&1)); then
Problem: Travis rebuilds libsodium every time Solution: use packages on Ubuntu and brews on OSX. The packages and the brews are always kept up to date, so it's no use to rebuild the libsodium stable branch manually everytime.
2016-12-26 21:50:38 +01:00
git clone --depth 1 -b stable git://github.com/jedisct1/libsodium.git
Problem: CI runs libsodium tests Solution: don't, libzmq's CI tests are not responsible for testing libsodium stable releases. Save some time in the CI.
2017-05-01 13:29:24 +02:00
( cd libsodium; ./autogen.sh; ./configure --prefix=$BUILD_PREFIX; make install)
Problem: Travis rebuilds libsodium every time Solution: use packages on Ubuntu and brews on OSX. The packages and the brews are always kept up to date, so it's no use to rebuild the libsodium stable branch manually everytime.
2016-12-26 21:50:38 +01:00
fi
Problem: CI use of sodium or nacl is confusing Solution: establish a matrix of CI options. On one axis we have the build system (autotools, cmake, android) and on the other axis we have the encryption options (tweetnacl, libsodium or none).
2016-02-11 23:06:33 +01:00
fi
Problem: Travis does not test GSSAPI Solution: enable option and install build-dependency for the jobs that already install packages only, to minimise marginal cost in term of runtime
2017-08-19 18:51:54 +02:00
if [ -n "$GSSAPI" ] && [ "$GSSAPI" == "enabled" ]; then
CONFIG_OPTS+=("--with-libgssapi_krb5=yes")
fi
Problem: Travis does not test PGM Solution: enable option and install build-dependency for the jobs that already install packages only, to minimise marginal cost in term of runtime
2017-08-19 18:54:42 +02:00
if [ -n "$PGM" ] && [ "$PGM" == "enabled" ]; then
CONFIG_OPTS+=("--with-pgm=yes")
fi
Problem: Travis does not build with NORM Solution: install package and enable the build on some Linux jobs
2017-10-17 12:17:13 +02:00
if [ -n "$NORM" ] && [ "$NORM" == "enabled" ]; then
CONFIG_OPTS+=("--with-norm=yes")
fi
Problem: TIPC availability check is too strict (#2977) * Problem: TIPC availability check is too strict Solution: at build time only check if the API is available. In the tests do a first check and a skip if the functionality is not available. TIPC needs an in-tree but not loaded by default kernel module, tipc.ko to be loaded, which requires root, so it is unlikely to be available on any build system by default. This will allow most distributions to ship with TIPC support built in, and to avoid tests failure if the module is not there. * Problem: no Travis tests for TIPC Solution: mark one job with sudo: required and load the kernel module * Problem: CMake fails when test returns 77 (skip) Solution: set property to let it mark the test as skipped as intended
2018-03-09 17:47:42 +01:00
if [ -n "$TIPC" ] && [ "$TIPC" == "enabled" ]; then
sudo modprobe tipc
fi
Problem: regression with "select" on *nix (#2940) * Problem: build failure with select as polling mechanism Solution: cast mailbox_handle argument to (poller_t::handle_t) like in the reaper thread class. * Problem: build failure due to INT_MAX use without include Solution: include limits and climits in src/select.cpp where INT_MAX is used * Problem: build failure due to unused variable in select.cpp Solution: move the declaration of int rc inside the ifdef block where it is actually used * Problem: reference to wrong variable in select.cpp breaks build Solution: fix it * Problem: family_entry_t constructor has no body, build fails on *nix Solution: add empty inline function in the struct * Problem: no test coverage for poll and select Solution: add Travis jobs for them on Linux * Problem: Travis jobs cannot run in container infra Solution: set sudo: false as it is not required anymore
2018-02-12 09:01:03 +01:00
if [ -n "$POLLER" ]; then
CONFIG_OPTS+=("--with-poller=${POLLER}")
fi
Problem: no CI tests with DRAFT enabled Solution: do default test with DRAFT APIs enabled
2016-05-02 22:57:42 +02:00
if [ -z $DRAFT ] || [ $DRAFT == "disabled" ]; then
CONFIG_OPTS+=("--enable-drafts=no")
elif [ $DRAFT == "enabled" ]; then
CONFIG_OPTS+=("--enable-drafts=yes")
fi
Problem: no automated way to enforce C++98 compatibility Solution: if the compiler supports it, pass C++98-compat flags. Currently Clang supports this flag but GCC does not. Add a new flag to enable it, as building with C++98-compat but also with -std=gnu++11 will cause a lot of warnings due to the backward compat ifdefs. Add a CI job to run it and ensure we don't break compatibility.
2018-11-09 19:54:46 +01:00
if [ -n "$FORCE_98" ] && [ "$FORCE_98" == "enabled" ]; then
CONFIG_OPTS+=("--enable-force-CXX98-compat=yes")
fi
Problem: Deploying release artifacts is a manual process Solution: Use travis to deploy these artifacts automatically. The deployment is triggered by tagging on the zeromq/libzmq repository. Of the many builds travis is checking only the default one with libsodium and drafts disabled is used for deployment. For now the results of `make distcheck` are deployed as well as their md5 and sha1 hash sums. Further changes may upload a generated Changelog as well.
2016-05-04 22:05:40 +02:00
# Build and check this project
Problem: test-suite.log is not accessible on failing CI build Currently, a test fails on Travis-CI but that can not be reproduced locally. Without the contents of the test-suite.log, this is difficult to analyze. Solution: print test-suite.log if "make check" fails This is based on the following answer on SO: http://stackoverflow.com/a/32597140
2015-11-25 09:17:53 +01:00
(
./autogen.sh &&
Problem: CI still thinks libsodium is default Solution: build by default with tweetnacl, and add sub-build project to test libsodium
2016-02-11 21:12:10 +01:00
./configure "${CONFIG_OPTS[@]}" &&
Problem: ci_build does not fully test build system Solution: run make dist-check, which will run additional tests, including making sure that the library is installable and the distributable tarball is buildable, along with the usual make and make check.
2016-03-06 19:05:28 +01:00
export DISTCHECK_CONFIGURE_FLAGS="${CONFIG_OPTS[@]}" &&
Problem: CI builds and test runs not done in parallel Solution: run make with -j5, as now the tests support it.
2017-05-01 13:30:23 +02:00
make VERBOSE=1 -j5 distcheck
Problem: test-suite.log is not accessible on failing CI build Currently, a test fails on Travis-CI but that can not be reproduced locally. Without the contents of the test-suite.log, this is difficult to analyze. Solution: print test-suite.log if "make check" fails This is based on the following answer on SO: http://stackoverflow.com/a/32597140
2015-11-25 09:17:53 +01:00
) || exit 1
Problem: No builtin way to build for qt-android Solution: Add qt-android build system and add to travis-ci
2014-11-03 02:33:23 +01:00
else
cd ./builds/${BUILD_TYPE} && ./ci_build.sh
fi
Reference in New Issue Copy Permalink