Automatic change request

Test Results related list

Lists the tests that were run in a pipeline after a package was created. If no package was created, then the list includes the tests that were run after an artifact version was created.

Scenarios:

A package is created in the pipeline, but no artifact versions are registered.

• If the change request is created in the package creation stage:

  No test results are displayed because a package is not yet linked to the pipeline execution.

• If the change request is created in a stage after the package creation stage:

  Build test summaries include those associated with stages after the package creation stage, up to the change-controlled stage.

Artifact versions are registered, but no package is created.

• If the change request is created in the artifact version stage:

  No test results will be displayed, because no tests are associated until the task execution is completed.

• If the change request is created in a stage after the artifact version stage:

  Build test summaries include those in the artifact version stage, as well as the stages afterward, up to the change-controlled stage.

Both artifact versions and package are created in the pipeline.

• If the change request is part of the stage after artifact version and package creation stages:

  Build test summaries include those associated with the package creation stage, as well as the stages afterward, up to the change-controlled stage.

• If the change request is part of the package creation stage, and artifact versions are created as part of an earlier stage; or

  the change request is created in a stage (not package creation) after the artifact version stage, but before package creation stage; or

  the change request is part of the package creation stage and artifact versions are created as part of an earlier stage:

  Build test summaries include those associated with the artifact version stage, as well as stages afterward, up to the change-controlled stage.

Custom change request process

These DevOps change properties are available to customize your change request flow.

To customize your change request flow, you must first create a System Definition > Choice List. For example, DevOps_Implement (value - 10).

Then, add the choice list to System Definition > Script Include > ChangeRequestStateHandlerSNC.

Once you have created the choice list and added it to the script include, you can update DevOps change properties with the new choice list values. For example, DevOps change request implement state -10.

Change Approval Policy workflow

A change request is automatically approved for low risk changes, when calculated risk and impact are below threshold values (set on the Step form for the app). The state is moved to Implement.

When calculated risk and impact values are at or above threshold values, the normal change stays in the Assess state until approved.

DevOps Change Policy workflow

A change request is automatically approved when certain conditions in the DevOps auto approval cycle are met. The state is moved to Implement. DevOps Change Policy approval is useful for less critical changes that do not require manual approval.

Change Approval Policy is mapped to DevOps Change Policy (instead of Normal Workflow Policy), and Risk Approvals is mapped to DevOps Change Policy.

This policy is inactive by default.

DevOps Risk Condition

You can use the DevOps risk and impact calculation based on committer risk score.

This condition is inactive by default.