You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
Variables and shared artifact with json data format will cover it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.