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

Neels Hofmeyr nhofmeyr at sysmocom.de
Mon Mar 6 13:53:39 UTC 2017


On Sun, Mar 05, 2017 at 10:03:20PM +0100, Klaus Müller wrote:
> Hi,
> 
> >> So, what would be the actual benefits?
> 
> >>* complete job config in git? (to be confirmed)
> 
> Just to clarify, the Pipeline plugin on its own doesn't provide a
> complete config handling in git. This means only the code shown in
> image [3] lives in git, configurations within the "General" or "Build
> Triggers" tab will still be handled in the web-ui.***
> For the sake of completeness the JobDSL plugin [2][ has to be mention.
> This plugin allows to put the entire job configuration to git and
> deploys jobs without previous manual setup in the web-ui.
> 
> >>* faster because less things have to be rebuilt? (to be confirmed)
> 
> Somehow I doubt that this improvement dependents on the Pipeline
> plugin, but I know to few details to have an opinion based on facts.
> :)
> 
> >>* faster because easily parallelizable/easier integration with docker? (to be
> >>  confirmed)
> 
> first point: e.g. Pipeline can trigger "down-stream-projects/stages"
> after one specific part of a
> parallel-block/matrix-configurations-project is finished.
> 
> second point: Pipeline brings a docker wrapper, so one don't have to
> pass one build script holding the entire build sequence when invoking
> the container. You can invoke as much scripts as you want within the
> docker wrapper. (no black-box god-script :)

This sounds to me like Pipelines don't actually provide any of the features I
was dreaming about, except maybe easier docker integration?

> Is this mailing list the appropriate communication channel?

yes.

> Is there already a osmocom ci wiki page, which I overlooked? I'd be
> happy to contribute!

well, searching osmocom.org for jenkins gave me

https://osmocom.org/projects/cellular-infrastructure/wiki/Jenkins
https://osmocom.org/projects/osmocom-servers/wiki/Jenkins_Node_Setup
https://osmocom.org/projects/cellular-infrastructure/wiki/Nightly_Builds
[...]

and "Wiki" is an ancient African word for "hopelessly outdated"...
We appreciate every checked and/or corrected facts on those pages,
and the Jenkins_Node_Setup could probably be merged into the Jenkins one.


> [1] https://jenkins.blobb.me/view/osmocom/

nice, a sleepy pipeline ;)

> [2] https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin

This sounds like we want to use it!

> [2.5] https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.pipelineJob
> [3] http://tinyurl.com/zbavrtp

direct link without javascript cruft: https://media.comsysto.com/images/2016-11-23-jenkins-pipelines/new-jenkins-pipeline-config--c.png

so far that doesn't look like an improvement of

  #!/bin/sh
  ./contrib/jenkins.sh

~N

-- 
- Neels Hofmeyr <nhofmeyr 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
* Geschäftsführer / Managing Directors: Harald Welte
-------------- 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/20170306/afeaa3f0/attachment.bin>


More information about the OpenBSC mailing list