cellular-infrastructure
/
osmo-msc
mirror of https://gerrit.osmocom.org/osmo-msc
9
0
Fork 0
Code Issues Releases Wiki Activity
osmo-msc/contrib/jenkins.sh

61 lines
1.4 KiB
Bash
Raw Normal View History

jenkins: Add the build script from jenkins here This can be used to replicate a build issue more easily.
2016-04-13 23:03:38 +00:00
#!/usr/bin/env bash
jenkins.sh: Proper error message if local environment isn't set up Change-Id: I79c2302365824d9c8783dadfa378c8eaa07e2ee7
2017-07-10 13:00:00 +00:00
# jenkins build helper script for openbsc. This is how we build on jenkins.osmocom.org
if ! [ -x "$(command -v osmo-build-dep.sh)" ]; then
echo "Error: We need to have scripts/osmo-deps.sh from http://git.osmocom.org/osmo-ci/ in PATH !"
exit 2
fi
jenkins: Add the build script from jenkins here This can be used to replicate a build issue more easily.
2016-04-13 23:03:38 +00:00
set -ex
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
base="$PWD"
deps="$base/deps"
inst="$deps/install"
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
export deps inst
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
jenkins: use osmo-clean-workspace.sh before and after build See osmo-ci change I2409b2928b4d7ebbd6c005097d4ad7337307dd93 for rationale. Depends: I2409b2928b4d7ebbd6c005097d4ad7337307dd93 Change-Id: I6ae80147b2624079b5c364dbce08194215cc4e95
2017-10-27 20:54:40 +00:00
osmo-clean-workspace.sh
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
mkdir "$deps" || true
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
osmo-build-dep.sh libosmocore "" ac_cv_path_DOXYGEN=false
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
Use value string check from osmo-ci Necessary since libosmocore I513835be2d931d0a931cdfc996f361a451bc1a15 removes the script from libosmocore/contrib. Change-Id: I02d7e1c0151c687fd9341d21a09ca15cbf5a1938
2017-08-26 19:19:35 +00:00
verify_value_string_arrays_are_terminated.py $(find . -name "*.[hc]")
jenkins: add value_string termination check Depends: libosmocore change-id I2bc93ab4781487e7685cfb63091a489cd126b1a8 Change-Id: I4183415cd1ead9d46ae3a556e94243325ef5a844
2017-03-01 14:06:16 +00:00
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
export PKG_CONFIG_PATH="$inst/lib/pkgconfig:$PKG_CONFIG_PATH"
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
export LD_LIBRARY_PATH="$inst/lib"
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
osmo-build-dep.sh libosmo-abis
jenkins.sh: Iu: use libosmo-sccp,-netif master The iu specific branches of libosmo-sccp and libosmo-netif have recently been merged to master. Change-Id: I9465d7b956c3bd65d6e8a387e6710235672352e8
2017-03-31 12:03:39 +00:00
osmo-build-dep.sh libosmo-netif
Implement AoIP, port to M3UA SIGTRAN (large addition and refactoring) This was originally a long series of commits converging to the final result seen in this patch. It does not make much sense to review the smaller steps' trial and error, we need to review this entire change as a whole. Implement AoIP in osmo-msc and osmo-bsc. Change over to the new libosmo-sigtran API with support for proper SCCP/M3UA/SCTP stacking, as mandated by 3GPP specifications for the IuCS and IuPS interfaces. From here on, a separate osmo-stp process is required for SCCP routing between OsmoBSC / OsmoHNBGW <-> OsmoMSC / OsmoSGSN jenkins.sh: build from libosmo-sccp and osmo-iuh master branches now for new M3UA SIGTRAN. Patch-by: pmaier, nhofmeyr, laforge Change-Id: I5ae4e05ee7c57cad341ea5e86af37c1f6b0ffa77
2017-04-09 10:32:51 +00:00
osmo-build-dep.sh libosmo-sccp
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
PARALLEL_MAKE="" osmo-build-dep.sh libsmpp34
Use osmo-ggsn instead of openggsn in jenkins tests Change-Id: Ib70360feb82fb9f871461f94982634c11d58f772
2017-11-23 15:48:24 +00:00
osmo-build-dep.sh osmo-ggsn
jenkins: fix build: osmo-mgw from master, not pre_release pre_release is gone, we need to build from master now. Change-Id: I86a50c523ab04d96575aade624daa5a2f9fd6d83
2017-09-03 20:47:51 +00:00
osmo-build-dep.sh osmo-mgw
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
jenkins.sh: add --enable-iu matrix build Change-Id: Ida76f24d0b801fa609f3a128b3b912572cad4297
2016-07-11 17:44:58 +00:00
if [ "x$IU" = "x--enable-iu" ]; then
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
osmo-build-dep.sh libasn1c
#osmo-build-dep.sh asn1c aper-prefix # only needed for make regen in osmo-iuh
Implement AoIP, port to M3UA SIGTRAN (large addition and refactoring) This was originally a long series of commits converging to the final result seen in this patch. It does not make much sense to review the smaller steps' trial and error, we need to review this entire change as a whole. Implement AoIP in osmo-msc and osmo-bsc. Change over to the new libosmo-sigtran API with support for proper SCCP/M3UA/SCTP stacking, as mandated by 3GPP specifications for the IuCS and IuPS interfaces. From here on, a separate osmo-stp process is required for SCCP routing between OsmoBSC / OsmoHNBGW <-> OsmoMSC / OsmoSGSN jenkins.sh: build from libosmo-sccp and osmo-iuh master branches now for new M3UA SIGTRAN. Patch-by: pmaier, nhofmeyr, laforge Change-Id: I5ae4e05ee7c57cad341ea5e86af37c1f6b0ffa77
2017-04-09 10:32:51 +00:00
osmo-build-dep.sh osmo-iuh
jenkins.sh: add --enable-iu matrix build Change-Id: Ida76f24d0b801fa609f3a128b3b912572cad4297
2016-07-11 17:44:58 +00:00
fi
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
set +x
echo
echo
echo
jenkins: apply rename to osmo-msc in log marker Change-Id: I8ca9a1a8bdb5b9615df5f19f0c1017cb9383f6ee
2017-07-12 21:37:05 +00:00
echo " =============================== osmo-msc ==============================="
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
echo
set -x
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
cd "$base"
jenkins: Add the build script from jenkins here This can be used to replicate a build issue more easily.
2016-04-13 23:03:38 +00:00
autoreconf --install --force
Remove obsolete ./configure option The '--enable-vty-tests' is just alias to '--enable-external-tests' anyway. Change-Id: I8ab3ac3d9becee6b4e989b4e71d34598ea012f47
2017-11-23 15:14:40 +00:00
./configure --enable-smpp $IU --enable-external-tests
jenkins.sh: remove code dup Have a bash function to build each dependency with the same commands. There is a tradeoff: having each dependency build with the same function means you can't easily tweak one of the dependencies. OTOH having a unified function means a) more readable script, b) that we're sure not to forget some steps and c) no need to do the same edit n times. Set the PKG_CONFIG_PATH globally. Also a tradeoff: if a future addition wouldn't need the same PKG_CONFIG_PATH, this would make things ugly. But that is actually quite unlikely, and the readability improvement is substantial. Use env variables to remember local paths. That means we always are sure to cd to the same absolute base path, which a 'cd ..' can't guarantee; also, we avoid possible typos for e.g. "$deps/install". Change-Id: Ib23f86c6cc1441d882de59bcdde5de87fa4e9fdf
2016-07-11 17:39:51 +00:00
$MAKE $PARALLEL_MAKE
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
LD_LIBRARY_PATH="$inst/lib" $MAKE check \
|| cat-testlogs.sh
jenkins: pass proper configure flags to make distcheck Enable various components according to the build matrix during make distcheck. Add python tests, osmo-bsc, nat, ... Change-Id: Ic724cf61d44409337414dc58c8795896b4b97a8a
2017-07-20 15:57:37 +00:00
LD_LIBRARY_PATH="$inst/lib" \
Remove obsolete ./configure option The '--enable-vty-tests' is just alias to '--enable-external-tests' anyway. Change-Id: I8ab3ac3d9becee6b4e989b4e71d34598ea012f47
2017-11-23 15:14:40 +00:00
DISTCHECK_CONFIGURE_FLAGS="--enable-smpp $IU --enable-external-tests" \
jenkins: pass proper configure flags to make distcheck Enable various components according to the build matrix during make distcheck. Add python tests, osmo-bsc, nat, ... Change-Id: Ic724cf61d44409337414dc58c8795896b4b97a8a
2017-07-20 15:57:37 +00:00
$MAKE distcheck \
jenkins.sh: use osmo-build-dep.sh, log test failures Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-10-06 22:58:22 +00:00
|| cat-testlogs.sh
jenkins: use osmo-clean-workspace.sh before and after build See osmo-ci change I2409b2928b4d7ebbd6c005097d4ad7337307dd93 for rationale. Depends: I2409b2928b4d7ebbd6c005097d4ad7337307dd93 Change-Id: I6ae80147b2624079b5c364dbce08194215cc4e95
2017-10-27 20:54:40 +00:00
osmo-clean-workspace.sh