his:
def task = new com.bla.jobs.BuildApplication()
task.start()
So now it works with the stash git commit hook.
Best regards,
Tom,
On Tuesday, 21 April 2015 09:22:40 UTC+2, Tom Deblauwe wrote:
>
> Hello,
>
> It seems one (not so good) solution is to disable giving the SHA1 to
> jenkins i
anymore about what must be built.
Best regards
Tom,
On Monday, 20 April 2015 12:47:13 UTC+2, Tom Deblauwe wrote:
>
> Hello,
>
> I am using the "groovy CPS DSL from SCM" as my configuration for my
> workflow. This works well and reads the scripts from my "workflows
Hello,
I am using the "groovy CPS DSL from SCM" as my configuration for my
workflow. This works well and reads the scripts from my "workflows.git"
reposity.
In the workflow script itself, I start with:
node {
git branch: '**', changelog: false, poll: true, url:
'ssh://git@stash:7999/my/pro
h the error.
Now I could approve it, and now my original production code works.
Best regards,
Tom,
On Tuesday, 3 March 2015 17:07:06 UTC+1, Tom Deblauwe wrote:
>
> Hello group,
>
> I was trying to use a groovy construct where I could give a closure with
> an argument, and pa
Hello group,
I was trying to use a groovy construct where I could give a closure with an
argument, and pass that closure to a function, something like this below:
class Test {
int num = 5
}
def runit(def func) {
echo "Will run it"
def obj = new Test()
func(obj)
echo "Ran it"
}
node {
hello list,
We are using the buildflow plugin succesfully. We have one job with parameters
and also associated with a label, and italso has the enable concurrent builds
option set. We also have multiple buildslaves with the same label. We expected
that the buildflow jobs are scheduled evenly
Hello,
I want to create a modularized system for my jobs in order for them to be
maintainable. I looked at all sorts of template plugins and generators, but
it is either difficult(XML groovy script transformation?) or not really
reuseable in my opinion. Now I stumbled upon the build flow plugin
Hello,
I have the same problem here but no solution.
Notice that you also can use "covhtml" with the same syntax as "bullshtml"
to generate even better output html than bullshtml.
Statement coverage is really unneeded according to the bullseye guys. The
best solution would possibly be that the
