Skip to content
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

VSTS cloud builds should set buildnumber variable #80

Closed
AArnott opened this issue Jun 24, 2016 · 1 comment
Closed

VSTS cloud builds should set buildnumber variable #80

AArnott opened this issue Jun 24, 2016 · 1 comment

Comments

@AArnott
Copy link
Collaborator

AArnott commented Jun 24, 2016

The VSTS cloud builds have a Build.BuildNumber variable, as defined here.

Although NB.GV can set the build number, the Build.BuildNumber variable remains unchanged. Consider changing it explicitly within the build as well.

@AArnott
Copy link
Collaborator Author

AArnott commented Jun 29, 2016

I confirmed that without any change, the BUILD_BUILDNUMBER environment variable does change at least by the time the next task in the VSTS build definition executes. But perhaps the issue @kirankulkarni747 and I saw is because the BUILD_BUILDNUMBER environment variable is consumed by the same build task that invoked NB.GV. If that's true, then the fix is probably to have NB.GV set the environment variable directly in addition to emitting the special ##vso instruction.

AArnott pushed a commit that referenced this issue Sep 5, 2022
Adapt to GitHub's new env and path operations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant