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