Run pipeline action in Azure DevOps package

The Run pipeline action in the Azure DevOps package enables you to submit a run request for an existing CI/CD pipeline in Azure DevOps. You can optionally pass runtime parameters, pipeline variables, and a list of stages to skip from an automation workflow. The action queues the run and returns the run ID on successful submission.

Settings

  • Session name: The name of the active Azure DevOps session. Choose Session name and enter the name you specified when you opened the session, or choose Variable to use a session variable.
  • Pipeline ID: Specify the unique identifier of the pipeline to run. Enter the pipeline ID directly or use a string variable. You can obtain the pipeline ID from the Create pipeline action .
  • Parameters (optional): Specify a dictionary of parameter names and values to pass to the pipeline run. Each key-value pair represents a parameter name and its corresponding value. Choose Dictionary to configure the dictionary inline, or choose Variable to use an existing dictionary variable. The action converts dictionary values to plain objects before sending the request.
    Example:
    {
      "environment": "qa",
      "runPerfTests": true
    }
    This passes two parameters to the pipeline: environment set to qa, and runPerfTests set to true.
  • Variables (optional): Specify a table of pipeline variables to pass at runtime. The table must include the following columns: name (string), value (string), and isSecret (Boolean). Set isSecret to true for variables that contain sensitive values, such as credentials. Choose Table to configure the table inline, or choose Variable to use an existing table variable.
    Example:
    {
      "appName": {
        "value": "billing-service"
      },
      "region": {
        "value": "westus2"
      },
      "apiKey": {
        "value": "$Credential:ADO_API_KEY
    quot;, "isSecret": true } }
    This sets three variables: appName and region as plain-text values, and apiKey as a secret that will not appear in pipeline logs.
  • Stages to skip (optional): Specify a list of pipeline stage names to exclude from the current run. Enter each stage name as a string. Choose List to configure the list inline, or choose Variable to use an existing list variable.
    Example:
    ["PerfTest"]
    This skips the PerfTest stage.
  • Assign output to a variable: The variable to store the run ID returned by Azure DevOps after the run is queued. Use this ID in subsequent actions, such as Get pipeline run details, to monitor the run.