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

André Boddenberg dr.blobb at gmail.com
Wed Sep 6 12:40:26 UTC 2017


+1 for moving towards describing jobs instead of clicking them!

I haven't used yaml DSL, only JobDSL and Pipeline so far. I will try
to migrate some jobs (nightly, gerrit) to yaml DSL to see if all
needed configurations are available and let you know. Or did someone
already check this?

2017-08-30 13:53 GMT+02:00 Neels Hofmeyr <nhofmeyr at sysmocom.de>:
> 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



-- 
Gruß
Blobb



More information about the OpenBSC mailing list