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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,459,328
Community Members
 
Community Events
176
Community Groups

How to pass parameters to the jobs while triggering any job

Suppose we have one ssh job that  should run in multiple env like ENV-A, ENV-B
Now i want to run the job with parameter ENV-B or ENV-B, if it matches with ENV-A, it will run for ENV-A . Is there any way to use single job for multiple env or we have create separate separate job for multiple env. 

2 answers

0 votes

Hi Suvankar,

If your intention is to connect to multiple environments, it is necessary to define multiple ssh tasks to connect to multiple environments preferably in a different job/plan based on your requirement.

If you want to run using the same job, you may use plan variables and define the hostname in *Configure plan -> Variables(tab)*

host= env1hostname

and use this variable in your script task

ssh://${bamboo.host}

Now, you can choose Run customized and give a hostname of your preference to override the hostname variable for that build. See Triggering a plan build manually for more info

0 votes
robhit Atlassian Team Apr 04, 2018

Hi Suvankar,

Thanks for your question!

I believe the only solution to your problem in my knowledge is by using a script task.

Thanks,

Robhit

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events