Skip to content

Adjust SDK Diff Pipeline Resource Trigger to Improve Frequency #5152

Open
@ellahathaway

Description

@ellahathaway

Related to #5151:

The SDK Diff pipeline is currently configured to trigger only on successful release branch builds of the dotnet-unified-build pipeline. However, due to the low success rate of dotnet-unified-build pipeline runs, the SDK Diff pipeline is not running frequently. For example, in this build, all build stages succeeded, but the SDK Diff pipeline did not trigger because the final VMR validation stage failed.

To address this, we should consider adjusting the resource trigger so that the SDK Diff pipeline fires after the SB build and VMR final join stages complete successfully.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-testingImprovements in CI and testing

    Type

    No type

    Projects

    Status

    10.0 RC1

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions