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

Is it possible to have a single bamboo installation that caters for multiple instances

Marnus van der Schyff April 5, 2022

We trying to setup a single bamboo installation with multiple instances for each business unit to sign in.

 

For example, we have team1, team 2 and team3. All the teams sign in to the same bamboo to their own instance. For each team they have their own set of build agents, build plans and deployment plans.

 

At the moment we have 5 bamboo's, and each bamboo has 5 dedicated build agents. So we want to collapse the 5 bamboo's, but still have a logical split for each business unit.

1 answer

0 votes
Eduardo Alvarenga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 5, 2022

Hello @Marnus van der Schyff,

Welcome to Atlassian Community!

You can surely have a single Bamboo instance that would be cross-functional operating on multiple business units, each one running its own set of Agents.

To accomplish that, you'll need.

  • A Bamboo licence that would support the desired number of agents
  • Plan and Define sets of Dedicated agents across your Builds and Deployments

When dedicating Agents, you can categorise them at the following entity levels:

  • Build
    • Project
    • Plan
    • Job
  • Deployment
    • Project
    • Environment

For example: considering you have 3 teams, you can create 3 Projects named "Team 1", "Team 2" and "Team 3" and dedicate 5 remote agents per project. This way each Project will have an independent set of 5 build/deployment agents that will be isolated from each other and won't compete for resources outside of their Project scope.

That's a very simple example, you can customise it at deeper levels when using Plans or Jobs.

Alternatively, you can define custom capabilities named "Team 1", "Team 2" and "Team 3" on your agents and add them as a requirement at the Job level. Using capabilities allows a bit more flexibility as you can have "soft-dedicated" agents but also use any free resources for other non-dedicated builds or deployments that don't need to be bound to a specific agent.

 

Cheers,

 

Eduardo Alvarenga
Atlassian Support APAC 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events