RFC: jenkins pipeline

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

Max msuraev at sysmocom.de
Thu Mar 9 12:07:09 UTC 2017


Hi!


On 06.03.2017 16:15, André Boddenberg wrote:
>
> Agreed, the biggest advantages of Pipeline are:
>
> -  the "eye-candy" (but who cares? :)
>
> - easy artifacts sharing across different steps, which run on
> different nodes (but afaics you don't even use the "Copy Artifacts
> Plugin", which makes this argument pointless).
>
> - the duration/sub-steps can be easily seen (as mentioned by Max), but
> this can be achieved which some simple python scripts/plugins +
> influxDB + grafana as well.

I don't think that installing and maintaining 2 additional software 
packages + writing custom code is as easy as enabling plugin in jenkins 
and configuring it. Being able to immediately see how long each step in 
the pipeline took is not only eye-candy - it's a great hint as to where 
our potential optimization targets are.

Having said that, if similar visibility could be achieved without using 
pipeline than by all means - go for it.

-- 
Max Suraev <msuraev at sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte




More information about the OpenBSC mailing list