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/.

André Boddenberg dr.blobb at gmail.com
Thu Sep 7 13:34:48 UTC 2017


Hi Neels,

>> The libosmocore job would update the libosmocore image, the libosmo-abis job
>> builds on it to produce the libosmo-abis image, and so forth. The jenkins jobs
>> would naturally re-use the other jobs' results and be clean every time.

Of course this will work, but afaics it won't suite for gerrit
verifications. Because docker always takes the latest available base
image. So if libosmocore image is currently rebuild and didn't finish
yet, a libosmo-abis docker build, which uses libosmocore as base image
wouldn't wait until the "new" libosmocore image is built, it would
simply use the "old" one. That's why I really like the "one container"
solution for gerrit verifications, which checks whether all
dependencies are up to date by a "docker build" invocation.

>> Would be great to not build separate tester images anymore.

My knowledge about the gsm-tester is quite limited to its manual and I
agree with the general idea of reusing things, but it might be better
to have Docker images for precise purposes?


My spike with Harald's gerrit-verification image [1] and
jenkins-job-builder [2] will probably finish next week (mo/tu).

BR,
 André

[1] https://git.osmocom.org/docker-playground/tree/osmo-gerrit-libosmo/Dockerfile
[2] https://pypi.python.org/pypi/jenkins-job-builder/



More information about the OpenBSC mailing list