thank you all for your input.
I am investigating to do a local change to build flow plugin.
Introduce a comment "//includefile " that is detected and
replaced it with the content of the file. I have a demo working.
What is missing is to be able to have a parameter as the second argument.
If you
It's all on the master.
On Mon, Apr 7, 2014 at 9:47 AM, Les Mikesell wrote:
> On Mon, Apr 7, 2014 at 11:13 AM, Marc MacIntyre
> wrote:
> > Put your build flow in a groovy class, and reference it in the build flow
> > like:
> >
> > File myFile = new File("/var/lib/jenkins/groovy/myClass.groovy"
On Mon, Apr 7, 2014 at 11:13 AM, Marc MacIntyre wrote:
> Put your build flow in a groovy class, and reference it in the build flow
> like:
>
> File myFile = new File("/var/lib/jenkins/groovy/myClass.groovy");
Does everything load from the master or would you have to manage your
own installation o
It would be a nice feature :)
My approach is to generate the build flow jobs via the Gary Hale's
gradle-jenkins plugin. Everything is then stored in source control and the
jobs generated by runnign a gradle script.
HTH.
On Monday, 7 April 2014 08:13:29 UTC+1, asmundo wrote:
>
> hi all,
>
> I w
Put your build flow in a groovy class, and reference it in the build flow
like:
File myFile = new File("/var/lib/jenkins/groovy/myClass.groovy");
Class myUtils = new
GroovyClassLoader(getClass().getClassLoader()).parseClass(myFile);
myUtils.dsl = this
I used a bunch of static methods to define v
hi all,
I want to thank Jenkins community for a this excellent tool.
To make my work even easier I would very much like to be able to do
regression testing on my build flow scripts. See [1] for motivation. If
anybody have solved this already I would very much like to know the
solution.
My sugges
