On 26 November 2016 at 15:45, Gary Gregory wrote:
> That sounds even more complicated to deal with :-( I would have to fiddle
> with branches just to make a Jenkins build change? Is there a precedent for
> such a set up?
Huh?
Surely the Jenkins setup script is independent of the build.
The prec
That sounds even more complicated to deal with :-( I would have to fiddle
with branches just to make a Jenkins build change? Is there a precedent for
such a set up?
I do like the idea of having the Jenkins build file right there like Travis
CI but it is slightly worrisome that we have more files t
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
Ritter
>To: Commons Developers List
>Sent: Saturday, 26 November 2016 11:18 PM
>Subject: [DISCUSS] Jenkins Pipeline DSL
>
>
>Hello,
>
>currently we define our Jenkins job through the Jenkins UI. The problem
>with this is, that there is no connection between the source c
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 [
