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,463,430
Community Members
 
Community Events
176
Community Groups

How can I attach or upload a file for a plan to use when I trigger the plan manually on Bamboo 6.9.1

I have a plan that I would like to be able to either accept a file as a parameter, or in the plan browse to a location and select a file to be uploaded.  My plan will then move the file to a specific location and rename it.  Can anyone suggest a method that does not require a plugin (unless the plugin is free) that will accomplish this in Bamboo.  This is fairly easy to do in Jenkins.

1 answer

0 votes

Hi @Jim Schwarz

The Bamboo SCP task does only upload from Bamboo to other servers/locations. There is an old request though to add also the download behavior to it.

I'm afraid this was not prioritized due to the low number of votes given the time this is already open.

Usually, we want a build to be predictable/replicable and therefore the data processed in it should come from a versioned source (repository). In your case you want the source to be external which will make a build associated with a repository to have multiple possible results for the same changeset of the associated source repository.

The best option I see in this case is using a script task with the SCP command to copy the file you want to the Bamboo build working directory (with this variable ${bamboo.build.working.directory})

In case you want to control this behavior with a custom variable, then will need to make sure your script task checks this variable and decide what to do next. The variable could bring the path to the file you want to copy in. e.g. The default value of the variable could tell the script task that no file needs to be copied.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events