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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Building only selected projects in Visual Studio solution

We have a huge Visual Studio (2017) solution under one git repository and mutiple teams have their projects in it.

Let's say Team A has an ASP.NET Web Portal project - > Project 1

And Team B has a REST API project -> Project 2

These two teams would like to do CI on their own projects.

  • Visual Studio Solution
    • Project1
    • Project2
    • .
    • Project N

So, when configuring a build plan, can we specify bamboo just to build Project 2 and dependencies but do not build and deploy anything belongs to Project1?

Because the main issue is ( actually very rare) sometimes someone commits code which is not buildable and belongs to another team's project. But since bamboo tries to build entire solution, it also affects other teams CI.

Also will appreciate if you could refer related resources docos for this.



1 answer

Hi @Ahmet Sertan Yıldırım please try with bamboo inject variables.

You can edit some file in your code, with the name of the project to build and inject into bamboo and make the build based in this injected variable.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events