Replies: 1 comment
-
|
Thanks for bringing this up, @mturczyn -- our documentation is incorrect. Azure Pipelines does not automatically map secret environment variables into steps/tasks. You have to manually map them using the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In documentation/scenarios/nuget-credentials.md it is mentioned we can use Nuget Authenticate task in Azure pipelines
But that do not work (even echoing showed it as empty). I guess that might be due to the fact that VSS_NUGET_ACCESSTOKEN is secret value.
I wonder if I am correct about my assumption, or is there something I could do better? Something I have missed?
My workaround currently is to have custom task with docker build and push commands that accepts correctly VSS_NUGET_ACCESSTOKEN secret through environment variables
Beta Was this translation helpful? Give feedback.
All reactions