With various older console, service and web applications, I used Bamboo's GitVersion task type in a build plan task, calling the "/UpdateAssemblyInfo" argument, and placed a GityVersion.yml file in my project root in the repository and it worked fine.
However, doing the same with my ASP.Net Core 2.0 code causes the build to fail. Removing the GitVersion task allowed the build to complete successfully.
I can run GitVersion.exe /UpdateAssemblyInfo in my local dev machine and it displays the output json without any errors. It just fails when run in the Bamboo build server using the GitVersion task.
Is there a different way this needs to be handled for ASP.Net Core 2.0 code?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.