[X] I have searched issues to ensure it has not already been reported
GitVersion package
AzureDevops task
What are you seeing?
We upgraded from task v0/GitVersion v5 to task v3/GitVersion v6. We made no changes to your gitversion config file that is used by all our builds. We didn't realize that the config format had changed. When the execute task ran all we got in the output was a "command failed" message. There was no indication why it failed or what was wrong.
The only way we diagnosed this issue was by cloning the repo locally, dropping in the config file that is used and then running the same command line that the build server runs. This revealed that our config file had entries that are no longer supported.
What is expected?
If an error occurs while attempting to run gitversion then the detailed error information should be passed back up to the output log so the problem can be diagnosed without having to manually replicate the build environment.
It was also frustrating to have to manually figure out what breaking changes were made to both the task and underlying Gitversion config. To fix the config we had to fix the one error that was reported, rerun the process, fix the next error. If a migration document or similar was available (maybe it is?) then this would have sped up the process.
Steps to Reproduce
Use the latest task/gitversion tooling in a DevOps build with a config file that contains invalid data. Example of invalid data would be a config that was valid in older versions. Here's an example.
# Configuration file for GitVersion
assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: None
commit-message-incrementing: Enabled # MergeMessageOnly doesn't seem to work properly
mode: ContinuousDelivery
increment: Patch
branches:
# main uses a version based upon release tag plus any commits to branch with commit messages for PRs
main:
regex: ^(master|main)
tag: ''
increment: Patch
prevent-increment-of-merged-branch-version: true
is-mainline: true
# release uses the version in the branch name (+hotfix) and increments patch if there has been any changes since then
release:
regex: release?[/-]
tag: 'hotfix'
source-branches:
- master
- main
increment: Patch
is-release-branch: true
Output log or link to your CI build (if appropriate).
Prerequisites
GitVersion package
AzureDevops task
What are you seeing?
We upgraded from task v0/GitVersion v5 to task v3/GitVersion v6. We made no changes to your gitversion config file that is used by all our builds. We didn't realize that the config format had changed. When the execute task ran all we got in the output was a "command failed" message. There was no indication why it failed or what was wrong.
The only way we diagnosed this issue was by cloning the repo locally, dropping in the config file that is used and then running the same command line that the build server runs. This revealed that our config file had entries that are no longer supported.
What is expected?
If an error occurs while attempting to run gitversion then the detailed error information should be passed back up to the output log so the problem can be diagnosed without having to manually replicate the build environment.
It was also frustrating to have to manually figure out what breaking changes were made to both the task and underlying Gitversion config. To fix the config we had to fix the one error that was reported, rerun the process, fix the next error. If a migration document or similar was available (maybe it is?) then this would have sped up the process.
Steps to Reproduce
Use the latest task/gitversion tooling in a DevOps build with a config file that contains invalid data. Example of invalid data would be a config that was valid in older versions. Here's an example.
Output log or link to your CI build (if appropriate).