Better Bitbucket support for gitversion /output buildserver for Powershell #3833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When running gitversion in Bitbucket Pipeline in Windows Powershell environment,
gitversion.ps1file is also written, in addition to the originalgitversion.propertiesfor Bash (not changed).Related Issue
#3831
Motivation and Context
Getting the gitversion output variables into Powershell session requires now only one command:
. .\gitversion.ps1Old way was to parse
gitversion.propertiesfile:How Has This Been Tested?
Included checks to existing tests.
I have tested this manually in our Bitbucket Pipelines and I haven't found any issues.
Checklist: