Nice Video, I have a question if you can answer me, I have created a variable group named DEV and have a variable insdie DEV group is "connectionstring". In azure repo I have a file called .env, I want to store the value of a "connectionstring" variable into .env. How can I do this?
Great.. but there's no real explanation on how do set different variables for different branches. Its all set statically within the YAML itself. This was also of help, thanks!
I was able to achieve this by setting the value within our variable group as a specific branch name then using $[variables[variables['Build.SourceBranchName']]] to reference the output from our variable.
Thanks for the video.. Its really helpful. I have one requirement like in my codeway yml file I have 3 environments like Dev stg and pro. When I run the pipeline all the environments are executing one after other. But my requirement is I want to select only specific environment to run like choice parameters same as in Jenkins. Is there any way to achieve to build specific environment. Thanks in advance
Thank you for this video. I am not sure if I understand correctly how these are used. I have a keyvault linked variable group. I was trying to follow this video and the MS doc. I have a group say 'variable-group' and I have a secret in a keyvault called 'my-secret'. In the pipeline I had placed these lines and kept getting a syntax failure variables: - group: 'variable-group' -name: secret-from-kv value: $[variables.my-secret] I was however easily able to do this. variables: - group: 'variable-group' then down in the pipeline when I wanted to reference that variable I do this and it works. I thought the above code would let you tweak the naming of secrets within the pipeline but may be missing something. -script: echo $(my-secret)
thanks for saving my a$$, never thought i have to link variable group to my pipeline!
Is there a way to prompt selection of variable group upon run instead of hard coding the single variable group?
what if you have more than one variable group? That is an obvious question which you missed
Can you use single variable group across all Azure Devops project ?
Nice Video, I have a question if you can answer me, I have created a variable group named DEV and have a variable insdie DEV group is "connectionstring". In azure repo I have a file called .env, I want to store the value of a "connectionstring" variable into .env. How can I do this?
Great video mate > how to i automate this creation process and does it make sense to run it and always link it to the key vault values?
Nice video and clear explanation
Great.. but there's no real explanation on how do set different variables for different branches. Its all set statically within the YAML itself. This was also of help, thanks!
I was able to achieve this by setting the value within our variable group as a specific branch name then using $[variables[variables['Build.SourceBranchName']]] to reference the output from our variable.
If there's secret variable in group this doesn't work. Could You specify how to fix it, please?
I had the same problem when using Azure key vault
Thanks!
Thanks for the video.. Its really helpful.
I have one requirement like in my codeway yml file I have 3 environments like Dev stg and pro.
When I run the pipeline all the environments are executing one after other.
But my requirement is I want to select only specific environment to run like choice parameters same as in Jenkins.
Is there any way to achieve to build specific environment.
Thanks in advance
Can you please explain "How to add two variable groups in same stage?"
- group: 'groupA'
- group: 'groupB'
Thank you for this video. I am not sure if I understand correctly how these are used. I have a keyvault linked variable group. I was trying to follow this video and the MS doc.
I have a group say 'variable-group' and I have a secret in a keyvault called 'my-secret'. In the pipeline I had placed these lines and kept getting a syntax failure
variables:
- group: 'variable-group'
-name: secret-from-kv
value: $[variables.my-secret]
I was however easily able to do this.
variables:
- group: 'variable-group'
then down in the pipeline when I wanted to reference that variable I do this and it works. I thought the above code would let you tweak the naming of secrets within the pipeline but may be missing something.
-script:
echo $(my-secret)