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

Plan to execute on the agent depending on an input variable

We have a Bamboo plan that is used to create tenancies in an application. The same plan can be used to create tenancies in Model or Prod.

We have separate agents for Model & Prod. We want a way to select the agent based on an input variable when the plan is triggered.

1 answer

1 accepted

1 vote
Answer accepted
Jimmy Seddon Community Leader Jun 05, 2019

Hi @Devendra Singh Rawat,

Welcome to the Community!

Can you provide a bit more information about what makes the agents for Model & Prod different and what build tasks they are performing differently?

I'm almost wondering if what you really need is a deployment project instead of an input variable, any more information you can provide about what is being done would be helpful.



Thanks James for the response. Below are the details.

The main difference between Model & Prod agent is that they are in different networks. Model agent connects to Model environment and Prod agent to Prod environment. Please note both the environment constitutes of same set of applications (though different instances).

With regard to tasks also they are doing exactly the same thing in Model & Production. Just for reference the plan triggers an Ansible playbook which connects to multiple interfacing applications to manage tenancies. From build perspective the only difference is the endpoint used by respective agents the tasks the are same.  

Jimmy Seddon Community Leader Jun 06, 2019

Hi @Devendra Singh Rawat,

Ok based on your response you should look at using a Deployment Project instead of a Build Plan.

Here's a link to the documentation on what deployment projects are:

In a nutshell, this will allow you to setup multiple "environments" (in your case Model & Prod) you can then provide a list of tasks you wish to have run when deploying to that environment (which includes things like checking out configs from source code, downloading built artifacts, running scripts, copying files, etc.)

You can also assign agents to environments (which is exactly the piece you are looking for) where you get to decide which agent is capable of executing the set of tasks for a given environment.

I hope that helps answer your question!


Thanks James the deployment project achieved my objective

Like Jimmy Seddon likes this
Jimmy Seddon Community Leader Jun 20, 2019

Awesome!  I'm glad that worked for you!


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events