Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,501,434
Community Members
 
Community Events
180
Community Groups

How do I auto-version ASP.Net Core 2.0 code in Bamboo

Edited

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?

 

 

1 answer

0 votes

Hi! 

Variables and shared artifact with json data format will cover it

https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html

 

Cheers,

Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events