nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Plan to execute on the agent depending on an input variable

Devendra Singh Rawat

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.

Accepted answers

Jimmy Seddon

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

All comments

Jimmy Seddon

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

Devendra Singh Rawat

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

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:

https://confluence.atlassian.com/bamboo/deployment-projects-338363438.html

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!

-James

Devendra Singh Rawat

Thanks James the deployment project achieved my objective

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

plan

remote-agent