subject:"\"Build Flow plugin\""

yes, by intention, as the real world CD scenario I've considered aren't
static and can involve various steps depending on runtime context

start a new pipeline is just about re-trigger the initial step (which I
expect to be a git push)
re-run a build could make sense, but then you can just enable retry plugin
on the adequate jobs
manual steps aren't considered by build flow plugin (but fully supported by
workflow)


2015-07-21 17:02 GMT+02:00 Christoph Kutzinski :

> Am I right when saying the the buildgraphview-plugin is a king of 'after
> the fact' view of a pipeline run?
> *I.e. I can see the results of a pipeline afterwards, but I can not
> actively control a pipeline (lie in the Build Pipeline pluing):*
> *- starting a new pipeline run*
> *- re-running a build*
> *- triggering manul steps*
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:45 Uhr
> *Von:* "nicolas de loof" 
> *An:* "jenkinsci-users@googlegroups.com"  >
> *Betreff:* Re: Re: Build Pipeline plugin and Build Flow plugin
>  build graph view do rely on upstreamCause so should handle most
> relations between builds
> and for the others (including build-flow) do offer an extension point to
> discover other relations
>
> 2015-07-21 16:44 GMT+02:00 Christoph Kutzinski :
>>
>>   Thanks!
>> I didn't know about
>> https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin
>>
>> Can I also define manual triggered steps in a setup of the Build-Flow
>> plugin and the build-graphview-plugin like you can do with the build
>> pipeline plugin?
>>
>> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
>> *Von:* "nicolas de loof" 
>> *An:* "jenkinsci-users@googlegroups.com" <
>> jenkinsci-users@googlegroups.com>
>>
>> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>>  build flow did introduce buildgraphview-plugin for this exact use case
>>
>>  build pipeline only can rendre static and mostly sequential pipelines
>>
>> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>>>
>>>  Hi,
>>>
>>> I'm trying to set up a CD pipeline with Jenkins where I can
>>>
>>> I) concisely define the relationship (triggers) between the single
>>> pipeline steps (jobs)
>>> II) have a nice visualisation of the full pipeline
>>>
>>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>>> plugin is a nice fit for II.
>>> However, the Build Pipeline plugin doesn't seem to understand the job
>>> dependencies defined via the Build Flow plugin.
>>>
>>> Does someone have experiences with similar setups? What is your solution
>>> for this?
>>>
>>>
>>> cheers
>>> Christoph
>>>
>>>
>>>
>>> --
>>> 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 email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>>> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1

Aw: Re: Re: Build Pipeline plugin and Build Flow plugin

Am I right when saying the the buildgraphview-plugin is a king of 'after the fact' view of a pipeline run?

I.e. I can see the results of a pipeline afterwards, but I can not actively control a pipeline (lie in the Build Pipeline pluing):

- starting a new pipeline run

- re-running a build

- triggering manul steps

Gesendet: Dienstag, 21. Juli 2015 um 14:45 Uhr
Von: "nicolas de loof"
An: "jenkinsci-users@googlegroups.com"
Betreff: Re: Re: Build Pipeline plugin and Build Flow plugin

build graph view do rely on upstreamCause so should handle most relations between builds
and for the others (including build-flow) do offer an extension point to discover other relations

2015-07-21 16:44 GMT+02:00 Christoph Kutzinski <ku...@gmx.de>:

Thanks!

I didn't know about https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

Can I also define manual triggered steps in a setup of the Build-Flow plugin and the build-graphview-plugin like you can do with the build pipeline plugin?

Gesendet: Dienstag, 21. Juli 2015 um 14:37 Uhr
Von: "nicolas de loof" <nicolas.del...@gmail.com>
An: "jenkinsci-users@googlegroups.com" <jenkinsci-users@googlegroups.com>
Betreff: Re: Build Pipeline plugin and Build Flow plugin

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski <ku...@gmx.de>:

Hi,

I'm trying to set up a CD pipeline with Jenkins where I can

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

Does someone have experiences with similar setups? What is your solution for this?

cheers

Christoph

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41.

For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-6e98f37c-ab18-4f08-9ac4-6db9b3071625-1437490941266%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Build Pipeline plugin and Build Flow plugin

build graph view do rely on upstreamCause so should handle most relations
between builds
and for the others (including build-flow) do offer an extension point to
discover other relations

2015-07-21 16:44 GMT+02:00 Christoph Kutzinski :

> Thanks!
> I didn't know about
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin
>
> Can I also define manual triggered steps in a setup of the Build-Flow
> plugin and the build-graphview-plugin like you can do with the build
> pipeline plugin?
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
> *Von:* "nicolas de loof" 
> *An:* "jenkinsci-users@googlegroups.com"  >
> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>  build flow did introduce buildgraphview-plugin for this exact use case
>
> build pipeline only can rendre static and mostly sequential pipelines
>
> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>>
>>  Hi,
>>
>> I'm trying to set up a CD pipeline with Jenkins where I can
>>
>> I) concisely define the relationship (triggers) between the single
>> pipeline steps (jobs)
>> II) have a nice visualisation of the full pipeline
>>
>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>> plugin is a nice fit for II.
>> However, the Build Pipeline plugin doesn't seem to understand the job
>> dependencies defined via the Build Flow plugin.
>>
>> Does someone have experiences with similar setups? What is your solution
>> for this?
>>
>>
>> cheers
>> Christoph
>>
>>
>>
>> --
>> 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
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41
> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Aw: Re: Build Pipeline plugin and Build Flow plugin

Thanks!

I didn't know about https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

Can I also define manual triggered steps in a setup of the Build-Flow plugin and the build-graphview-plugin like you can do with the build pipeline plugin?

Gesendet: Dienstag, 21. Juli 2015 um 14:37 Uhr
Von: "nicolas de loof"
An: "jenkinsci-users@googlegroups.com"
Betreff: Re: Build Pipeline plugin and Build Flow plugin

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski <ku...@gmx.de>:

Hi,

I'm trying to set up a CD pipeline with Jenkins where I can

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

Does someone have experiences with similar setups? What is your solution for this?

cheers

Christoph

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Build Pipeline plugin and Build Flow plugin

oh yes indeed, oss version only has a simplified step vizualisation

2015-07-21 16:42 GMT+02:00 Christoph Kutzinski :

> Yes,
> but it doesn't have any visualisation, either (unless I use Jenkins
> Enterprise), has it?
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
> *Von:* "nicolas de loof" 
> *An:* "jenkinsci-users@googlegroups.com"  >
> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>  Did you considered using workflow plugin ?
>
> 2015-07-21 16:37 GMT+02:00 nicolas de loof :
>>
>> build flow did introduce buildgraphview-plugin for this exact use case
>>
>> build pipeline only can rendre static and mostly sequential pipelines
>>
>> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>>>
>>>  Hi,
>>>
>>> I'm trying to set up a CD pipeline with Jenkins where I can
>>>
>>> I) concisely define the relationship (triggers) between the single
>>> pipeline steps (jobs)
>>> II) have a nice visualisation of the full pipeline
>>>
>>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>>> plugin is a nice fit for II.
>>> However, the Build Pipeline plugin doesn't seem to understand the job
>>> dependencies defined via the Build Flow plugin.
>>>
>>> Does someone have experiences with similar setups? What is your solution
>>> for this?
>>>
>>>
>>> cheers
>>> Christoph
>>>
>>>
>>>
>>> --
>>> 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 email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>>> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41
> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzneprg3%3De2QUPU%2Ba0aZtHU%3DzZQxnZKqU8Rojeig8qGsYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Pipeline plugin and Build Flow plugin

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :

> Hi,
>
> I'm trying to set up a CD pipeline with Jenkins where I can
>
> I) concisely define the relationship (triggers) between the single
> pipeline steps (jobs)
> II) have a nice visualisation of the full pipeline
>
> The Build Flow plugin is a good fit for I, while the Build Pipeline plugin
> is a nice fit for II.
> However, the Build Pipeline plugin doesn't seem to understand the job
> dependencies defined via the Build Flow plugin.
>
> Does someone have experiences with similar setups? What is your solution
> for this?
>
>
> cheers
> Christoph
>
>
> --
> 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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Aw: Re: Build Pipeline plugin and Build Flow plugin

Yes,

but it doesn't have any visualisation, either (unless I use Jenkins Enterprise), has it?

Gesendet: Dienstag, 21. Juli 2015 um 14:37 Uhr
Von: "nicolas de loof"
An: "jenkinsci-users@googlegroups.com"
Betreff: Re: Build Pipeline plugin and Build Flow plugin

Did you considered using workflow plugin ?

2015-07-21 16:37 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>:

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski <ku...@gmx.de>:

Hi,

I'm trying to set up a CD pipeline with Jenkins where I can

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

Does someone have experiences with similar setups? What is your solution for this?

cheers

Christoph

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Build Pipeline plugin and Build Flow plugin

Did you considered using workflow plugin ?

2015-07-21 16:37 GMT+02:00 nicolas de loof :

> build flow did introduce buildgraphview-plugin for this exact use case
>
> build pipeline only can rendre static and mostly sequential pipelines
>
> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>
>> Hi,
>>
>> I'm trying to set up a CD pipeline with Jenkins where I can
>>
>> I) concisely define the relationship (triggers) between the single
>> pipeline steps (jobs)
>> II) have a nice visualisation of the full pipeline
>>
>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>> plugin is a nice fit for II.
>> However, the Build Pipeline plugin doesn't seem to understand the job
>> dependencies defined via the Build Flow plugin.
>>
>> Does someone have experiences with similar setups? What is your solution
>> for this?
>>
>>
>> cheers
>> Christoph
>>
>>
>> --
>> 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
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>> <https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Build Pipeline plugin and Build Flow plugin

Hi,

 

I'm trying to set up a CD pipeline with Jenkins where I can

 

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

 

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

 

Does someone have experiences with similar setups? What is your solution for this?

 

 

cheers

Christoph

 



-- 
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 email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Build flow plugin iterate builds for a job.

2015-07-17 Thread Jacek Tomaka

Hi, 
I have a few jenkins job that use promoted builds plugin. Each of jobs has a 
bunch of parameters. 

I promote builds on demand using "only when manually promoted". This is fine 
for single builds but usually i want to promote a set of builds (one per job) 
with matching parameter values. 

Now i would like to create a build flow job that would for jobs A,B,C iterate 
builds of A,B,C to see if the value is as required and if so, kick off the 
promotion process. 

Can this be done using build flow plugin? I mean, how do i iterate builds of a 
job by name?
I am thinking about something like: 

builds = job("A").getBuilds()

then iterating over the builds, getting parameters of each of them and if 
parameters match, save it's build number to execute promotion later.

How do i solve this?
Regards.
Jacek Tomaka

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/izebrtfajmzibxeqaync%40itcm.
For more options, visit https://groups.google.com/d/optout.

Build Flow plugin -- hostnames of other parallel jobs?

2015-07-07 Thread Adam Seering

Hi all,
I have a Build Flow that launches a bunch of test jobs in parallel. 
 I'd like to have the jobs communicate over the network.  Is there a way 
for one of the jobs to get the list of hostnames of the machines where 
other jobs are running?  (Is there a tool other than Build Flow that is 
better for this type of scenario?)

Thanks,
Adam


-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4f3409f5-2f77-484c-9fff-ff0176dbfc2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build flow plugin serialization

2015-06-24 Thread jan_lut

update:

Diving into stack trace has revealed the suspision that the line

myDSL.build.setDisplayName(params["PARAMETER"]) 

Caused the issue. The exact same syntax used in other jobs worked fine and
continued to work fine after the updates (or maybe just a coincidence?), but
for some reason refused to work in this particular job. It is worth being
mentioned that even job configs are relatively similar. Just out of pure
curiosity would be interesting what can cause this behavior. Anyone has got
an idea?

//Jan



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Build-flow-plugin-serialization-tp4756393p4756402.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1434723468894-4756402.post%40n4.nabble.com.
For more options, visit https://groups.google.com/d/optout.

Build flow plugin serialization

2015-06-24 Thread jan_lut

Hi,

After upgrading  Build Flow Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin>   from 0.14
to 0.18 
and installing  Claim Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin>   I'm getting an
error when running fairly simple build flow dsl script:

import static hudson.model.Result.FAILURE
import static hudson.model.Result.SUCCESS

class test_trigger_arm_stub {

  def myDSL;

  def do_test_trigger(dsl, params) {
out.println "do_test_trigger started"
myDSL = dsl

myDSL.build.setDisplayName(params["PARAMETER"])

myDSL.retry 2, { myDSL.build("test",
  PARAMETER: params["PARAMETER"])}

out.println "do_test_trigger done"
  }
}


Any ideas what went wrong here? Downgrading the build flow plugin from 0.18
to 0.17 and then 0.14 didn't resolve the issue. Also, other dsl scripts seem
to execute just fine. Only this job fails. Jenkins core is 1580.3 and it
looks to be ok for these plugins.

ERROR: Failed to run DSL Script java.lang.RuntimeException: Failed to
serialize hudson.model.Actionable#actions for class
com.cloudbees.plugins.flow.FlowRun  at
hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214)
 
at
hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182)
 
at
com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138)
 
at
hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167)
 
at
hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108)
 
at
com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
 
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
 
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)
 
at
com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) 
at
com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37)
 
at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026)  at
com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at
com.thoughtworks.xstream.XStream.toXML(XStream.java:988)at
hudson.XmlFile.write(XmlFile.java:178)  at
hudson.model.Run.save(Run.java:1915)at
hudson.model.Run.setDisplayName(Run.java:782)   at
hudson.model.Run$setDisplayName.call(Unknown Source)at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
 
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
 
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
 
at
test_trigger_arm_stub.do_test_trigger_arm_stub(test_trigger_yb_arm_stub.groovy:13)
 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 
at java.lang.reflect.Method.invoke(Method.java:606) at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at
org.codehaus.groovy.runtime.metaclass.MixinInstanceMetaMethod.invoke(MixinInstanceMetaMethod.java:53)
 
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)   at
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1079) at
groovy.lang.ExpandoMetaClass.invokeMethod(ExpandoMetaClass.java:1106)   at
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)  at
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:723)  at
com.cloudbees.plugins.flow.FlowDelegate.invokeMethod(FlowDSL.groovy)at
hudson.util.spring.ClosureScript.invokeMethod(ClosureScript.java:83)at
org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:72)
 
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
 
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
 
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
 
at Script1.run(Script1.groovy:3)at Script1$run.call(Unknown Source) 
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
 
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
 
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
 
at com.cloudbees.plugins.flow.FlowDSL.executeFlowScript(FlowDSL.groovy:84) 
at
com.cloudbees.plugins.flow.FlowRun$FlyweightTaskRunnerImpl.run(FlowRun.java:219)
 
at hudson.model.Run.execute(Run.java:1745)  at
com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155)at
hudson.model.ResourceController.execute(ResourceContr

[Build-Flow-Plugin] Parallel & Join operation

2015-06-11 Thread ramesh v r




Hello All,
 I am trying to use Jenkins build flow plugin to create below build chain.


<https://lh3.googleusercontent.com/-RiusPDtzJP8/VXlWpPCLBMI/ANA/3_G4K6MyLG0/s1600/Presentation1.png>


I have used below DSL to achieve up to build D. 
How to specify that Build E should start only after both Build D & Build C 
are completed?

// Declare all Build Results
def Build_A_Result
def Build_B_Result
def Build_C_Result
def Build_D_Result
def Build_E_Result

// Declare the build calls
def Build_A_Flow= { Build_A_Result= ignore(UNSTABLE) { build( 'Build_A' ) } 
}
def Build_B_Flow= { Build_B_Result= ignore(UNSTABLE) { build( 'Build_B' ) } 
}
def Build_C_Flow= { Build_C_Result= ignore(UNSTABLE) { build( 'Build_C' ) } 
}
def Build_D_Flow= { Build_D_Result= ignore(UNSTABLE) { build( 'Build_D' ) } 
}
def Build_E_Flow= { Build_E_Result= ignore(UNSTABLE) { build( 'Build_E' ) } 
}

//Start the process flow
def BuildBDFlow= {
[   Build_B_Flow,
Build_D_Flow
].each { it() }
}

def BuildABCFlow= {
[Build_A_Flow,
{ parallel(BuildBDFlow, Build_C_Flow) }
].each { it() }
}

[ BuildABCFlow ].each { it() }




-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/09279607-c353-4d58-b3a3-dc56ddd92671%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Build-Flow-Plugin] Parallel & Join operation

2015-06-11 Thread ramesh v r

Hello All,

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2cc02884-6387-43f8-8a13-6da9dbbd323a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

"hipchat" Plugin + "build-flow-plugin" Plugin = No notifications

2015-05-05 Thread Stephen Melrose

Hi all,

I'm trying to get HipChat notifications working for our Jenkins server, but 
I'm sadly running into issues.

I've added the config for HipChat into Jenkins' "Configure System" and hit 
"Test configuration", and everything works.

I've added the post build notification to one of our "normal" jobs and it's 
working as expected. I've then added it to one of our "build flow" jobs, 
which the vast majority of our main jobs are, and they're not working.

I've no idea whether this is hipchat or build-flow-plugin specific, but 
I've tried multiple permutations with the settings, and nothing is working. 
Everything else does.

Any ideas?

Jenkins Version: 1.612
hipchat Version: 0.1.9
build-flow-plugin Version: 0.17

Thanks

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c4f9462d-d697-4b73-b090-b60898a5b489%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Build Flow Plugin - Dynamic Job Invocation

2015-04-22 Thread Zile Rehman

I am trying to use the Build Flow Plugin 
(https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin) to 
dynamically define a parallel build job.

In my main script, I am dynamically defining a playCompBuilderList. Then I 
iterate through through the list and trigger the build for each item, as 
shown below.. My question is, how do I wrap it up in parallel statement to 
trigger the builds in parallel?


playCompBuilderList.each {
it.each {
comp, map -> build('play_comp_builder',
COMP: map['comp'],
COMP_TAG: map['comp_tag'],
CORUS_TAG   : map['corus_tag'],
DRAGONBALL_TAG  : map['dragonball_tag'],
PLAY_VERSION: map['play_version'])
}
}

This is a sample playCompBuilderList ==> [
{
"athena": {
"comp": "athena",
"comp_tag": "develop",
"corus_tag": "develop",
"dragonball_tag": "master",
"play_version": "2.3.6"
}
},
{
"atlas": {
"comp": "atlas",
"comp_tag": "develop",
"corus_tag": "develop",
"dragonball_tag": "master",
"play_version": "2.3.6"
}
}
]




I tried something like this but didn’t work:

*parallel (*
  playCompBuilderList.each {
it.each {
comp, map -> build('play_comp_builder',
COMP: map['comp'],
COMP_TAG: map['comp_tag'],
CORUS_TAG   : map['corus_tag'],
DRAGONBALL_TAG  : map['dragonball_tag'],
PLAY_VERSION: map['play_version'])
}
  }
*)*

Please help! Thanks.

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/443b39af-a82b-42f1-86d8-e256c6450d4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Build flow plugin] Cannot load balance multiple workflows

2015-03-09 Thread Ty Satrang

I think you must be right, my solution was to stop caring where the flow 
runs, and focus on an alternative method of retrieving the report/log data. 
I used the Build Flow Toolbox which lets you copy files with the flow:
job = build('downstream job')
toolbox.copyFiles(job.workspace, build.workspace)
//Unrelated but also useful:
out.println job.build.log



On Sunday, March 8, 2015 at 9:03:30 AM UTC-7, stefan thomasson wrote:
>
> Hi,
> If i understood your description, i am wondering if this Isn't the 
> expected behaviour for buildflow as it is a "fly weight" job and therefore 
> do not consume any executors?
>
> 5 mar 2015 kl. 23:39 skrev Ty Satrang >:
>
> I am not sure how you want to receive that, but here is a gist of the 
> config that will reproduce the issue. 
> Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235
> Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160
>
>
> On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote:
>>
>>  Can you provide a simple example of your main buildflow job?
>>
>>  
>>
>> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
>> Behalf Of *Ty Satrang
>> *Sent:* Thursday, March 05, 2015 5:12 PM
>> *To:* jenkins...@googlegroups.com
>> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>>
>>  
>>  
>> Thank you, I did see this copy pasta in another thread, and I did try 
>> changing the scheduling strategy with a plug-in. It seems that this 
>> particular problem is somewhat exclusive to the Build Flow plugin. It 
>> doesn't just queue jobs up, as you can see in the image link, it runs the 
>> flow jobs all at once on a single node.
>>  
>>
>> On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
>>  
>> Maybe I misunderstand your problem. Let’s keep it simple.
>>
>>  
>>
>> The reason the multiple runs of your build flow job run on the same node 
>> is because, when selecting a node, it tries to run it one the same node it 
>> previously ran on (#2 in the Strategy below). If your nodes had just 1 
>> executor defined, then any consecutive runs would run on different nodes. 
>> But with 8 executors, it just runs it there.
>>
>>  
>>
>> *Scheduling strategy*
>>
>> Some slaves are faster, while others are slow. Some slaves are closer 
>> (network wise) to a master, others are far away. So doing a good build 
>> distribution is a challenge. Currently, Jenkins employs the following 
>> strategy:
>>
>>1. If a project is configured to stick to one computer, that's always 
>>honored.
>>2. Jenkins tries to build a project on the same computer that it was 
>>previously built.
>>3. Jenkins tries to move long builds to slaves, because the amount of 
>>network interaction between a master and a slave tends to be logarithmic 
>> to 
>>the duration of a build (IOW, even if project A takes twice as long to 
>>build as project B, it won't require double network transfer.) So this 
>>strategy reduces the network overhead.
>>
>>  If you have interesting ideas (or better yet, implementations), please 
>> let me know.
>>
>>  
>>
>> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
>> Behalf Of *Ty Satrang
>> *Sent:* Thursday, March 05, 2015 1:52 PM
>> *To:* jenkins...@googlegroups.com
>> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>>
>>  
>>  
>> "if you have a label assigned to many slaves, each with one executor, it 
>> will do what you want"
>> My slaves do all share the same label and I tried to "Restrict where 
>> this project can be run" and I get the same behavior.
>>
>> "One way to do what you want is to have each “archive” whatever files 
>> you want which puts them onto the Jenkins server and then use “Copy 
>> artifacts from another project”"
>>  
>> I suppose this could work, but does it copy the files to the workspace or 
>> does it just archive them? I am using a plugin to publish reports from the 
>> workspace.
>>  
>>  
>>  
>>
>> On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
>>  
>> Its strategy is to try to use the same node it last built on. If you have 
>> available executors, it will use one. if you have a label assigned to many 
>> slaves, each with one executor, it will do what you want.
>>
>>  
>>
>> One way to do what y

Re: [Build flow plugin] Cannot load balance multiple workflows

2015-03-08 Thread Stefan Thomasson

Hi,
If i understood your description, i am wondering if this Isn't the expected 
behaviour for buildflow as it is a "fly weight" job and therefore do not 
consume any executors?

> 5 mar 2015 kl. 23:39 skrev Ty Satrang :
> 
> I am not sure how you want to receive that, but here is a gist of the config 
> that will reproduce the issue. 
> Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235
> Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160
> 
> 
>> On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote:
>> Can you provide a simple example of your main buildflow job?
>> 
>>  
>> 
>> From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On 
>> Behalf Of Ty Satrang
>> Sent: Thursday, March 05, 2015 5:12 PM
>> To: jenkins...@googlegroups.com
>> Subject: Re: [Build flow plugin] Cannot load balance multiple workflows
>> 
>>  
>> 
>> Thank you, I did see this copy pasta in another thread, and I did try 
>> changing the scheduling strategy with a plug-in. It seems that this 
>> particular problem is somewhat exclusive to the Build Flow plugin. It 
>> doesn't just queue jobs up, as you can see in the image link, it runs the 
>> flow jobs all at once on a single node.
>> 
>> 
>> On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
>> 
>> Maybe I misunderstand your problem. Let’s keep it simple.
>> 
>>  
>> 
>> The reason the multiple runs of your build flow job run on the same node is 
>> because, when selecting a node, it tries to run it one the same node it 
>> previously ran on (#2 in the Strategy below). If your nodes had just 1 
>> executor defined, then any consecutive runs would run on different nodes. 
>> But with 8 executors, it just runs it there.
>> 
>>  
>> 
>> Scheduling strategy
>> 
>> Some slaves are faster, while others are slow. Some slaves are closer 
>> (network wise) to a master, others are far away. So doing a good build 
>> distribution is a challenge. Currently, Jenkins employs the following 
>> strategy:
>> 
>> If a project is configured to stick to one computer, that's always honored.
>> Jenkins tries to build a project on the same computer that it was previously 
>> built.
>> Jenkins tries to move long builds to slaves, because the amount of network 
>> interaction between a master and a slave tends to be logarithmic to the 
>> duration of a build (IOW, even if project A takes twice as long to build as 
>> project B, it won't require double network transfer.) So this strategy 
>> reduces the network overhead.
>> If you have interesting ideas (or better yet, implementations), please let 
>> me know.
>> 
>>  
>> 
>> From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On 
>> Behalf Of Ty Satrang
>> Sent: Thursday, March 05, 2015 1:52 PM
>> To: jenkins...@googlegroups.com
>> Subject: Re: [Build flow plugin] Cannot load balance multiple workflows
>> 
>>  
>> 
>> "if you have a label assigned to many slaves, each with one executor, it 
>> will do what you want"
>> My slaves do all share the same label and I tried to "Restrict where this 
>> project can be run" and I get the same behavior.
>> 
>> "One way to do what you want is to have each “archive” whatever files you 
>> want which puts them onto the Jenkins server and then use “Copy artifacts 
>> from another project”"
>> 
>> I suppose this could work, but does it copy the files to the workspace or 
>> does it just archive them? I am using a plugin to publish reports from the 
>> workspace.
>> 
>>  
>> 
>> 
>> On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
>> 
>> Its strategy is to try to use the same node it last built on. If you have 
>> available executors, it will use one. if you have a label assigned to many 
>> slaves, each with one executor, it will do what you want.
>> 
>>  
>> 
>> One way to do what you want is to have each “archive” whatever files you 
>> want which puts them onto the Jenkins server and then use “Copy artifacts 
>> from another project”
>> 
>>  
>> 
>> From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On 
>> Behalf Of Ty Satrang
>> Sent: Thursday, March 05, 2015 3:50 AM
>> To: jenkins...@googlegroups.com
>> Subject: [Build flow plugin] Cannot load balance multiple workflows
>> 
>>  
>> 
>> http://i.imgur.com/VEZ1Erc.png
>

Re: [Build flow plugin] Cannot load balance multiple workflows

I am using Jenkins to run tests for several teams, and I would like to be 
able to run tests concurrently rather than serially. I have a master job 
that takes parameters (team, tests, code to pull) that I pass using a build 
flow. I use Jenkins so that I can have this happen on demand or on a 
schedule. It appears I may be going about this the wrong way. Do you have 
any suggestions?

On Thursday, March 5, 2015 at 2:54:13 PM UTC-8, rginga wrote:
>
>  Ok, so your upper job Sample Flow does 
>
>  
>
> Build(Sample downstream job, node: name-name)
>
>  
>
> And Sample downstream job does a find grep command
>
>  
>
> And your image represents starting Sample flow job 9 times. Since there 
> are 9 available executors on dvm-qa5, all 9 Sample flow jobs start. I 
> expect that 8 of them pend waiting on Sample downstream job to finish 
> (unless you checked “Run concurrent”)
>
>  
>
> And I think you wanted those 9 jobs to be distributed among other nodes in 
> your group like dvm-qa2 and 1? 
>
>  
>
> I think that I don’t know how to get it to do what you want but I would 
> not call it a “problem”. This strategy “Jenkins tries to build a project on 
> the same computer that it was previously built.” Is called “affinity” and 
> it helps a great deal when jobs are pulling source code and/or building. It 
> can greatly speed up the process.
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 5:39 PM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> I am not sure how you want to receive that, but here is a gist of the 
> config that will reproduce the issue. 
>  
> Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235
> Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160
>  
>  
>  
>
> On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote:
>  
> Can you provide a simple example of your main buildflow job?
>
>  
>
> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
> Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 5:12 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> Thank you, I did see this copy pasta in another thread, and I did try 
> changing the scheduling strategy with a plug-in. It seems that this 
> particular problem is somewhat exclusive to the Build Flow plugin. It 
> doesn't just queue jobs up, as you can see in the image link, it runs the 
> flow jobs all at once on a single node.
>  
>
> On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
>  
> Maybe I misunderstand your problem. Let’s keep it simple.
>
>  
>
> The reason the multiple runs of your build flow job run on the same node 
> is because, when selecting a node, it tries to run it one the same node it 
> previously ran on (#2 in the Strategy below). If your nodes had just 1 
> executor defined, then any consecutive runs would run on different nodes. 
> But with 8 executors, it just runs it there.
>
>  
>
> *Scheduling strategy*
>
> Some slaves are faster, while others are slow. Some slaves are closer 
> (network wise) to a master, others are far away. So doing a good build 
> distribution is a challenge. Currently, Jenkins employs the following 
> strategy:
>
>1. If a project is configured to stick to one computer, that's always 
>honored.
>2. Jenkins tries to build a project on the same computer that it was 
>previously built.
>3. Jenkins tries to move long builds to slaves, because the amount of 
>network interaction between a master and a slave tends to be logarithmic 
> to 
>the duration of a build (IOW, even if project A takes twice as long to 
>build as project B, it won't require double network transfer.) So this 
>strategy reduces the network overhead.
>
>  If you have interesting ideas (or better yet, implementations), please 
> let me know.
>
>  
>
> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
> Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 1:52 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> "if you have a label assigned to many slaves, each with one executor, it 
> will do what you want"
> My slaves do all share the same label and I tried to "Restrict where this 
> project can be run" and I get the same behavior.
>
> "One way to do what you want i

RE: [Build flow plugin] Cannot load balance multiple workflows

Ok, so your upper job Sample Flow does

Build(Sample downstream job, node: name-name)

And Sample downstream job does a find grep command

And your image represents starting Sample flow job 9 times. Since there are 9 
available executors on dvm-qa5, all 9 Sample flow jobs start. I expect that 8 
of them pend waiting on Sample downstream job to finish (unless you checked 
“Run concurrent”)

And I think you wanted those 9 jobs to be distributed among other nodes in your 
group like dvm-qa2 and 1?

I think that I don’t know how to get it to do what you want but I would not 
call it a “problem”. This strategy “Jenkins tries to build a project on the 
same computer that it was previously built.” Is called “affinity” and it helps 
a great deal when jobs are pulling source code and/or building. It can greatly 
speed up the process.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 5:39 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: [Build flow plugin] Cannot load balance multiple workflows

I am not sure how you want to receive that, but here is a gist of the config 
that will reproduce the issue.
Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235
Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160


On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote:
Can you provide a simple example of your main buildflow job?

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 5:12 PM
To: jenkins...@googlegroups.com
Subject: Re: [Build flow plugin] Cannot load balance multiple workflows

Thank you, I did see this copy pasta in another thread, and I did try changing 
the scheduling strategy with a plug-in. It seems that this particular problem 
is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, 
as you can see in the image link, it runs the flow jobs all at once on a single 
node.

On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
Maybe I misunderstand your problem. Let’s keep it simple.

The reason the multiple runs of your build flow job run on the same node is 
because, when selecting a node, it tries to run it one the same node it 
previously ran on (#2 in the Strategy below). If your nodes had just 1 executor 
defined, then any consecutive runs would run on different nodes. But with 8 
executors, it just runs it there.

Scheduling strategy
Some slaves are faster, while others are slow. Some slaves are closer (network 
wise) to a master, others are far away. So doing a good build distribution is a 
challenge. Currently, Jenkins employs the following strategy:

  1.  If a project is configured to stick to one computer, that's always 
honored.
  2.  Jenkins tries to build a project on the same computer that it was 
previously built.
  3.  Jenkins tries to move long builds to slaves, because the amount of 
network interaction between a master and a slave tends to be logarithmic to the 
duration of a build (IOW, even if project A takes twice as long to build as 
project B, it won't require double network transfer.) So this strategy reduces 
the network overhead.
If you have interesting ideas (or better yet, implementations), please let me 
know.

From: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com> 
[mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 1:52 PM
To: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>
Subject: Re: [Build flow plugin] Cannot load balance multiple workflows

"if you have a label assigned to many slaves, each with one executor, it will 
do what you want"
My slaves do all share the same label and I tried to "Restrict where this 
project can be run" and I get the same behavior.

"One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”"
I suppose this could work, but does it copy the files to the workspace or does 
it just archive them? I am using a plugin to publish reports from the workspace.


On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
Its strategy is to try to use the same node it last built on. If you have 
available executors, it will use one. if you have a label assigned to many 
slaves, each with one executor, it will do what you want.

One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”

From: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com> 
[mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 3:50 AM
To: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>
Subject: [Build flow plugin] Cannot load balanc

Re: [Build flow plugin] Cannot load balance multiple workflows

I am not sure how you want to receive that, but here is a gist of the 
config that will reproduce the issue. 
Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235
Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160


On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote:
>
>  Can you provide a simple example of your main buildflow job?
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 5:12 PM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> Thank you, I did see this copy pasta in another thread, and I did try 
> changing the scheduling strategy with a plug-in. It seems that this 
> particular problem is somewhat exclusive to the Build Flow plugin. It 
> doesn't just queue jobs up, as you can see in the image link, it runs the 
> flow jobs all at once on a single node.
>  
>
> On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
>  
> Maybe I misunderstand your problem. Let’s keep it simple.
>
>  
>
> The reason the multiple runs of your build flow job run on the same node 
> is because, when selecting a node, it tries to run it one the same node it 
> previously ran on (#2 in the Strategy below). If your nodes had just 1 
> executor defined, then any consecutive runs would run on different nodes. 
> But with 8 executors, it just runs it there.
>
>  
>
> *Scheduling strategy*
>
> Some slaves are faster, while others are slow. Some slaves are closer 
> (network wise) to a master, others are far away. So doing a good build 
> distribution is a challenge. Currently, Jenkins employs the following 
> strategy:
>
>1. If a project is configured to stick to one computer, that's always 
>honored.
>2. Jenkins tries to build a project on the same computer that it was 
>previously built.
>3. Jenkins tries to move long builds to slaves, because the amount of 
>network interaction between a master and a slave tends to be logarithmic 
> to 
>the duration of a build (IOW, even if project A takes twice as long to 
>build as project B, it won't require double network transfer.) So this 
>strategy reduces the network overhead.
>
>  If you have interesting ideas (or better yet, implementations), please 
> let me know.
>
>  
>
> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
> Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 1:52 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> "if you have a label assigned to many slaves, each with one executor, it 
> will do what you want"
> My slaves do all share the same label and I tried to "Restrict where this 
> project can be run" and I get the same behavior.
>
> "One way to do what you want is to have each “archive” whatever files you 
> want which puts them onto the Jenkins server and then use “Copy artifacts 
> from another project”"
>  
> I suppose this could work, but does it copy the files to the workspace or 
> does it just archive them? I am using a plugin to publish reports from the 
> workspace.
>  
>  
>  
>
> On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
>  
> Its strategy is to try to use the same node it last built on. If you have 
> available executors, it will use one. if you have a label assigned to many 
> slaves, each with one executor, it will do what you want.
>
>  
>
> One way to do what you want is to have each “archive” whatever files you 
> want which puts them onto the Jenkins server and then use “Copy artifacts 
> from another project”
>
>  
>
> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
> Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 3:50 AM
> *To:* jenkins...@googlegroups.com
> *Subject:* [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> http://i.imgur.com/VEZ1Erc.png
>  
>  
>  
> For some reason my flow jobs like to all run on a single node instead of 
> choosing an idle node.
>  
>  
>  
> This is a problem for me because I am using the Node and Label parameter 
> plugin 
> <https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin> to 
> run the jobs on the same VM as the flow job so I can copy the reports and 
> logs to the parent workspace for publishing.
>  
>  
>  
> I tried using the Least Load plugin 
> <http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin>, but I get

RE: [Build flow plugin] Cannot load balance multiple workflows

Can you provide a simple example of your main buildflow job?

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 5:12 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: [Build flow plugin] Cannot load balance multiple workflows

Thank you, I did see this copy pasta in another thread, and I did try changing 
the scheduling strategy with a plug-in. It seems that this particular problem 
is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, 
as you can see in the image link, it runs the flow jobs all at once on a single 
node.

On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
Maybe I misunderstand your problem. Let’s keep it simple.

The reason the multiple runs of your build flow job run on the same node is 
because, when selecting a node, it tries to run it one the same node it 
previously ran on (#2 in the Strategy below). If your nodes had just 1 executor 
defined, then any consecutive runs would run on different nodes. But with 8 
executors, it just runs it there.

Scheduling strategy
Some slaves are faster, while others are slow. Some slaves are closer (network 
wise) to a master, others are far away. So doing a good build distribution is a 
challenge. Currently, Jenkins employs the following strategy:

  1.  If a project is configured to stick to one computer, that's always 
honored.
  2.  Jenkins tries to build a project on the same computer that it was 
previously built.
  3.  Jenkins tries to move long builds to slaves, because the amount of 
network interaction between a master and a slave tends to be logarithmic to the 
duration of a build (IOW, even if project A takes twice as long to build as 
project B, it won't require double network transfer.) So this strategy reduces 
the network overhead.
If you have interesting ideas (or better yet, implementations), please let me 
know.

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 1:52 PM
To: jenkins...@googlegroups.com
Subject: Re: [Build flow plugin] Cannot load balance multiple workflows

"if you have a label assigned to many slaves, each with one executor, it will 
do what you want"
My slaves do all share the same label and I tried to "Restrict where this 
project can be run" and I get the same behavior.

"One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”"
I suppose this could work, but does it copy the files to the workspace or does 
it just archive them? I am using a plugin to publish reports from the workspace.

On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
Its strategy is to try to use the same node it last built on. If you have 
available executors, it will use one. if you have a label assigned to many 
slaves, each with one executor, it will do what you want.

One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”

From: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com> 
[mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 3:50 AM
To: jenkins...@googlegroups.com<mailto:jenkins...@googlegroups.com>
Subject: [Build flow plugin] Cannot load balance multiple workflows

http://i.imgur.com/VEZ1Erc.png

For some reason my flow jobs like to all run on a single node instead of 
choosing an idle node.

This is a problem for me because I am using the Node and Label parameter 
plugin<https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin> 
to run the jobs on the same VM as the flow job so I can copy the reports and 
logs to the parent workspace for publishing.

I tried using the Least Load 
plugin<http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin>, but I get 
the same behavior.

I also tried the Throttle Concurrent Builds 
Plug-in<http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin>
 to restrict the jobs per node to 1, to no effect.

I am just realizing this now but, maybe it would be easier to get the files to 
the parent workspace another way and let the flow jobs all run on whatever 
single node they want. (maybe? 
https://github.com/dnozay/build-flow-toolbox-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 email 
to jenkinsci-use...@googlegroups.com<mailto:jenkinsci-use...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com<https://groups.google.com/d/

Re: [Build flow plugin] Cannot load balance multiple workflows

Thank you, I did see this copy pasta in another thread, and I did try 
changing the scheduling strategy with a plug-in. It seems that this 
particular problem is somewhat exclusive to the Build Flow plugin. It 
doesn't just queue jobs up, as you can see in the image link, it runs the 
flow jobs all at once on a single node.

On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote:
>
>  Maybe I misunderstand your problem. Let’s keep it simple.
>
>  
>
> The reason the multiple runs of your build flow job run on the same node 
> is because, when selecting a node, it tries to run it one the same node it 
> previously ran on (#2 in the Strategy below). If your nodes had just 1 
> executor defined, then any consecutive runs would run on different nodes. 
> But with 8 executors, it just runs it there.
>
>  
>
> *Scheduling strategy*
>
> Some slaves are faster, while others are slow. Some slaves are closer 
> (network wise) to a master, others are far away. So doing a good build 
> distribution is a challenge. Currently, Jenkins employs the following 
> strategy:
>
>1. If a project is configured to stick to one computer, that's always 
>honored.
>2. Jenkins tries to build a project on the same computer that it was 
>previously built.
>3. Jenkins tries to move long builds to slaves, because the amount of 
>network interaction between a master and a slave tends to be logarithmic 
> to 
>the duration of a build (IOW, even if project A takes twice as long to 
>build as project B, it won't require double network transfer.) So this 
>strategy reduces the network overhead.
>
>  If you have interesting ideas (or better yet, implementations), please 
> let me know.
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 1:52 PM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> "if you have a label assigned to many slaves, each with one executor, it 
> will do what you want"
> My slaves do all share the same label and I tried to "Restrict where this 
> project can be run" and I get the same behavior.
>
> "One way to do what you want is to have each “archive” whatever files you 
> want which puts them onto the Jenkins server and then use “Copy artifacts 
> from another project”"
>  
> I suppose this could work, but does it copy the files to the workspace or 
> does it just archive them? I am using a plugin to publish reports from the 
> workspace.
>  
>  
>  
>
> On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
>  
> Its strategy is to try to use the same node it last built on. If you have 
> available executors, it will use one. if you have a label assigned to many 
> slaves, each with one executor, it will do what you want.
>
>  
>
> One way to do what you want is to have each “archive” whatever files you 
> want which puts them onto the Jenkins server and then use “Copy artifacts 
> from another project”
>
>  
>
> *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On 
> Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 3:50 AM
> *To:* jenkins...@googlegroups.com
> *Subject:* [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> http://i.imgur.com/VEZ1Erc.png
>  
>  
>  
> For some reason my flow jobs like to all run on a single node instead of 
> choosing an idle node.
>  
>  
>  
> This is a problem for me because I am using the Node and Label parameter 
> plugin 
> <https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin> to 
> run the jobs on the same VM as the flow job so I can copy the reports and 
> logs to the parent workspace for publishing.
>  
>  
>  
> I tried using the Least Load plugin 
> <http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin>, but I get 
> the same behavior.
>   
>  
>  
> I also tried the Throttle Concurrent Builds Plug-in 
> <http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin>
>  to 
> restrict the jobs per node to 1, to no effect.
>  
>  
>  
> I am just realizing this now but, maybe it would be easier to get the 
> files to the parent workspace another way and let the flow jobs all run on 
> whatever single node they want. (maybe? 
> https://github.com/dnozay/build-flow-toolbox-plugin )
>  
>  
>   
>  
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubs

RE: [Build flow plugin] Cannot load balance multiple workflows

Maybe I misunderstand your problem. Let’s keep it simple.

The reason the multiple runs of your build flow job run on the same node is 
because, when selecting a node, it tries to run it one the same node it 
previously ran on (#2 in the Strategy below). If your nodes had just 1 executor 
defined, then any consecutive runs would run on different nodes. But with 8 
executors, it just runs it there.

Scheduling strategy
Some slaves are faster, while others are slow. Some slaves are closer (network 
wise) to a master, others are far away. So doing a good build distribution is a 
challenge. Currently, Jenkins employs the following strategy:

  1.  If a project is configured to stick to one computer, that's always 
honored.
  2.  Jenkins tries to build a project on the same computer that it was 
previously built.
  3.  Jenkins tries to move long builds to slaves, because the amount of 
network interaction between a master and a slave tends to be logarithmic to the 
duration of a build (IOW, even if project A takes twice as long to build as 
project B, it won't require double network transfer.) So this strategy reduces 
the network overhead.
If you have interesting ideas (or better yet, implementations), please let me 
know.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 1:52 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: [Build flow plugin] Cannot load balance multiple workflows

"if you have a label assigned to many slaves, each with one executor, it will 
do what you want"
My slaves do all share the same label and I tried to "Restrict where this 
project can be run" and I get the same behavior.

"One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”"
I suppose this could work, but does it copy the files to the workspace or does 
it just archive them? I am using a plugin to publish reports from the workspace.


On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
Its strategy is to try to use the same node it last built on. If you have 
available executors, it will use one. if you have a label assigned to many 
slaves, each with one executor, it will do what you want.

One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”

From: jenkins...@googlegroups.com 
[mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 3:50 AM
To: jenkins...@googlegroups.com
Subject: [Build flow plugin] Cannot load balance multiple workflows

http://i.imgur.com/VEZ1Erc.png

For some reason my flow jobs like to all run on a single node instead of 
choosing an idle node.

This is a problem for me because I am using the Node and Label parameter 
plugin<https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin> 
to run the jobs on the same VM as the flow job so I can copy the reports and 
logs to the parent workspace for publishing.

I tried using the Least Load 
plugin<http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin>, but I get 
the same behavior.

I also tried the Throttle Concurrent Builds 
Plug-in<http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin>
 to restrict the jobs per node to 1, to no effect.

I am just realizing this now but, maybe it would be easier to get the files to 
the parent workspace another way and let the flow jobs all run on whatever 
single node they want. (maybe? 
https://github.com/dnozay/build-flow-toolbox-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 email 
to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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 email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0a9cb8a5-d3ef-4f02-8506-0e4b0a986493%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/0a9cb8a5-d3ef-4f02-8506-0e4b0a986493%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.googl

Re: [Build flow plugin] Cannot load balance multiple workflows

"if you have a label assigned to many slaves, each with one executor, it 
will do what you want"
My slaves do all share the same label and I tried to "Restrict where this 
project can be run" and I get the same behavior.

"One way to do what you want is to have each “archive” whatever files you 
want which puts them onto the Jenkins server and then use “Copy artifacts 
from another project”"
I suppose this could work, but does it copy the files to the workspace or 
does it just archive them? I am using a plugin to publish reports from the 
workspace.


On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote:
>
>  Its strategy is to try to use the same node it last built on. If you 
> have available executors, it will use one. if you have a label assigned to 
> many slaves, each with one executor, it will do what you want.
>
>  
>
> One way to do what you want is to have each “archive” whatever files you 
> want which puts them onto the Jenkins server and then use “Copy artifacts 
> from another project”
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Ty Satrang
> *Sent:* Thursday, March 05, 2015 3:50 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* [Build flow plugin] Cannot load balance multiple workflows
>
>  
>  
> http://i.imgur.com/VEZ1Erc.png
>  
>  
>  
> For some reason my flow jobs like to all run on a single node instead of 
> choosing an idle node.
>  
>  
>  
> This is a problem for me because I am using the Node and Label parameter 
> plugin 
> <https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin> to 
> run the jobs on the same VM as the flow job so I can copy the reports and 
> logs to the parent workspace for publishing.
>  
>  
>  
> I tried using the Least Load plugin 
> <http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin>, but I get 
> the same behavior.
>   
>  
>  
> I also tried the Throttle Concurrent Builds Plug-in 
> <http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin>
>  to 
> restrict the jobs per node to 1, to no effect.
>  
>  
>  
> I am just realizing this now but, maybe it would be easier to get the 
> files to the parent workspace another way and let the flow jobs all run on 
> whatever single node they want. (maybe? 
> https://github.com/dnozay/build-flow-toolbox-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 
> email to jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>  

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0a9cb8a5-d3ef-4f02-8506-0e4b0a986493%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [Build flow plugin] Cannot load balance multiple workflows

Its strategy is to try to use the same node it last built on. If you have 
available executors, it will use one. if you have a label assigned to many 
slaves, each with one executor, it will do what you want.

One way to do what you want is to have each “archive” whatever files you want 
which puts them onto the Jenkins server and then use “Copy artifacts from 
another project”

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang
Sent: Thursday, March 05, 2015 3:50 AM
To: jenkinsci-users@googlegroups.com
Subject: [Build flow plugin] Cannot load balance multiple workflows

http://i.imgur.com/VEZ1Erc.png

For some reason my flow jobs like to all run on a single node instead of 
choosing an idle node.

This is a problem for me because I am using the Node and Label parameter 
plugin<https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin> 
to run the jobs on the same VM as the flow job so I can copy the reports and 
logs to the parent workspace for publishing.

I tried using the Least Load 
plugin<http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin>, but I get 
the same behavior.

I also tried the Throttle Concurrent Builds 
Plug-in<http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin>
 to restrict the jobs per node to 1, to no effect.

I am just realizing this now but, maybe it would be easier to get the files to 
the parent workspace another way and let the flow jobs all run on whatever 
single node they want. (maybe? 
https://github.com/dnozay/build-flow-toolbox-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 email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

-- 
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 email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6C6EE445A6F6CE4E8A0FFB51B071A4E26E507091%40AMERMBX02.PERKINELMER.NET.
For more options, visit https://groups.google.com/d/optout.

[Build flow plugin] Cannot load balance multiple workflows