jenkins slave setup and artifact re-use

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Wed Sep 6 15:22:04 UTC 2017


Hi Andre,

On Wed, Sep 06, 2017 at 03:05:27PM +0200, Harald Welte wrote:
> In the basic form I would see only one dockerfile+image for libosmo* in
> master branch that can be used for all osmo-* application build testing.

I've prototyped this at http://git.osmocom.org/docker-playground/tree/osmo-gerrit-libosmo/Dockerfile

If you're trying this, make sure you're running it using 'make run' or
manually including the "--tmpfs /tmpfs:exec" arguments.

The VTY tests of course take ages, but the actual build of openbsc.git
is pretty fast and executed on /tmpfs.

if the jenkins job for openbsc-gerrit would then do
* docker build ...
* docker run ...

Then the latest openbsc.git would be built and automatically all upstream
dependencies are updated from latest master - but only if the latest
master of those dependencies has changed (unlike current osmo-deps.sh).

This is of course all just a prototype, and proper scripts/integration
is needed.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list