Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is there a way to supply values for variables when selecting the release to deploy?

Jimmy Seddon Community Leader Apr 03, 2019

Hello Everyone,

Currently, we have a Bamboo Deployment project with a few environments that run powershell based deployment scripts.  This started as something that was run manually that we are trying to move into Bamboo.

When we runs these scripts manually there have been times where a couple of the servers in the powershell list fail to deploy for whatever reason, instead of running a full deployment again they added an override flag to be able to define a subset of the servers to re-deploy to.  Instead of editing the environment taks and adding this into the script task, then running the deployment, and finally removing it from the task again, our deployment team was wondering if there is a setting our add-on that would allow them to provide that value on the fly when they are selecting what release to deploy.

Does anyone know if this is something that is possible?

1 answer

1 accepted

2 votes
Answer accepted

Hi @Jimmy Seddon

Thank you for explaining in details what is your scenario there. I totally get why you need custom run for deployments allowing you to set the variables previously, even though this feature is not available.

We do have an old feature request for this at [BAM-13707] Parameterised variables for Deployment environments which was not prioritized among other more important features along the time.
(i) Please check our Implementation of New Features Policy for more details on how we prioritize the implementation of new suggestions.

Possible workaround

If you know the remote agent used for your deployment (which can be dedicated), you could get the flag from a file in that server and inject it into the deployment using the Inject variables task.

Add-ons from third-party vendors

I was searching for possible add-ons for this and found this one that could potentially help you: Custom Deployments for Bamboo.

I hope I could help.

Jimmy Seddon Community Leader Apr 04, 2019

Hi Daniel,

Thanks for the response.  Bare minimum I'll go and vote for that feature request, and I'll take a look at your suggested work around.

Thanks for your help!

-James

Like Daniel Santos likes this

If you think this answer can help other users, please click the button "this helped me". 
See you in the next thread!

Like Jimmy Seddon likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

223 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you