osmo-gsm-tester/contrib/jenkins-build-osmo-pcu.sh

#!/bin/sh
set -e -x
base="$PWD"
name="osmo-pcu"
. "$(dirname "$0")/jenkins-build-common.sh"

build_repo libosmocore ${SANITIZE_FLAGS} --disable-pcsc --disable-doxygen --disable-uring
build_repo osmo-pcu ${SANITIZE_FLAGS}

create_bin_tgz osmo-pcu
contrib: Add scripts to build osmo-pcu Change-Id: I90e7d2a79fb4ab7cc7fae5f3a1287a2e5bb748ab 2017-08-31 14:58:33 +00:00			`#!/bin/sh`
			`set -e -x`
			`base="$PWD"`
			`name="osmo-pcu"`
			`. "$(dirname "$0")/jenkins-build-common.sh"`

contrib/jenkins-build: libosmocore: disable-uring This should fix the many builds currently failing from the osmo-gsm-tester_build jobs. Related: OS#5751 Change-Id: Ibc9605933380351a5fd23b772868c0e698b39c37 2023-08-25 08:39:15 +00:00			`build_repo libosmocore ${SANITIZE_FLAGS} --disable-pcsc --disable-doxygen --disable-uring`
Be able to switch-off ASAN builds of our binaries. Inroduce a way to not take a 2x performance hit when testing. It is of importance if we run with hundreds of BTSes and 10k+ subscribers. In the absence of using getops or shflags use an environment for it. Change-Id: I540ba1c35e8fb72abcee0d86e0bdc1136b47345c 2018-09-23 14:14:00 +00:00			`build_repo osmo-pcu ${SANITIZE_FLAGS}`
contrib: Add scripts to build osmo-pcu Change-Id: I90e7d2a79fb4ab7cc7fae5f3a1287a2e5bb748ab 2017-08-31 14:58:33 +00:00
jenkins: per build, drop programs built "unintentionally" Each of the jenkins-build-* scripts intends to build a specific set of programs. While compiling dependencies, other programs may end up in $prefix/bin. Drop those other binaries to reduce potential confusion. Add arguments to the create_bin_tgz function: callers need to list exactly the $prefix/bin/* binaries that should be tar'd. All others are first removed from the prefix. Adjust existing scripts to provide such binary names. Change-Id: Ib1a00b2149453fedf9ece0460dd4d6e83f774d45 2017-09-04 14:34:18 +00:00			`create_bin_tgz osmo-pcu`