>>> <http://stacktrace.jenkins-ci.org/search?query=groovy.lang.MissingMethodException>:
>>>> No signature of method:
>>>> com.cloudbees.plugins.flow.**FlowDelegate.rescue() is applicable for
>>>> argument types: (Script1$_run_closure1_**clo
le for argument types: (Script1$_run_closure1_closure3) values:
>>>
>>>
>>> Removing the guard clause made it work. So I'm guessing guard can only
>>> handle 1 item?
>>>
>>> Thanks
>>>
>>> Petrik
>>>
>>&
tion>:
>>> No signature of method: com.cloudbees.plugins.flow.FlowDelegate.rescue()
>>> is applicable for argument types: (Script1$_run_closure1_closure3) values:
>>>
>>>
>>> Removing the guard clause made it work. So I'm guessing guard can o
Hi Bob,
You could package it up in an extension (plugin).
See
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin#BuildFlowPlugin-ExtensionPoint
/James
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bob Bick
Sent: 28 August 2013 15:51
Thanks James.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of James Nord (jnord)
Sent: Wednesday, August 28, 2013 11:09 AM
To: jenkinsci-users@googlegroups.com
Subject: RE: Build Flow Plugin - Groovy libraries
Hi Bob,
You could package it up in an
f Bob Bick
Sent: Wednesday, August 28, 2013 10:24 AM
To: jenkinsci-users@googlegroups.com
Subject: Build Flow Plugin - Groovy libraries
Hi,
I have been using the Build Flow Plugin for a while now, and it works great.
I have multiple Build Flow Plugin jobs that have common groovy code that I'
Hi,
I have been using the Build Flow Plugin for a while now, and it works great.
I have multiple Build Flow Plugin jobs that have common groovy code that I’d
like to put into a Groovy library (call it Library.groovy). The Build Flow
Plugin uses groovy.lang.GroovyShell to execute the groovy
line after a commit on your scm, you can configure the flow to be
>> triggered as the first scm-polling job is run". Does this means that if my
>> flow job is running build A, and that build contains CVS polling, Build
>> Flow Plugin can somehow intercept this, and start flow ins
is running build A, and that build contains CVS polling, Build
> Flow Plugin can somehow intercept this, and start flow instead of actual A?
> If this is true, how I can configure such trigger?
>
> Thank you
>
> --
> You received this message because you are subscribed to the Googl
it on your scm, you can configure the flow to be
triggered as the first scm-polling job is run". Does this means that if my
flow job is running build A, and that build contains CVS polling, Build
Flow Plugin can somehow intercept this, and start flow instead of actual A?
If this is true,
lowDelegate.rescue() is
>> applicable for argument types: (Script1$_run_closure1_closure3) values:
>>
>>
>> Removing the guard clause made it work. So I'm guessing guard can only
>> handle 1 item?
>>
>> Thanks
>>
>> Petrik
>>
>>
>>
(i.e. the master node keeps
> the history)? I have no clue if that is even possible...
>
> Sorry for all these newbie questions.
>
> Thanks,
>
> Bob
>
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com
for all these newbie questions.
Thanks,
Bob
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
Sent: Wednesday, August 07, 2013 2:52 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting
Nicolas and Daniel, thank you for the help.
Bob
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: Wednesday, August 07, 2013 3:02 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
I
and it seems
> to be a nice tool. I’d like to expose the information as a nice web page in
> Jenkins, but assume that is not really feasible. So, right now, I am
> thinking to just have a the users run a groovy script with text output.
> >
> > From: jenkinsci-users@googlegro
legroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
> Sent: Wednesday, August 07, 2013 2:56 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Build Flow Plugin - reporting capability
>
> you probably can use jenkins REST API to retrieve t
lf Of nicolas de loof
Sent: Wednesday, August 07, 2013 2:56 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin - reporting capability
you probably can use jenkins REST API to retrieve the list of executed jobs
from a build flow execution, not sure yet
2013/8/6 Bob Bick mail
you probably can use jenkins REST API to retrieve the list of executed jobs
from a build flow execution, not sure yet
2013/8/6 Bob Bick
> Hi,
>
> ** **
>
> The Jenkins Build Flow Plugin is replacing our “massive” home grown build
> system.
>
> ** **
>
>
Hi,
The Jenkins Build Flow Plugin is replacing our "massive" home grown build
system.
A couple of times a year, our build team will create a Build Flow job from a
template to perform the "massive" build which can last for several days.
The build team will execute the Buil
Figured it out. You specified one parallel 'lane' that executes two builds in
sequence.
The example from the wiki has three 'lanes', with one job each.
Something like the following is also possible:
parallel (
{
build('j1')
build('j2')
}, {
build('j3')
})
... which builds three jobs in two
AFAICT your syntax is wrong. From the Wiki:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build("job1") },
{ build("job2") },
{ build("job3") }
)
Note the extra braces. That's probably why it's not actually parallel.
The build flow itself is "lightweight", which means
Hi,
We have a Build Flow that runs two jobs in parallel.
DSL==>
parallel {
build('job1')
build('job2')
}
When I run the build flow, it always runs the jobs on the same node. Since each
node has a max executors equal to 2, job1 and job2 execute serially (i.e. the
Build Flow job a
static job name like
> "build-release" but when you use multiple SCM's build params don't work for
> some reason. It's an open bug not sure when the fix is coming. So
> currently we have a Sync_job that creates new jenkins jobs when a new
> release is
e multiple SCM's build params don't work for
some reason. It's an open bug not sure when the fix is coming. So
currently we have a Sync_job that creates new jenkins jobs when a new
release is created for that particular release. Thus the reason to want to
pass in a param to bu
If I understand correctly you actually have two independent jobs. You
shouldn't use flow plugin just to monitor repository and then start
downstream jobs. Each job should be configured independently with different
SCM trigger.
--
You received this message because you are subscribed to the Goog
obs based on scm commit, do it BEFORE you
> call build("job")
>
> How would I do that - any ideas? Can you give me an example?
>
> Cheers
> Tom
>
> Sent from my iPhone
>
> On 13 Jul 2013, at 21:32, Thomas Fields wrote:
>
> Hi there,
>
> The build fl
Thanks for the reply.
>> is you have to exclude some jobs based on scm commit, do it BEFORE you call
>> build("job")
How would I do that - any ideas? Can you give me an example?
Cheers
Tom
Sent from my iPhone
On 13 Jul 2013, at 21:32, Thomas Fields wrote:
> Hi t
build flow orchestrate job execution, it don't handle scm-triggers. When
flow is started, all builds involved will run
is you have to exclude some jobs based on scm commit, do it BEFORE you call
build("job")
2013/7/13 Thomas Fields
> Hi there,
>
> The build flow plug
Hi there,
The build flow plugin looks really powerful but it appears to be lacking
the ability to only trigger sub jobs when there are scm changes. I have a
simple build flow setup like so:
def tomjob = parallel ([
first: { build("tomflow1") },
second: { build("tomflow2") }
>> guard {
>> parallel ([
>> t1: { build("something") },
>> t2: { build("something else") }
>> ])
>> } rescue {
>> build("blab")
>> }
>>
>>
>>
>> 2013/6/20 pawelrychlik
I have recently written up some material of using the Cloudbees Build Flow
Plugin that goes beyond the basics. Maybe it will be of worth to someone.
OTOH feedback will also be appreciated.
The link to the blog posting is
http://delivervalue.blogspot.co.uk/2013/06/more-advanced-build-flows-with
k :)
Another pitfall: the Buildstep jobs are executed on random executors/nodes.
So you need another trick until this is fixed in the build flow plugin. You
need the
https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin.
Specify for each buildstep such a node parameter and name
What about this library? It looks pretty good.
http://cytoscape.github.io/cytoscape.js/
slide
--
View this message in context:
http://jenkins.361315.n4.nabble.com/Build-flow-plugin-does-not-visualize-the-flow-correctly-tp4660016p4667453.html
Sent from the Jenkins users mailing list archive
Hi
Is it possible somehow to don't trigger build on job, when there are no changes
for job in scm?
E.g.:
Job1 has no SCM change in time of "build command" execution. Command build(
"job1" )will not start the build because of no scm change in job1. For this job
variables it will use previous bu
Here is Build Flows page:
- https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
Hi,
I'm trying to set a variable in one job and have it passed along to the
next, something that can easily be achieved by using the Parameterized
trigger plugin.
When using the build flow plugin
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin I'm having
some trouble to d
, 2013 9:35 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin does not visualize the flow correctly
2013/3/21 Wrobel, Pawel (NSN - PL/Wroclaw)
mailto:pawel.wro...@nsn.com>>
Hi,
I guess this one is still under work right
(https://wiki.jenkins-ci.org/display/JENKINS/Buil
8 728 455 306*
> *e-mail: **pawel.wro...@nsn.com*
>
> ** **
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *ext nicolas de loof
> *Sent:* Thursday, March 21, 2013 9:22 AM
> *To:* jenkinsci-users@googlegroups.com
&
Of ext nicolas de loof
Sent: Thursday, March 21, 2013 9:22 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin does not visualize the flow correctly
flow visualization is still early stage, and probably need some love to address
complex graphs.
We are extracting it into a more g
flow visualization is still early stage, and probably need some love to
address complex graphs.
We are extracting it into a more general purpose plugin (build graph view)
so it can both handle flows and "classic" jenkins downstream chains
2013/3/21 Pawel Wrobel
> Hi,
> I have an issue with bulid
Hi,
I have an issue with bulid flow plugin. The defined flow is executed
correctly (visible in Console Output) but the flow graph is being cut at
some point of time and to further jobs from chain are ploted. the flow is
the following:
build("JOB-1")
parallel (
{
ignore(FAILURE) { b
x27;t see an option for setting the custom workspace on a build flow
> plugin, am I missing something? I currently have the first build inside the
> build flow checking out the code from SVN to the custom workspace, but I'd
> like to move that into the actual flow so that I can see t
I don't see an option for setting the custom workspace on a build flow
plugin, am I missing something? I currently have the first build inside the
build flow checking out the code from SVN to the custom workspace, but I'd
like to move that into the actual flow so that I can see the
ver tried this.
>>
>> I expected you could also retrieve this commit revision from
>> SCMRevisionState action, but git-plugin don't use this API (sic)
>>
>> 2013/2/4 Johannes Schirrmeister
>>
>>> Hi everyone,
>>>
>>> The Build
pass
> GIT_COMMIT to triggered jobs, never tried this.
>
> I expected you could also retrieve this commit revision from
> SCMRevisionState action, but git-plugin don't use this API (sic)
>
> 2013/2/4 Johannes Schirrmeister
>
>> Hi everyone,
>>
>> The
everyone,
>
> The Build Flow Plugin seems like a great way to orchestrate our build
> pipelines. I would like to ask if there is any best practice on how to
> ensure that all jobs in one pipeline checkout the same revisions of a Git
> repository.
>
> I believe the Git plugin
Hi everyone,
The Build Flow Plugin seems like a great way to orchestrate our build
pipelines. I would like to ask if there is any best practice on how to
ensure that all jobs in one pipeline checkout the same revisions of a Git
repository.
I believe the Git plugin initially sets the GIT_COMMIT
t; .
>
> Asmund
>
>
> On Thu, Jan 17, 2013 at 2:23 PM, nicolas de loof > wrote:
>
>> just use the copy-artifact plugin to copy from upstream build / pass
>> fingerprints as you would do without build flow to orchestrate jobs
>>
>>
>> 2013/1/
/ pass
> fingerprints as you would do without build flow to orchestrate jobs
>
>
> 2013/1/17 Åsmund Østvold
>
>> I am investigating the build flow plugin and have hit a issue I am not
>> able to solve. What I want to able to copy artifacts from build job to
>> test jobs
just use the copy-artifact plugin to copy from upstream build / pass
fingerprints as you would do without build flow to orchestrate jobs
2013/1/17 Åsmund Østvold
> I am investigating the build flow plugin and have hit a issue I am not
> able to solve. What I want to able to copy artifact
I am investigating the build flow plugin and have hit a issue I am not able
to solve. What I want to able to copy artifacts from build job to test
jobs:
buildJob = build("buildBinaries")
parallel(
{ build("test1") },
{ build("test2") }
)
All projects need
post-job even when some jobs are
>> unstable
>>
>>
>> 2013/1/2 Patrick
>>
>>> Ok I'm going to have to amend this answer. My idea of having a separate
>>> job at the end to gather the results would work if it wasn't for the fact
>>
> 2013/1/2 Patrick
>
>> Ok I'm going to have to amend this answer. My idea of having a separate
>> job at the end to gather the results would work if it wasn't for the fact
>> that the build flow plugin kills the build as soon as one of the jobs
>> fails. T
use gard+rescue so you can execute a post-job even when some jobs are
unstable
2013/1/2 Patrick
> Ok I'm going to have to amend this answer. My idea of having a separate
> job at the end to gather the results would work if it wasn't for the fact
> that the build flow plugin
Guard + rescue
Le 2 janv. 2013 02:11, "Patrick" a écrit :
> Ok I'm going to have to amend this answer. My idea of having a separate
> job at the end to gather the results would work if it wasn't for the fact
> that the build flow plugin kills the build as soon as
Ok I'm going to have to amend this answer. My idea of having a separate job
at the end to gather the results would work if it wasn't for the fact that
the build flow plugin kills the build as soon as one of the jobs fails.
That means I only can get the results if the build works wh
in the DSL
>
> 2013/1/1 Patrick
>
>> Hi All
>>
>> I've started using the Build Flow plugin to simplify my build pipeline.
>> I've gotten it to work just fine (all the jobs get triggered at the right
>> stage) but I can't seem to copy the generat
fingerprints or copy-artifact plugin, not sure yet about the way to define
this in the DSL
2013/1/1 Patrick
> Hi All
>
> I've started using the Build Flow plugin to simplify my build pipeline.
> I've gotten it to work just fine (all the jobs get triggered at the right
> s
Hi All
I've started using the Build Flow plugin to simplify my build pipeline.
I've gotten it to work just fine (all the jobs get triggered at the right
stage) but I can't seem to copy the generated build results from the
downstream jobs. For instance my build produces a CCM l
that build is subsequently built by the build-flow
plugin. However with a large number of jobs to re-configure it's proving
painful to track all of these issues down.
Is there anyway to find out what is causing the failure?
Thanks
Damian
users!
>
> I want to run several jobs sequentially using the Build Flow plugin. The
> jobs do not depend on each other and all must be executed even if any of
> the others fails. The problem: The call of "build(job name)" lets the
> hosting job fail (and terminate) once
Hello Jenkins users!
I want to run several jobs sequentially using the Build Flow plugin. The jobs
do not depend on each other and all must be executed even if any of the others
fails. The problem: The call of "build(job name)" lets the hosting job fail
(and terminate) once a ch
t all four nodes would be used to execute the
> "Job-Build" instances four at a time in parallel.
> Am I doing something wrong in the code?
> Also, I'm using the latest jenkins (build 1.492) and the latest build flow
> plugin (build 0.6)
>
> build("Job-Init&qu
Do you have this job configured to allow concurrent execution ?
this is not a restriction for the build-flow plugin : this one only
schedule jobs, but execution depends on jenkins build queue management and
related job configuration
2012/12/7 Glenn McElhoe
> I noticed this problem as well.
I noticed this problem as well. If you run parallel build of the same job,
it doesn't work.
My workaround was to make 12 jobs (Job-Build-1 through Job-Build-12), and
it will call them in parallel.
t that all four nodes would be used to execute the
"Job-Build" instances four at a time in parallel.
Am I doing something wrong in the code?
Also, I'm using the latest jenkins (build 1.492) and the latest build flow
plugin (build 0.6)
build("Job-Init");
parallel (
Why don't you handle the result codes in your job? Meaning just intercept
the result code and change it to 0 if the build is only unstable.
Yes, it is an ugly solution...
On Thursday, November 22, 2012 10:40:19 AM UTC-5, Egle wrote:
>
> Hi,
>
> I am trying to set up a following flow if builds:
>
the error is ugly, but the behavior is as expected. A non successful step
in the flow will interrupt the execution.
The DSL could probably be extended to ignore some build results, something
like :
build( "B" ).ignore( UNSTABLE )
contributors are welcome :)
2012/11/22 Egle
> Hi,
>
> I am tryin
Hi,
have you tried to select the "Build after other projects are build" option ?
In this case, if B is failing, C wouldnt be executed.
Clem
Hi,
I am trying to set up a following flow if builds:
build( "A" )
build( "B" )
build( "C" )
Now I get "FATAL: null" error and stack trace in console if build B is
unstable. So the flow does not execute job C. Is there a way to configure a
flow that it would only terminate if the performed buil
son
>
> Installed jenkins build flow plugin 0.5.
>
> Create a job and launched it.
> Nothing happened. Nothing launched.
>
> Replaced with version 0.4.
> Now I get an exception.
>
> Any ideas?
>
> My job is configured with:
>
> // q7 jobs will run in parallel.
> p
Running 2.2 of Hudson
Installed jenkins build flow plugin 0.5.
Create a job and launched it.
Nothing happened. Nothing launched.
Replaced with version 0.4.
Now I get an exception.
Any ideas?
My job is configured with:
// q7 jobs will run in parallel.
parallel (
{ build(q7_win
ACTION"])}
)
On Saturday, November 10, 2012 9:28:18 AM UTC-5, Nicolas De loof wrote:
>
> parallel expect a set of closures, each closure being ran in a separate
> thread :
>
> parallel( { build(A) },
> { build(B) }
> )
>
>
> 2012/11/9 r2_ >
parallel expect a set of closures, each closure being ran in a separate
thread :
parallel( { build(A) },
{ build(B) }
)
2012/11/9 r2_
> Hey, I got a really cool looking error using Build Flow Plugin. The flow
> is just 2 parameterized jobs which should run in paral
Hey, I got a really cool looking error using Build Flow Plugin. The flow
is just 2 parameterized jobs which should run in parallel on different
nodes. Here's the DSL:
parallel (
build("agile_code", ENVIRONMENT: params["ENVIRONMENT"], ACTION:
params[&quo
Been trying to get a bit of attention on this one. I've recently started
experimenting with the build-flow plugin, and I like it. However, I cannot
get the publishers to execute after the flow completes.
I've done a bit of digging through JIRA and see that there has been some
tr
always saves an empty DSL. I configure it, enter in:
>> build("job"). Then after saving, if I reconfigure it or look at the config
>> file in the filesystem the dsl is always empty. Is there something I'm
>> missing?
>>
>> I have a new install of Jenkin
he filesystem the dsl is always empty. Is there something I'm
> missing?
>
> I have a new install of Jenkins version 1.484 and I've added the Build
> Flow plugin version 0.5 to it. That's it.
>
> Thanks!
>
I've added the Build Flow
plugin version 0.5 to it. That's it.
Thanks!
> >
> > could someone post an example on how to read parameters passed from
> > one job to another using Build Flow plugin? Plugin documentationhttps://
> wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugingives
> > information on how to put a parameter to the job, b
Hi All,
any hints?
--
Regards,
Tomek Kaczanowski
On 13 Sie, 17:45, Tomek Kaczanowski
wrote:
> Hi All,
>
> could someone post an example on how to read parameters passed from
> one job to another using Build Flow plugin? Plugin
> documentationhttps://wiki.jenkins-ci.org/displa
Hello,
I am using a job that is triggering 2 jobs A & B, using build flow plugin.
Each job is build flow job itself. I can use guard and rescue, but what I
really need is to exit if Job A fails (or any job under Job A fails). So
whats the syntax of adding just exit within rescue part of J
Hi All,
could someone post an example on how to read parameters passed from
one job to another using Build Flow plugin? Plugin documentation
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin gives
information on how to put a parameter to the job, but does not show
how to use them
ok, got it:
b = build( "my-build" )
out.println b.build.properties.environment['SVN_REVISION']
Hi All,
I'm experimenting with Build Flow Plugin. Can't figure out how to get
the SVN revision from the first build so I could pass it to every
build in my flow.
Please give some hints, I'm stuck.
--
Regards,
Tomek Kaczanowski
201 - 285 of 285 matches
Mail list logo
