Skip to end of banner
Go to start of banner

How to add labels to all builds in a plan using Bamboo Command Line Interface (CLI)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This article explains how to add labels to all the builds in a particular plan using the Bamboo Command Line Interface (CLI) app.

Instructions

Use the runFromBuildList action along with addLabels to add labels in all the builds under the Bamboo plan.

  1. Execute the below CLI action.

     --action runFromBuildList --plan "TR-TP" --common "-a addLabels --build "@build@" --labels label1"

    Here is the output of the action:

    Run: -a addLabels --build TR-TP-10 --labels label1
    'label1' labels were added to TR-TP-10.
    
    Run: -a addLabels --build TR-TP-9 --labels label1
    'label1' labels were added to TR-TP-9.
    
    Run: -a addLabels --build TR-TP-8 --labels label1
    'label1' labels were added to TR-TP-8.
    
    Run: -a addLabels --build TR-TP-7 --labels label1
    'label1' labels were added to TR-TP-7.
    
    Run: -a addLabels --build TR-TP-6 --labels label1
    'label1' labels were added to TR-TP-6.
    
    Run: -a addLabels --build TR-TP-5 --labels label1
    'label1' labels were added to TR-TP-5.
    
    Run: -a addLabels --build TR-TP-4 --labels label1
    'label1' labels were added to TR-TP-4.
    
    Run: -a addLabels --build TR-TP-3 --labels label1
    'label1' labels were added to TR-TP-3.
    
    Run: -a addLabels --build TR-TP-2 --labels label1
    'label1' labels were added to TR-TP-2.
    
    Run: -a addLabels --build TR-TP-1 --labels label1
    'label1' labels were added to TR-TP-1.
    
    Run completed successfully. 10 actions were successful 
    
    

    Check the below screenshot to see how it appears after adding the labels: 


  • It is recommended to test the commands in a non-production environment or run the action with --simulate parameter to verify the behavior before deploying.
  • No labels