Unfortunately, there is no Jenkins capability to inject environment vars at 
folder level

Thanks

-Dan

On Saturday, March 18, 2017 at 1:15:34 AM UTC-7, Stephen Connolly wrote:
>
> You could also define env vars at the folder level (as multibranch is a 
> folder) and then use conditions based on the env vars... less elegant I know
>
> On Sat 18 Mar 2017 at 07:22, Dan Tran <dan...@gmail.com <javascript:>> 
> wrote:
>
>> I have a requirement to run maven sonar:sonar against all branches. This 
>> means my Jenkinsfile must explicitly invoke sonar and can only run sonar 
>> only environment
>>
>> if jenkins pipline allows injection of a user env variable, my 
>> Jenkinsfile can react appropriately.
>>
>> However, I just found  a promising option at 
>> https://github.com/jenkinsci/workflow-multibranch-plugin/pull/59
>>
>> Thanks
>>
>> -Dan 
>>
>> On Friday, March 17, 2017 at 2:51:39 AM UTC-7, Stephen Connolly wrote:
>>
>>> Could you describe your use-case more concretely?
>>>
>>> On Fri 17 Mar 2017 at 01:44, Dan Tran <dan...@gmail.com> wrote:
>>>
>> anyone?  or this is a limitation of multibranch pipeline?
>>>>
>>>> Thanks
>>>>
>>>> -Dan
>>>>
>>>>
>>>> On Wednesday, March 15, 2017 at 5:23:04 PM UTC-7, Dan Tran wrote:
>>>>>
>>>>> Hi 
>>>>>
>>>>> My Jenkinsfile  has a boolean parameter, and I would like to enable a 
>>>>> parameter via 
>>>>>
>>>>>   - user selection
>>>>>   - ENV set at the job where my groovy will detect and flip the param
>>>>>
>>>>> However, I can't find any hook into those 2 options at top folder level
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> -D
>>>>>
>>>>> to be more concrete,  this particular job that I have must perform 
>>>>> sonar:sonar, and my jenkinsfile disable this option by default
>>>>>
>>>>> I am using declarative pipeline syntax
>>>>>
>>>> -- 
>>>> 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/e3a897e6-cc62-4a55-923f-4efe8d9e6617%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/e3a897e6-cc62-4a55-923f-4efe8d9e6617%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>>> Sent from my phone
>>>
>> -- 
>> 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 <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/ab81b9c2-c3da-437f-94b1-0ced0d52e243%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/ab81b9c2-c3da-437f-94b1-0ced0d52e243%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Sent from my phone
>

-- 
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/48bcda9f-6ceb-44ea-b655-02796976b067%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to