You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with "overrideConfig" param update-build-number=false, the task still updates the pipeline name
........GitVersion executed successfullyAsync Command Start: Update Build NumberUpdate build number to 1.1.1 for build 1416Async Command End: Update Build NumberFinishing: execute gitversion
........
in .gitversion.yaml the parameter update-build-number: true is specified, but changing it also has no effect, the task still updates the name regardless of this
What is expected?
This should not change the build number
Steps to Reproduce
Use the following pipeline structure for Azure DevOps Service
Prerequisites
GitVersion package
GitVersion.Tool, gittools/actions
GitVersion version
6.0.5
Operating system
Linux
What are you seeing?
When starting a task in CI (Azure DevOps Service)
with "overrideConfig" param
update-build-number=false
, the task still updates the pipeline namein
.gitversion.yaml
the parameterupdate-build-number: true
is specified, but changing it also has no effect, the task still updates the name regardless of thisWhat is expected?
This should not change the build number
Steps to Reproduce
Use the following pipeline structure for Azure DevOps Service
configuration file
.gitversion.yaml
RepositoryFixture Test
No response
Output log or link to your CI build (if appropriate).
The text was updated successfully, but these errors were encountered: