Updated on 2024-05-29 GMT+08:00

Using Parameters

This section describes how to configure the releaseversion parameter in a pipeline and transfer the parameter to a build job.

Procedure

  1. Create a build task.
  2. On the Parameters tab page, add the releaseversion parameter, set the default value, and enable Runtime Settings.

  3. On the Build Actions tab page, select Upload to Release Repos and set Release Version as a reference parameter. After you enter $ in the text box, a parameter list is displayed. Select the releaseversion parameter created in the previous step.

  4. Save the build task.
  5. Create a pipeline using a blank template, add the Build extension and select the build task created in previous steps. The parameter releaseversion is displayed.

  6. Move the cursor to the releaseversion parameter to set it as a pipeline parameter. Alternatively, click OK, switch to the Parameter Configuration tab page, create the pipeline parameter releaseversion, set Type to Auto-increment or String, set a default value, and enable Runtime Setting.

  7. Switch back to the Task Orchestration tab page, and edit the added build task. Use $ to reference releaseversion parameter in the build task.

    • Only parameters for which Runtime Setting is enabled are displayed.
    • The parameter reference format is "${ParameterName}". ParameterName indicates the pipeline parameter name. After you enter $ in the parameter text box, the parameter list is automatically displayed.
    • You can move the cursor to a parameter name to quickly set the parameter as a pipeline parameter and directly reference the parameter.

  8. Save the information and click Save and Execute. In the displayed dialog box, you can check the parameter information.

    The parameter value is the default value specified when you add the parameter. You can change the value. If you change it, the new value will be used in the build job.

  9. Click Execute to execute the pipeline.