We have a huge amount of plans in bamboo (400+) and I'd like to be able to give them all labels so we can use the filtering functionality better. I don't see a way of doing this as a bulk operation however.
I saw in the rest api documentation that you can change the plan-build labels and I altered this call to try and change the plan labels. The command worked ok. Retrieving the labels after the change showed the label was added but this wasn't reflected on the web ui. (I added the label "test" and it did show up in the filter options but the plan didn't show the label and when the filter was selected there were zero plans shown)
Curl command I used:
curl -k -v -X POST --user <USER>:<PASSWORD> "<BAMBOO-URL>/rest/api/latest/plan/<PLAN-NAME>/label" -d "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?><label name=\"test\"/>" -H "Content-type: application/xml"
Any ideas on an alternative to going in to 400+ plans and adding labels one by one?
I wonder if editing labelled plan configuration (and saving it) would be enough for Bamboo to start displaying the labels in the UI. Would you be able to check that on a single plan? I think you've encountered a bug (obviously) but above test could narrow down where the problem exists in the Bamboo code...
Yes, the manual editing of a plan and adding a label on the UI works fine. Using the rest api, I can see the change going in fine in to the buildresultsummary_label database table. Except it needs a restart of bamboo for that change to be picked up on the UI.
As I said, it shows up in the list of labels to filter but it doesn't seem to be attached to the plan.
What would happen if you:
1) used REST to add a 'test' label to a plan that has no such label.
1a) check in the UI if the 'test' label appear - we expect it won't appear, while it will be in the db table.
2) edited configuration of that plan and saved it (for example changed the plan name from "Plan name" to "Plan name2")
3) would the 'test' label appear in the UI?
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot