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
I have searched issues to ensure it has not already been reported
GitVersion package
AzureDevops task
What are you seeing?
I'm migrating from version 2 to version 3 of the azdo GitVersion tasks.
However, I'm seeing some behaviours I can't explain.
We have a pretty standard multi-project c# solution with a file called SharedAssemblyInfo.cs at the root. We configure GetVersion to update that file using our own config file.
I've done 3 tests as documented below where execute@2 produces the expected result, but neither execute@3 and command@3 do. I've included the command lines where are generated and they look correct and similar.
C:\hostedtoolcache\windows\GitVersion.Tool\5.12.0\dotnet-gitversion.exe --roll-forward Major D:/a/2/s/My.Project /output json /l console /config D:\a\2\s\azdtasks\PipelineTemplates\GitVersion.yml /updateassemblyinfo D:\a\2\s\My.Project/SharedAssemblyInfo.cs
...
INFO [03/28/25 11:06:58:84] Updating assembly info files
INFO [03/28/25 11:06:58:84] Found 17 files
INFO [03/28/25 11:06:58:93] Done writing
This run finds all of the old AssemblyInfo.cs files within the project which are redundant (yes, they should be removed at some point!). However, it completely misses my SharedAssemblyInfo.cs and it's not one of the 17 files that git version has modified.
command@3
After trying execute@3 I thought I would try assembling the command line myself via command@3.
Prerequisites
GitVersion package
AzureDevops task
What are you seeing?
I'm migrating from version 2 to version 3 of the azdo GitVersion tasks.
However, I'm seeing some behaviours I can't explain.
We have a pretty standard multi-project c# solution with a file called
SharedAssemblyInfo.cs
at the root. We configure GetVersion to update that file using our own config file.I've done 3 tests as documented below where execute@2 produces the expected result, but neither execute@3 and command@3 do. I've included the command lines where are generated and they look correct and similar.
To summarise the below:
I'm at a bit of a loss to explain the differences.
execute@2
This is what we're migrating from and it works as expected:
Here is the generated command from the build logs:
This run is perfect and it has updated my
SharedAssemblyInfo.cs
as expected.execute@3
This was my first attempt at migrating away from version 3. I see that additionalArguments are no longer supported but that doesn't matter too much.
This run finds all of the old AssemblyInfo.cs files within the project which are redundant (yes, they should be removed at some point!). However, it completely misses my
SharedAssemblyInfo.cs
and it's not one of the 17 files that git version has modified.command@3
After trying execute@3 I thought I would try assembling the command line myself via command@3.
This run doesn't update any assembly info files at all.
What is expected?
Documented above.
Steps to Reproduce
See above.
Output log or link to your CI build (if appropriate).
The text was updated successfully, but these errors were encountered: