Skip to content

Conversation

@danbar2
Copy link
Contributor

@danbar2 danbar2 commented Jan 29, 2026

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR optimizes E2E test execution by:

  1. Consolidating the E2E workflow into the "Build, Check and Test" workflow
  2. E2E tests now only run when there are changes to operator/** or .github/** paths
  3. E2E tests are gated behind successful completion of test, build, and check jobs

This reduces unnecessary CI resource consumption by skipping expensive E2E tests when:

  • Changes don't affect operator or workflow code
  • Build/test/check jobs have already failed

Which issue(s) this PR fixes:

Fixes #377

Special notes for your reviewer:

  • Deleted .github/workflows/e2e-test.yaml and merged its contents into build-check-test.yaml
  • Uses dorny/paths-filter@v3 action to detect path changes
  • E2E jobs have needs: [test, build, check, changes] to enforce ordering

Does this PR introduce a API change?


# E2E tests - only run after build, check, and test jobs succeed
# Only triggered by changes to operator or .github folders
e2e:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense to allow people to also trigger e2e tests for DRAFT PRs to validate if all tests are running fine before the PR is opened up for review?
If you agree then we can add the following if condition:

e2e:
  if: |
    (github.event_name == 'pull_request' && (github.event.pull_request.draft == false || contains(github.event.pull_request.labels.*.name, 'run-e2e')))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

2 participants