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

Deploy customized

Hello, I am building some pipelines to build and deploy Big Data jobs to spark. I was happy to see that there is an option of Run Customized for a build plan, but I was really surprised when that option is not available where I actually need it: In the deployment project.

My idea is to version the data, pass input and ouptut directories for the job as parameters, so I can run the same artifacts with different input and output to process different versions of the data.

When I have a chain of jobs (A -> B) I don't want to re-build B when A outputs some version of the data, just to tell B that it has to run with that version. I would like to be able to specify to B that the latest deployment from A was version a1, so it has to take a1 as input parameter to deploy version b1.

I understand that this automatic linking may be a special use case for jobs, so I thought to make it manual: I will specify the version in a bamboo variable, that I can modify at deployment time. But I didn't find the option in bamboo to do that!, is there already a feature request to implement this? Am I missing something?

P.S. We are defining the pipelines as code with specs, so changing the code where we define the bamboo variables just to deploy with a different input is not what we really want. We need exactly the same pipeline, but with the ability to change the variable at deploy time, so we can say where to read and where to write.

Thanks for your help!

1 answer

1 accepted

1 vote
Answer accepted
Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 04, 2020

Hi @alvaro_martin,

Welcome to the Community!

We were in a similar situation and we ended up purchasing this marketplace app:

If you are looking for a solution that doesn't cost anything, we were investigating using extra deployment environments and using powershell scripts and some logic to determine which one should be triggered.  We decided that the cost of maintaining that would be larger than spending some money on an app.

I hope that helps!


we don't directly manage our bamboo deployment, so this option is a bit complicated for us. I already thought that the only alternative was that plugin, and I wanted to confirm that. Sad that there isn't a better alternative.

Thanks for your answer.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events