The JCasC doc is here.
https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/features/secrets.adoc
It depends on whether you already have an external secret system.


On Thu, Jun 17, 2021 at 11:49 PM Anu S <[email protected]> wrote:

> Hi Liejun* Tao,*
>
> let me check on this secret management system,
> Any links to guide me on this?
>
> thanks & Regards,
> Anu
>
> On Fri, Jun 18, 2021 at 12:26 AM Liejun Tao <[email protected]>
> wrote:
>
>> I assume when you put full configurations into JCasc, you already have a
>> way to inject secrets into the config.
>> You may treat the (changeable) global variable as a secret which could be
>> changed from outside (the secret management system).
>>
>>
>> On Thu, Jun 17, 2021 at 2:51 AM Anu S <[email protected]> wrote:
>>
>>> Hi Everyone,
>>>
>>> i need one info to proceed with my work.
>>>
>>> currently the new jenkins which my team is having - entire configuration
>>> is in JCAS(jenkins configuration as code) in a yaml stored in gitlab.
>>>
>>> now for our current scenario  - we need to define, 3 jenkins global
>>> variable which will decide the job has to run or not.
>>>
>>> to define it as global variable - i can do in yaml. - the thing is - we
>>> are going to change the values every now and then.
>>>
>>> 1. either change the value in yaml everytime - this might introduce any
>>> config error. any way we can avoid doing the change in yaml by changing it
>>> manually under manage jenkins - configure system. (the concern here is -
>>> any update in yaml will reset the value back to default for the 3 variable
>>> and the manual configuration will go off)
>>>
>>> so any other way we can change the jenkins global variable value
>>> configured in JCAS? without any impact or change?
>>>
>>> Regards,
>>> Anu
>>>
>>> --
>>> 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].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/1915a5af-c73d-4882-b4a8-4c62fd514786n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/1915a5af-c73d-4882-b4a8-4c62fd514786n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> --
>> Thanks,
>> Baibai
>>
>> --
>> 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].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAMRm5jacm%2BcK2Vd_n1U0KSNKGc1Q9dTgS6FueKy9_1Gx%3DqvdiA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAMRm5jacm%2BcK2Vd_n1U0KSNKGc1Q9dTgS6FueKy9_1Gx%3DqvdiA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAE4p%3DdPzQZrCuaFzd_2LWmFu%2BSAt2zGLAiWzRbw4JEbJTpunEg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAE4p%3DdPzQZrCuaFzd_2LWmFu%2BSAt2zGLAiWzRbw4JEbJTpunEg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,
Baibai

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMRm5jZ2CyOiOCTyfCc%2BvV%3DNLJ2394XT8BNQbeExnzqwRDHZUg%40mail.gmail.com.

Reply via email to