I do not think tha the build pipeline uses build flows.  Also, when I look at 
teh build flow plugin, they state that it is a POC plugin and it seems tha the 
developers are moving on and suggest the use of the workflow plugin.  It seems 
that there has to be some way to set global variables and use them without 
having to use the parameterized build plugin, as this forces me to have to 
indicate I want to run the build and the build pipeline plugin does not 
recognize this functionality (i.e. it does nto run with the default values).




On Thursday, June 5, 2014 12:28 PM, Mike Chmielewski <[email protected]> wrote:
 


I'm using the build flow plugin, which I believe is used by the build pipeline.

Basically my groovy script that orchestrates the build flow passes in some 
variables to the build calls in build flow. I don't have to define the 
parameters on the build job that I am calling with the parameters.



On Thu, Jun 5, 2014 at 10:13 AM, Eric Wood <[email protected]> wrote:

Mike:
>
>
>Thanks for the reply. I'm not sure I follow the response.  When you mention 
>Build Flows are you talking about build pipeline creating using the build 
>pipeline plugin?  Also, who are you setting the values that you pass in?
>
>
>Thanks, Eric
>
>
>
>On Wednesday, June 4, 2014 3:34 PM, Mike Chmielewski <[email protected]> 
>wrote:
> 
>
>
>For Build Flows, I have passed in arbitrary variables not defined on a job in 
>the flow, and they are picked up correctly.
>
>
>
>On Wed, Jun 4, 2014 at 12:42 PM, Eric Wood <[email protected]> wrote:
>
>I have several jenkins jobs that I want to use global variables.  The only way 
>I have seen to do this is to parameterize my build and to set a global 
>parameter string using the plugin documented here:
>>https://wiki.jenkins-ci.org/display/JENKINS/Global+Variable+String+Parameter+Plugin
>>
>>
>>
>>The issue I run into is that this forces me to run a build with parameters 
>>and prompts me to select the defaults., and the build pipeline plugin does 
>>not know anything about this and does not seem to kick off the build with the 
>>specified defaults.
>>
>>
>>It there a way for me to set up global parameters and get the build process 
>>to accept them without prompting me for a "parameterized" build?
>>
>>
>>Thansdk, Eric
>>
>> -- 
>>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 [email protected].
>>For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
>-- 
>
>Michael Chmielewski | Practice Lead, Release Engineering
>T 617.478.9368
>
>
>
>
>BULLHORN®
>
>Twitter | LinkedIn | Facebook
>
-- 
>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 [email protected].
>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 [email protected].
>For more options, visit https://groups.google.com/d/optout.
>


-- 

Michael Chmielewski | Practice Lead, Release Engineering
T 617.478.9368


BULLHORN®

Twitter | LinkedIn | Facebook

-- 
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 [email protected].
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to