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

Bamboo CLI addTask does not work for fields that have values with colons

Hi,

I've been having trouble using the bamboo cli to create a AWS S3 Object task. The bamboo cli uses a comma separated list where the fields are mapped to their values via colons

--fields field1:value1,field2:value2

However, this fails when the value contains colons, such as in the artifactToUpload field for the AWS S3 Object task:

-1:1:1:DEPLOYNAME: all artifacts

I noticed in the bamboo logs that the request ends up only using the value up until the first colon, so using the example above, only -1 is used in the request and fails.

However, when I switched to using the --field1 --value1 syntax, the call worked fine and created the task in bamboo. But since I had to go up to field7 using this syntax and since parameters field3 and above are deprecated, I was wondering if there was a workaround to getting this to work using the --fields parameter.

 

 

2 answers

0 votes

Hi! 

 

As I understand you wrote about bamboo cli from Bob-Swift toolset. 

Therefore I suggest you raise by link 

https://bobswift.atlassian.net/servicedesk

 

 

Cheers,

Gonchik Tsymzhitov

Use multiple field parameters to specify one field at a time - it is a bit easier.

In general, if you have CLI parameters that are comma and/or colon separated and the value contains a separator character, you need to single quote the value in order to prevent the embedded separator from being mis-interpreted.

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 ...

186 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