On Thu, Sep 19, 2013 at 3:21 PM, Daniel Beck 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 artifacts, al
On 19.09.2013, at 20:47, nicolas de loof 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 artifacts, all within a G
2013/9/19 Les Mikesell
> On Thu, Sep 19, 2013 at 12:36 PM, nicolas de loof
> 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 n
On Thu, Sep 19, 2013 at 12:36 PM, nicolas de loof
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 to orche
2013/9/19 Les Mikesell
> On Thu, Sep 19, 2013 at 10:41 AM, Schalk W. Cronjé
> 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
On Thu, Sep 19, 2013 at 10:41 AM, Schalk W. Cronjé 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 was only when I started to play
> with it that I
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
a li
On Thu, Sep 19, 2013 at 8:28 AM, nicolas de loof
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 isn't really a
jenki
o 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
Date: 19/09/2013 16:01 (GMT+00:00)
To: jenkinsci-users
Subject: Re: Build Flow Plugin and artifacts management in the DSL
O
On Thu, Sep 19, 2013 at 10:16 AM, Slide 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,
> but using the B
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
> On Thu, Sep 19, 2013 at 12:16 AM, nicolas de loof
> wrote:
> > I removed workspace in HEAD, previous version
On Thu, Sep 19, 2013 at 12:16 AM, nicolas de loof
wrote:
> I removed workspace in HEAD, previous version of plugin extend a classic job.
Doesn't the triggering svn check need that space? And probably other
triggering options, as well as the ability to archive anything it
produces? I don't
I removed workspace in HEAD, previous version of plugin extend a classic job
2013/9/18 Les Mikesell
> On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof
> 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 a
On Wed, Sep 18, 2013 at 3:06 PM, nicolas de loof
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 jenkins job
view contain
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
> On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof
> wrote:
> > not inside the flow DSL, but inside jobs. build-flow
On Wed, Sep 18, 2013 at 2:37 PM, nicolas de loof
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, etc)
>
> collect execute
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 numbe
On Wed, Sep 18, 2013 at 12:38 PM, nicolas de loof
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 do another build step w
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é
> With Build Flow Plugin you can only access Groovy modues that Jenkins
> System Groovy has access t
With Build Flow Plugin you can only access Groovy modues that Jenkins
System Groovy has access to. You cannot use @Grab to pull in extra modules.
This is a limitation of Build Flow Plugin IMHO, but Nicolas does not agree
- https://groups.google.com/forum/#!topic/jenkinsci-users/2XFDB5g7O7A).
Th
On Tue, Sep 17, 2013 at 10:06 AM, Schalk Cronjé 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 build numbers to
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 downl
On Mon, Sep 16, 2013 at 8:44 AM, Ginga, Dick 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 can pic
[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 wrote:
> There are a number of ways to "pick" the
To be honest I wouldn't pass buildnumber, I would use a run parameter so
that manual triggering should you ever need it (e.g. a failed deploy) would
be easier.
Format the build as
def job1runparam = build1.project.fullName + "#" build1.number
and then add that to the paramerers
def mypara
s.com
[mailto:jenkinsci-users@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 th
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 prod
: 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 c
;> *Sent:* Monday, September 16, 2013 9:04 AM
>> *To:* jenkins...@googlegroups.**com
>> *Subject:* Build Flow Plugin and artifacts management in the DSL
>>
>>
>>
>> Hello,
>>
>>
>>
>> We've checked the Build Flow Plugin for parallel
Of *Emmanuel
> Boudrant
> *Sent:* Monday, September 16, 2013 9:04 AM
> *To:* jenkins...@googlegroups.com
> *Subject:* Build Flow Plugin and artifacts management in the DSL
>
>
>
> Hello,
>
>
>
> We've checked the Build Flow Plugin for parallel
9:04 AM
To: jenkinsci-users@googlegroups.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 artifa
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 t
32 matches
Mail list logo
