commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: [DISCUSS] Jenkins Pipeline DSL
Date Sat, 26 Nov 2016 11:18:53 GMT
Seems OK to me.

However I think the script should be added to its own separate SVN/Git
branch (not trunk/master).
It's not a part of the source release per se, and as you write, it can
be applied to multiple branches.
Having it in the main source trees would be confusing, and more copies
to merge when updates are needed.

On 26 November 2016 at 10:18, Benedikt Ritter <> wrote:
> Hello,
> currently we define our Jenkins job through the Jenkins UI. The problem
> with this is, that there is no connection between the source code and the
> way it is build. The Build job configuration is versioned separately from
> the source code in Jenkins it self.
> With the Jenkins Pipeline Plugin [1] it is possible to define Jenkins Jobs
> in the source repository using a (groovy based) Job DSL [2]. So rather than
> clicking through the Jenkins UI, one just writes down what jenkins should
> to and checks it into version control.
> The cool part is, that jenkins is than able to recreate the build pipeline
> for every branch. This comes in handy when working with a gitflow like
> development process, where there are several branches being changed.
> I'd like to setup a PoC for the Commons Lang project showing, how this
> looks like in real life. The PoC can than be adopted by other components,
> if they wish.
> Please let me know if you have objections.
> Regards,
> Benedikt
> [1]
> [2]

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message