libzmq/ci_build.sh

#!/usr/bin/env bash

set -x
set -e

if [ $BUILD_TYPE = "default" ]; then
    mkdir tmp
    BUILD_PREFIX=$PWD/tmp

    source config.sh
    set_config_opts

    # Build and check this project
    (
        ./autogen.sh &&
        ./configure "${CONFIG_OPTS[@]}" &&
        export DISTCHECK_CONFIGURE_FLAGS="${CONFIG_OPTS[@]}" &&
        make VERBOSE=1 -j5 ${CHECK}
    ) || exit 1
else
    cd ./builds/${BUILD_TYPE} && ./ci_build.sh
fi
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: syntax errors in ci_build.sh Solution: fix them 2020-05-05 13:16:19 +02: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`

Problem: coverage build script doesn't recognize several config options Solution: extrace and reuse regular config option setting 2020-09-04 10:23:37 +02:00			`source config.sh`
			`set_config_opts`
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
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: we want to have multiple seed corpora per fuzzer binary Solution: store them each as a single line in the text file and convert them at install time 2020-05-04 23:30:37 +02:00			`make VERBOSE=1 -j5 ${CHECK}`
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`