On Wed, Mar 26, 2014 at 3:47 AM, teilo teilo+goo...@teilo.net wrote:
The states I'd want to store are the polling status of the underlying
subversion repository related to the job,
No workspace so - this is a bit moot as you have nowhere to checkout and
nowhere for jenkins to calculate the
My Build Flow job has the following structure:
b = build(Build)
parallel (
{
build(Test-Device, device: id1)
},
{
build(Test-Device, device: id2)
}
)
In the Build job, I have a variable: export DEVICES=id1 id2. From the
flow DSL, how can I have access to this variable in order
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of h...@renatorodrigues.me
Sent: Tuesday, March 25, 2014 11:25 AM
To: jenkinsci-users@googlegroups.com
Subject: How to access jobs variables with Build Flow Plugin?
My Build Flow job has the following structure:
b = build(Build)
parallel (
{
build
On Sat, Mar 22, 2014 at 3:04 AM, teilo teilo+goo...@teilo.net wrote:
Hi Les,
Firstly a workspace will never give you true stateless in Jenkins à workspace
availability is best effort (slave may be unavailable, workspace may be
deleted to reclaim slave disk space...)
Depending on what
Hi Les,
Firstly a workspace will never give you true stateless in Jenkins à workspace
availability is best effort (slave may be unavailable, workspace may be deleted
to reclaim slave disk space...)
Depending on what state you want to store you should look at writing either an
extension to the
I can write to a file successfully by adding the Jenkins workspace to the
path. try something like this:
workspace = build.environment.get(WORKSPACE);
new File(${workspace}/foo.ini).withWriter { out -
out.writeLine(this is a test)
}
On Tuesday, March 4, 2014 3:59:29 AM UTC-8, dev123
] On Behalf Of slopes...@gmail.com
Sent: 20 March 2014 17:00
To: jenkinsci-users@googlegroups.com
Subject: Re: Cannot write file to disk using the build Flow plugin
I can write to a file successfully by adding the Jenkins workspace to the path.
try something like this:
workspace
On Thu, Mar 20, 2014 at 12:19 PM, James Nord (jnord) jn...@cisco.com wrote:
Attempting to do this is a bad idea for the future.
The workspace does not exist in the latest version of the plugin (and having
it allowed people to abuse its functionality from being an orchestrator.)
Is there an
-users@googlegroups.com
Subject: RE: [Build Flow Plugin] how to execute different rescue when job
failed in guard
Thanks James for your comments
I try the following which is little different from your comment, and it can
work now.
def b
def guard_result =FAILURE
guard{
b=build(JobA)
} rescue
to handle the Cancel action from
Jenkins?
Thanks,
Hobby
-Original Message-
From: Hobby Tan
Sent: Thursday, March 13, 2014 12:45 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: [Build Flow Plugin] how to execute different rescue when job
failed in guard
Thanks James
Anyone has idea for this ??
Thanks,
Hobby
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of
Sent: Tuesday, March 11, 2014 12:31 AM
To: jenkinsci-users@googlegroups.com
Subject: [Build Flow Plugin] how to execute different rescue when job failed
@googlegroups.com
Subject: [Build Flow Plugin] how to execute different rescue when job failed
in guard
I want to execute different rescue based on job was failed or not in guard
as below:
guard{
build(JobA)
build(JobB)
}rescue{
if JobA or JobB failed
failed clean
{
build(Failure_Clean])
}
}
Hobby
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of James Chapman
Sent: Wednesday, March 12, 2014 8:01 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: [Build Flow Plugin] how
I want to execute different rescue based on job was failed or not in guard
as below:
guard{
build(JobA)
build(JobB)
}rescue{
if JobA or JobB failed
failed clean
else
normal clean
}
--
You received this message because you are subscribed to the Google Groups
Hello,
I would know if it's possible to get all Jenkins jobs name in Build Flow
Plugin? In order to use this as parameters for trigger particular job.
Thanks a lot
Thomas Collignon
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group
Given this flow:
def Build = { SpecificBuildSelectorbuildNumber + it +
/buildNumber/SpecificBuildSelector }
def BVT2Rescue = {
build(Restart_NRobotRemote, Test_Automation_Workstation:
BVT2.build.properties['builtOnStr'], WORKSPACE: BVT2.build.workspace)
build(BVT_CR2600, BN2:
I have a build flow job where the first step I need to execute is writing a
file to disk:
Properties props = new Properties();
props.setProperty(Var1, asdasd);
File f = new File(Configs.properties);
OutputStream out = new FileOutputStream( f );
props.store(out,null);
When I run the job I get:
I don't think build flows have a workspace, they run in the JVM. It is probably
trying to write to JENKINS_HOME
Sent from my iPhone
On Mar 4, 2014, at 3:59 AM, dev123 delber...@gmail.com wrote:
I have a build flow job where the first step I need to execute is writing a
file to disk:
:
Hello World
Foo
Bar
As DSL in a build flow I only get:
Hello World
CloudBees Build Flow
pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
v 0.10
What am I doing wrong?
-Steve Maring
Orlando, FL
--
You received this message because you are subscribed to the Google
in a build flow I only get:
Hello World
CloudBees Build Flow
pluginhttps://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
v 0.10
What am I doing wrong?
-Steve Maring
Orlando, FL
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group
just for completeness and clarity, this works in a Build Flow DSL ...
public class FooBar {
private OutputStream out;
public FooBar(OutputStream out) {
this.out = out;
}
public static void sayFoo(OutputStream out) {
out.println(Foo);
}
public void sayBar() {
)
}
serverDeployJobs.add(deployJob)
}
// schedule deploy jobs in parallel
parallel(serverDeployJobs)
Hope that helps,
Stuart
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Generating-parallel-flow-with-Build-Flow-Plugin-tp4687604p4691098.html
Sent from the Jenkins
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Generating-parallel-flow-with-Build-Flow-Plugin-tp4687604p4691098.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups
On 16 Jan 2014, at 19:15, Rodrigo García Peláez rodrigogarciapel...@gmail.com
wrote:
Any ideas?
When I run sequentially the GENERIC_DEPLOYMENT job quickly I get the job to
run twice in parallel. The quite period is 0 for this job. But when I do it
from the Build Flow job below it runs
Hi,
Thanks for your response.
My problem is that I'm trying to build it dynamically depending on the
parameters. I can receive a list of servers to deploy to so I want to run
the job to deploy to each server in parallel. That list of servers can be
different every time, as it's passed
Peláez wrote:
Hi,
I'm trying to use build flow plugin
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin to run the
same job multiple times in parallel but with different parameters that I
produce from a given String parameter in the job
I was trying something like
build flow is an orchestration plugin, not a scripting one. The DSL is
actually groovy based, but should be used only to trigger jobs.
2014/1/8 dev123 delber...@gmail.com
I have installed the Build Flow Plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
making the Build
+1, Nicolas De loof wrote:
build flow is an orchestration plugin, not a scripting one. The DSL is
actually groovy based, but should be used only to trigger jobs.
2014/1/8 dev123 delb...@gmail.com javascript:
I have installed the Build Flow Plugin:
https://wiki.jenkins-ci.org/display
On Thu, Jan 9, 2014 at 4:17 AM, dev123 delber...@gmail.com wrote:
Yes that make sense but it seems to me that the same functionality can be
achieved with the Groovy Plugin not as pretty though.
And why is the Build Environment removed from the Build Flow job type (e.g
Set Build Name is not
I have installed the Build Flow Plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
making the Build Flow Job Type available. But this jobtype does not have
the *Build Environment *configuration like the other jobtypes (freestyle,
maven, etc.) which I need.
I have also
Hi,
I'm trying to pass a parameter from one job in a build flow to another. I
have a job called 'jenktest' which sets a variable ENV_TEST in a shell exec
step. I want to catch that variable in the build flow and pass it to the
next step.
What I am doing so far:
//#
is ready, it has to wait until build #1 is done. Claim
plugin is one such plugin that serializes build order.
--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/Build-Flow-Plugin-Multiple-concurrent-jobs-are-ended-in-sequence-tp4680317p4681312.html
Sent from the Jenkins users
That is the standard Jenkins behaviour. You'll notice the same without the
build-flow plugin.
On Friday, 15 November 2013 17:12:59 UTC, Zofia Majenka wrote:
Hi,
We are using the Build Flow Plugin in Jenkins. This is scenario:
Start the flow 1: Job1 - Job2 - Job3
Start the flow 2
November 2013 17:13
*To:* jenkins...@googlegroups.com
*Subject:* Problem with Build Flow Plugin
Hi,
We are using the Build Flow Plugin in Jenkins. This is scenario:
Start the flow 1: Job1 - Job2 - Job3
Start the flow 2: Job1 - Job2 - Job3
Start the flow 3: Job1 - Job2 - Job3
Hi,
We are using the Build Flow Plugin in Jenkins. This is scenario:
Start the flow 1: Job1 - Job2 - Job3
Start the flow 2: Job1 - Job2 - Job3
Start the flow 3: Job1 - Job2 - Job3
The same flow is started 3 times with a few minutes delay between them.
We have noticed
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Zofia Majenka
Sent: 15 November 2013 17:13
To: jenkinsci-users@googlegroups.com
Subject: Problem with Build Flow Plugin
Hi,
We are using the Build Flow Plugin in Jenkins. This is scenario:
Start the flow 1: Job1 - Job2 - Job3
Start
...@googlegroups.com javascript:] *On Behalf Of *Zofia Majenka
*Sent:* 15 November 2013 17:13
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Problem with Build Flow Plugin
Hi,
We are using the Build Flow Plugin in Jenkins. This is scenario:
Start the flow 1: Job1 - Job2 - Job3
Start
Currently we trigger projects by using build(name of project);.. etc.
This blocks the build flow until the build is finished.
Is there a way to trigger a project that is nonblocking, and then
immediately execute other groovy tasks afterwards?
ie:
build1 = nonblockingbuild(foo);
print whatever;
I'm using a custom built version of the plugin (using the code from this
PR: https://github.com/jenkinsci/build-flow-plugin/pull/40). As you can see
from the commit history, this is based on the unreleased 0.11 version.
In my further exploration of this plugin (and the new version I had built
a custom built version of the plugin (using the code from this
PR: https://github.com/jenkinsci/build-flow-plugin/pull/40). As you can
see from the commit history, this is based on the unreleased 0.11 version.
In my further exploration of this plugin (and the new version I had built)
I realized
Future.get() don't return the Build object after completion, have no idea
what can get wrong
2013/10/30 Slide slide.o@gmail.com
I have an issue with the Build Flow plugin in that once a job that is
launched completes, the build flow never continues on. I've reduced my
build flow
On Wed, Oct 30, 2013 at 2:35 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
Workspace support has indeed been removed
Too many user use build-flow DSL as a groovy script console, that is another
topic (- scriptler plugin)
I'm still missing what would be wrong with having the build-flow
scriptler is for groovy scripts
build flow is (supposed to) offer a DSL to orchestrate job execution
both make sense. Maybe you're looking for something in the middle
2013/10/30 Les Mikesell lesmikes...@gmail.com
On Wed, Oct 30, 2013 at 2:35 AM, nicolas de loof
nicolas.del...@gmail.com
On Wed, Oct 30, 2013 at 7:48 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
scriptler is for groovy scripts
build flow is (supposed to) offer a DSL to orchestrate job execution
both make sense. Maybe you're looking for something in the middle
I'd like to create a more versatile 'matrix
I have an issue with the Build Flow plugin in that once a job that is
launched completes, the build flow never continues on. I've reduced my
build flow to a single step which just launches another build. I know that
build completes because I can see in it's build log that it is done, but
the flow
On Thu, Sep 19, 2013 at 3:21 PM, Daniel Beck m...@beckweb.net wrote:
it's just about using the adequate jenkins API
Jenkins.instance.getItemByFullName(job).scheduleBuild(...)
Let's make this into a real example. Execution of two other jobs (in parallel
even) below, plus copying their
build flow is a flightweight task, supposed to orchestrate jobs, not to
archive content or manage a workspace.
It can be triggered by commit hooks, best option.
2013/9/19 Les Mikesell lesmikes...@gmail.com
On Thu, Sep 19, 2013 at 12:16 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
I
On Thu, Sep 19, 2013 at 10:16 AM, Slide slide.o@gmail.com wrote:
That's what I do. I have my hourly/nightly checks kick off a job that uses
the Build Flow plugin to build other projects. It's worked very well for me
so far. I had issues with the trigger parameterized build and other plugins
to the previous example you will need to ${PARAM}s in your SVN setup
--
Schalk W. Cronjé
[Sent from mobile phone]
Original message
From: Les Mikesell lesmikes...@gmail.com
Date: 19/09/2013 16:01 (GMT+00:00)
To: jenkinsci-users jenkinsci-users@googlegroups.com
Subject: Re: Build Flow
On Thu, Sep 19, 2013 at 8:28 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
build flow is a flightweight task, supposed to orchestrate jobs, not to
archive content or manage a workspace.
It can be triggered by commit hooks, best option.
I guess I don't understand having a jenkins job
That's what I do. I have my hourly/nightly checks kick off a job that uses
the Build Flow plugin to build other projects. It's worked very well for me
so far. I had issues with the trigger parameterized build and other
plugins, but using the Build Flow plugin in the method I described has been
I
really need is some boilerplate groovy code or library to do the same
operations as the build flow plugin but in an ordinary build step.
Would the 'run other jobs in parallel' feature be possible there?
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you
if later
versions will have an equivalent. I'm beginning to think that what I
really need is some boilerplate groovy code or library to do the same
operations as the build flow plugin but in an ordinary build step.
Would the 'run other jobs in parallel' feature be possible there?
--
Les
On Thu, Sep 19, 2013 at 12:36 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
The very first time I read about Build Flow I also thought it to be a
DSL
for specifying complex steps in a job.
Maybe it was wishful thinking, because that seems to be what I need.
It's not, it's a tool
2013/9/19 Les Mikesell lesmikes...@gmail.com
On Thu, Sep 19, 2013 at 12:36 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
The very first time I read about Build Flow I also thought it to be a
DSL
for specifying complex steps in a job.
Maybe it was wishful thinking, because
On 19.09.2013, at 20:47, nicolas de loof nicolas.del...@gmail.com wrote:
it's just about using the adequate jenkins API
Jenkins.instance.getItemByFullName(job).scheduleBuild(...)
Let's make this into a real example. Execution of two other jobs (in parallel
even) below, plus copying their
this is a voluntary limitation. Even flow uses groovy, it's supposed to be
a DSL, not a system groovy script. Use scriptler/groovy plugin/etc if you
want to do such thing
2013/9/18 Schalk Cronjé ysb...@gmail.com
With Build Flow Plugin you can only access Groovy modues that Jenkins
System
On Wed, Sep 18, 2013 at 12:38 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
this is a voluntary limitation. Even flow uses groovy, it's supposed to be a
DSL, not a system groovy script. Use scriptler/groovy plugin/etc if you want
to do such thing
OK, but how? I don't see the option to
not inside the flow DSL, but inside jobs. build-flow is an orchestrator,
it's not here to replace jenkins classic way to share artifacts between
builds (fingerprints, copyartifact plugin, build number parameter, etc)
collect executed jobs build object
def b = build( foo )
then pass build number
On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
not inside the flow DSL, but inside jobs. build-flow is an orchestrator,
it's not here to replace jenkins classic way to share artifacts between
builds (fingerprints, copyartifact plugin, build number parameter,
build flow don't have a workspace, so no place to store child artifacts.
you could trigger a final job to collect other ones artifacts using
copy-artifact
2013/9/18 Les Mikesell lesmikes...@gmail.com
On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
not inside
On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
build flow don't have a workspace, so no place to store child artifacts.
you could trigger a final job to collect other ones artifacts using
copy-artifact
That's, ummm, interesting... I see a workspace in the
I removed workspace in HEAD, previous version of plugin extend a classic job
2013/9/18 Les Mikesell lesmikes...@gmail.com
On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof
nicolas.del...@gmail.com wrote:
build flow don't have a workspace, so no place to store child artifacts.
you could
This blog post might be insightful -
http://delivervalue.blogspot.co.uk/2013/06/more-advanced-build-flows-with-jenkins.html
It does show you how to run a number of similar jobs in parallel and then
send the resulting build numbers to a downstream job.
It does not, however, show you how to
On Tue, Sep 17, 2013 at 10:06 AM, Schalk Cronjé ysb...@gmail.com wrote:
This blog post might be insightful -
http://delivervalue.blogspot.co.uk/2013/06/more-advanced-build-flows-with-jenkins.html
It does show you how to run a number of similar jobs in parallel and then
send the resulting
Hello,
We've checked the Build Flow Plugin for parallel execution, is is possible
to manage the artifact in the plugin.
Example :
parallel (
// Each job is going to produce one artifact{ build(job1) },
{ build(job2) },
...
{ build(jobN) }
)
// deploy need access to all
Boudrant
*Sent:* Monday, September 16, 2013 9:04 AM
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Build Flow Plugin and artifacts management in the DSL
Hello,
We've checked the Build Flow Plugin for parallel execution, is is possible
to manage the artifact
.**com
*Subject:* Build Flow Plugin and artifacts management in the DSL
Hello,
We've checked the Build Flow Plugin for parallel execution, is is
possible to manage the artifact in the plugin.
Example :
parallel (
// Each job is going to produce one artifact
{ build(job1
: Build Flow Plugin and artifacts management in the DSL
There are a number of ways to pick the artifacts to archive. Use the
In your DSL, do
B1 = build(job 1)
B2 = build(job 2)
Then pass them to Deploy as parameters.
Then, as just stated, your deploy job can pick specific builds.
From: jenkinsci
Thanks, I will try !
-emmanuel
On Monday, September 16, 2013 6:04:02 AM UTC-7, Emmanuel Boudrant wrote:
Hello,
We've checked the Build Flow Plugin for parallel execution, is is possible
to manage the artifact in the plugin.
Example :
parallel (
// Each job is going to produce one
@googlegroups.com] On Behalf Of Emmanuel Boudrant
Sent: Monday, September 16, 2013 9:34 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Build Flow Plugin and artifacts management in the DSL
I am not sure it will work, copy Artifact plugin is going to only copy the last
successful artifact
Boudrant wrote:
Hello,
We've checked the Build Flow Plugin for parallel execution, is is
possible to manage the artifact in the plugin.
Example :
parallel (
// Each job is going to produce one artifact{ build(job1) },
{ build(job2) },
...
{ build(jobN
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Les Mikesell
Sent: Monday, September 16, 2013 10:51 AM
To: jenkinsci-users
Subject: Re: Build Flow Plugin and artifacts management in the DSL
On Mon, Sep 16, 2013 at 8:44 AM, Ginga, Dick dick.gi...@perkinelmer.com wrote:
There are a number of ways to pick
On Mon, Sep 16, 2013 at 8:44 AM, Ginga, Dick dick.gi...@perkinelmer.com wrote:
There are a number of ways to “pick” the artifacts to archive. Use the
In your DSL, do
B1 = build(“job 1”)
B2 = build(“job 2”)
Then pass them to Deploy as parameters.
Then, as just stated, your deploy
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
which
is not what I want. I want the results gathering to always take place,
even
a post-job even when some jobs are
unstable
2013/1/2 Patrick petrikva...@gmail.com
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
@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 09:28
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs
AggregatedTestResultPublisher should work with build-flow, passing
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
which
is not what I
are
unstable
2013/1/2 Patrick petrikva...@gmail.com
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
I see the class javadoc for that class but how would I use that to actually
aggregate the junit tests to report in the build-flow plugin?
Is it also possible to discourage people in the documentation and yet leave
the workspace there so its possible?
On Fri, Aug 30, 2013 at 9:22 AM, nicolas de
Russell jjruss...@gmail.com
I see the class javadoc for that class but how would I use that to
actually aggregate the junit tests to report in the build-flow plugin?
Is it also possible to discourage people in the documentation and yet
leave the workspace there so its possible?
On Fri, Aug
this should be moved to the dev list...
/James
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof
Sent: 30 August 2013 15:52
To: jenkinsci-users@googlegroups.com
Subject: Re: Build flow plugin: How to copy results from downstream jobs
I
First of all, I have to say that the build-flow-plugin is great. It has
simplified my build flow significantly, so thanks for that! I had a couple
questions about ignore and retry that can hopefully be answered.
I currently have an ignore(FAILURE) block with a build inside. I would
actually like
Can't you use log parser plugin to change target job status depending on
console output ?
2013/8/30 Slide slide.o@gmail.com
First of all, I have to say that the build-flow-plugin is great. It has
simplified my build flow significantly, so thanks for that! I had a couple
questions about
** **
*From:* jenkinsci-users@googlegroups.com [mailto:
jenkinsci-users@googlegroups.com] *On Behalf Of *nicolas de loof
*Sent:* 30 August 2013 15:52
*To:* jenkinsci-users@googlegroups.com
*Subject:* Re: Build flow plugin: How to copy results from downstream jobs
** **
I don't want
plugin to change target job status depending on
console output ?
2013/8/30 Slide slide.o@gmail.com
First of all, I have to say that the build-flow-plugin is great. It has
simplified my build flow significantly, so thanks for that! I had a couple
questions about ignore and retry that can
target job status depending on
console output ?
2013/8/30 Slide slide.o@gmail.com
First of all, I have to say that the build-flow-plugin is great. It has
simplified my build flow significantly, so thanks for that! I had a couple
questions about ignore and retry that can hopefully
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
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'd
like to put
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
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
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, how I can configure such trigger?
Thank you
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 Google Groups
Jenkins Users group.
To unsubscribe from
jobs are
unstable
2013/1/2 Patrick petrikva...@gmail.com javascript:
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
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, how I can
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 bb...@netjets.com
Hi,
** **
The Jenkins Build Flow Plugin is replacing our “massive” home grown build
system.
** **
A couple of times a year
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 bb
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 bb...@netjets.com
Hi,
The Jenkins
to just have a the users run a groovy script with text output.
From: jenkinsci-users@googlegroups.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
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
101 - 200 of 260 matches
Mail list logo
