Message ID | 20190411205159.7369-2-chipitsine@gmail.com |
---|---|
State | Changes Requested |
Headers | show |
Series | cirrus-ci support | expand |
On 11/04/2019 22:51, chipitsine@gmail.com wrote: > From: Ilya Shipitsin <chipitsine@gmail.com> > > enabled FreeBSD 12.0 builds > > Signed-off-by: Ilya Shipitsin <chipitsine@gmail.com> Hey, Just wondering about the value of adding yet another CI into the mix we have? We have Travis and buildbot. Travis doesn't handle all the *BSD flavours but gives us Windows. Our buildbot setup does Linux (CentOS, Fedora, Ubuntu, Arch), macOS, FreeBSD (7.4, 9.0, 10.3, 11), NetBSD (5.1, 7.0), OpenBSD (4.9, 6.0), OpenSolaris 10 ... I might have overlooked a few. The sum of this seems far more than what cirrus-ci provides. So I really wonder about the value here. You can always argue that it's just a text file laying there if not being used, but we also want to avoid "dead files" in our repository.
diff --git a/.cirrus.yml b/.cirrus.yml new file mode 100644 index 00000000..955b8de0 --- /dev/null +++ b/.cirrus.yml @@ -0,0 +1,24 @@ +FreeBSD_task: + freebsd_instance: + image: freebsd-12-0-release-amd64 + env: + ASSUME_ALWAYS_YES: TRUE # required for unattended "pkg" invocation + LZO_CFLAGS: '-I/usr/local/include' + LZO_LIBS: '-llzo2 -L/usr/local/lib' + LZ4_CFLAGS: '-I/usr/local/include' + LZ4_LIBS: '-llz4 -L/usr/local/lib' + MBEDTLS_CFLAGS: '-I/usr/local/include' + MBEDTLS_LIBS: '-lmbedtls -lmbedx509 -lmbedcrypto -L/usr/local/lib' + matrix: + - SSLLIB: openssl + - SSLLIB: mbedtls + install_script: + - pkg install cmake gmake openssl111 mbedtls git autoconf automake libtool + - git submodule update --init --recursive + script: + - autoreconf -iv + - ./configure --with-crypto-library=${SSLLIB} + - make + - src/openvpn/openvpn --version || true + - ldd src/openvpn/openvpn + - make check