jenkins build slaves: Rationale for some builds in docker vs. some not?

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

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Aug 30 11:53:21 UTC 2017


On Wed, Aug 30, 2017 at 01:12:06AM +0200, Holger Freyther wrote:
> In the sysmocom system-images I played with the XML "template" and the java
> client to create/update jobs but Lynxis found that yaml DSL to describe jobs
> more easily and I think we could explore that. We could have one repository
> will all the jobs and run that to populate jenkins. E.g. this even enforces
> standards like discarding old builds (we don't run on turing tape after all).

That sounds excellent! Setting up jobs on the web ui can be quite cumbersome
and documenting it is even worse... 

Yet someone needs to setup the yaml DSL.
(Sounds like a job for dr.blobb, but haven't heard anything in a while)

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170830/055f0aa7/attachment.bin>


More information about the OpenBSC mailing list