Skip to content

Skip integration tests or other expensive jobs when unnecessary #2845

@AlanGreene

Description

@AlanGreene

Integration tests are currently run on all PRs, even if the files modified don't impact the tests.

For example, a PR that only modifies docs or other workflow definitions wouldn't impact the outcome of the integration tests, but they are still run and required to pass for the PR to be merged.

This can be problematic in case of flaky tests, where PRs that could otherwise be merged are blocked and numerous retries are required, wasting both time and resources.

Recent example: tektoncd/pipeline#9052

Action:

Review integration tests across the projects and apply filters / exclusions so they only run when necessary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/plumbingIssues or PRs related to the plumbing infrastructure but needing attention in a non-plumbing repo.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions