summaryrefslogtreecommitdiffstats
path: root/contrib
AgeCommit message (Collapse)AuthorFilesLines
2016-10-12jenkins.sh: use osmo-build-dep.sh, log test failuresNeels Hofmeyr1-40/+23
Like in libosmo-abis' jenkins.sh Change-Id: I4d6ffd5b230dd095650cc2231678b66056a8e4b5
2016-08-15ci: Attempt to disable doxygen warnings of dependenciesHolger Hans Peter Freyther1-2/+3
We do not want to see doxygen warnings when building the libosmocore dependency. Change-Id: I4640cb5b91d54641e8e5b2f096c3bca49bfff60e
2016-07-13jenkins.sh: add --enable-iu matrix buildNeels Hofmeyr1-3/+14
Change-Id: Ida76f24d0b801fa609f3a128b3b912572cad4297
2016-07-13jenkins.sh: remove code dupNeels Hofmeyr1-52/+51
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-04-13jenkins: Add the build script from jenkins hereHolger Hans Peter Freyther1-0/+57
This can be used to replicate a build issue more easily.