lto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
> > Sent: Friday, January 10, 2014 10:41 AM
> > To: jenkinsci-users@googlegroups.com
> > Subject: Re: Failing a Build Flow
> >
> >
> > On 10.01.2014, at 16:26, "Ginga, Dick" wrote:
&g
(FAILURE) will work
> >
> > -Original Message-
> > From: jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
> > Sent: Friday, January 10, 2014 10:41 AM
> > To: jenkinsci-users@googlegroups.com
> > Subject
e
> combined status.
>
> Maybe return(FAILURE) will work
>
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
> Sent: Friday, January 10, 2014 10:41 AM
> To: jenkinsci-users@goog
build.state.result = FAILURE
On Fri, Jan 10, 2014 at 7:41 AM, Daniel Beck wrote:
>
> On 10.01.2014, at 16:26, "Ginga, Dick" wrote:
>
> > My 2 cents worth not being a Groovy programmer but I use the build flow.
> >
> > You can call build like this :
> >
> > A = build(“buildA”)
> >
> > From A yo
@googlegroups.com] On Behalf Of Daniel Beck
Sent: Friday, January 10, 2014 10:41 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Failing a Build Flow
On 10.01.2014, at 16:26, "Ginga, Dick" wrote:
> My 2 cents worth not being a Groovy programmer but I use the build flow.
>
>
On 10.01.2014, at 16:26, "Ginga, Dick" wrote:
> My 2 cents worth not being a Groovy programmer but I use the build flow.
>
> You can call build like this :
>
> A = build(“buildA”)
>
> From A you can get the status:
>
> Aresult = A.build.getResult()
How'd you set the build flow's result
ehalf Of Marc MacIntyre
Sent: Friday, January 10, 2014 9:00 AM
To: jenkinsci-users@googlegroups.com
Cc: jenkinsci-users@googlegroups.com
Subject: Re: Failing a Build Flow
That aside, I'm using this in production and it works well.
Sent from my iPhone
On Jan 9, 2014, at 11:51 PM, nicolas de loof
Hmm…
That didn’t seem to work at all.
I have “Throttle Concurrent Builds” checked and “Throttle this project alone”
selected. Then, “Maximum Total Concurrent Builds set to “1” and Maximum
Concurrent Builds Per Node set to “1” (I have only 1 node).
I have switched the job back to the standard
Thanks Nicolas and Marc. I’m trying the throttle plug-in, which I had already
installed but obviously did not take advantage of.
On Jan 10, 2014, at 9:11 AM, nicolas de loof wrote:
> yes I think so
>
>
> 2014/1/10 silver
> Would “Throttle Concurrent Builds" plugin do the same?
>
> The Lock
yes I think so
2014/1/10 silver
> Would “Throttle Concurrent Builds" plugin do the same?
>
> The Locks and Latches plugin displays this message when I visit the page:
> This plugin is on the Proposed Plugin Deprecation list. Take a look at
> the Throttle Concurrent Builds Plugin.
>
> On Jan 10,
Would “Throttle Concurrent Builds" plugin do the same?
The Locks and Latches plugin displays this message when I visit the page:
This plugin is on the Proposed Plugin Deprecation list. Take a look at the
Throttle Concurrent Builds Plugin.
On Jan 10, 2014, at 8:59 AM, nicolas de loof wrote:
>
ok, then the issue isn't an orchestration but resource one - this applies
to all jobs on your instance, not just the ones from a specific flow - and
you should use
https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin to
ensure your selenium jobs don't run concurrently
2014/1/10 s
That aside, I'm using this in production and it works well.
Sent from my iPhone
> On Jan 9, 2014, at 11:51 PM, nicolas de loof wrote:
>
> I don't recommend such a fully programmatic approach, build-flow is designed
> as a DSL, admittedly not constrained to just supported keywords (because I
>
I can’t run the jobs in parallel because I’m resource limited on my Selenium
hub.
They do *not* depend on each other sequentially.
The use case is that I need a group of jobs to run through to completion in
succession, not parallel, but at the end, if at any point a job had failed, to
fail the
This isn't supported at this time - I don't really get your use-case
why can't you run those jobs in parallel ? If they actually depend on each
other sequentially, why not stop the flow when first one fails ?
2014/1/10 silver
> Nicolas,
>
> Do you have a recommendation on how I can accomplish t
Nicolas,
Do you have a recommendation on how I can accomplish the goal at hand?
Otherwise, I see no other option but to try Marc's groovy script.
Thanks.
On Jan 10, 2014, at 2:51 AM, nicolas de loof wrote:
> I don't recommend such a fully programmatic approach, build-flow is designed
> as a
I don't recommend such a fully programmatic approach, build-flow is
designed as a DSL, admittedly not constrained to just supported keywords
(because I didn't know how to do this when I started this plugin) but
clearly not supposed to be used to create such a groovy script.
2014/1/10 Marc MacInty
You are overthinking it :) The trick is to grab the return value from the
build() call and check the result of that, then explicitly set the failure
state of the buildflow.
This is what I'm doing; it's more solution than you need, but it solves
your problem.
This buildflow takes a map of jobs an
Sorry for any confusion. The line: ”println(“There were “+FailuresPresent+"
test(s) that failed”);" is outside of the if statement resulting in the example
output at the end of this message.
On Jan 9, 2014, at 9:55 PM, silver wrote:
> When I run jobs in parallel, the Build Flow fails or passe
19 matches
Mail list logo
