-
-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: CloudBuild: Include all variables #178
Comments
Isn't this a dupe of #130 which is already fixed? |
You're right. I missed it because it's not documented here:
|
clairernovotny
changed the title
CloudBuild: Include all variables
Docs: CloudBuild: Include all variables
May 18, 2018
AArnott
added a commit
that referenced
this issue
May 18, 2018
AArnott
added a commit
that referenced
this issue
Feb 8, 2023
Adopt .NET 7 SDK and NuGet central package versioning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today, the cloudbuild, set variables option sets three variables. Would it make sense to set all of them and not just those three? There's various reasons they could be useful and it'd reduce the need to call the PowerShell version directly if everything was set as an env variable.
The text was updated successfully, but these errors were encountered: