Skip to content

Prevent triggering of e2e tests unless "Build, test, check" jobs succeed #377

@unmarshall

Description

@unmarshall

/area dev-productivity
/kind enhancement

What you would like to be added?

Prevent E2E tests to be triggered unless and until build, test and check jobs have completed successfully.

Why is this needed?

E2E tests require additional resources (bigger runners) and also take a long time to finish. When commits are made to a PR, then there are often cases where make check or make build or make test fails but it still triggers e2e tests which is completely unnecessary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/dev-productivityCategorizes Issue/PR as related to dev productivity improvementsenhancementNew feature or requestkind/enhancementCategorizes issue or PR as related to a new feature, enhancement or improvement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions