Skip to content

chore(e2e): rename e2e-next directory to e2e - #4128

Merged
adriankabala merged 1 commit into
v0.35from
ak/e2e-rename35
Jul 31, 2026
Merged

chore(e2e): rename e2e-next directory to e2e#4128
adriankabala merged 1 commit into
v0.35from
ak/e2e-rename35

Conversation

@adriankabala

@adriankabala adriankabala commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Mirrors the layout main has had since #4013 so backports land automatically. The shared backport flow re-roots a monorepo diff with git diff --relative=staging/github.com/loft-sh/vcluster/ and applies it with git apply --3way; that patch is rooted at e2e/, so against e2e-next/ there is no preimage blob to match and every test backport either conflicts or fabricates a second parallel tree.

Also passes test-dir: e2e to run-ginkgo in both ginkgo workflows. The action defaults to e2e-next and does cd "$TEST_DIR", so without this the suite would not run at all.

What issue type does this pull request address? (keep at least one, remove the others)
/kind test

What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible)
resolves #
Refs ENGQA-1484

Please provide a short message that should be published in the vcluster release notes
Fixed an issue where vcluster ...

What else do we need to know?

E2E Tests

Default Test Execution

The mandatory PR suite runs automatically. Only specify additional test suites below if needed.

Adding New Test Suites

When adding a new ginkgo test suite:

  • Add labels to the test suite
  • Update label-filter section below to execute the new test suite
  • Verify test suite runs in CI/CD pipeline

Additional test suites

Additional test suite(s) that will be executed before the mandatory PR suite:

none

Note

Medium Risk
Large mechanical rename across CI and all E2E imports; wrong path in one workflow or script would skip or break the suite, but no production runtime behavior changes.

Overview
Renames the Ginkgo E2E tree from e2e-next to e2e so it matches main and backport patches rooted at e2e/ apply cleanly. The suite package is now e2e (was e2e_next), and imports use github.com/loft-sh/vcluster/e2e/... throughout.

CI and local tooling now target ./e2e: Ginkgo workflows pass test-dir: e2e to run-ginkgo (the action otherwise defaults to e2e-next and would not run the suite). Change detection, Justfile / Justfile.agent, hack/test.sh unit-test exclusions, and .golangci.yml path rules are updated the same way. Agent docs, E2E conventions, and CODEOWNERS paths are aligned with the new name.

Reviewed by Cursor Bugbot for commit 35671f5. Bugbot is set up for automated code reviews on this repo. Configure here.

Mirrors the layout main has had since #4013 so backports land automatically.
The shared backport flow re-roots a monorepo diff with
`git diff --relative=staging/github.com/loft-sh/vcluster/` and applies it with
`git apply --3way`; that patch is rooted at `e2e/`, so against `e2e-next/` there
is no preimage blob to match and every test backport either conflicts or
fabricates a second parallel tree.

Also passes `test-dir: e2e` to run-ginkgo in both ginkgo workflows. The action
defaults to `e2e-next` and does `cd "$TEST_DIR"`, so without this the suite
would not run at all.

Refs ENGQA-1484
@github-actions

Copy link
Copy Markdown
Contributor

E2E Ginkgo Tests

Status Commit Run
Passed 35671f5e8fe8e51b772850c5f7b06e49c29a2411 View run #30615034659

@adriankabala
adriankabala marked this pull request as ready for review July 31, 2026 08:45
@adriankabala
adriankabala requested review from a team as code owners July 31, 2026 08:45
@adriankabala
adriankabala merged commit b465d0e into v0.35 Jul 31, 2026
29 of 33 checks passed
@adriankabala
adriankabala deleted the ak/e2e-rename35 branch July 31, 2026 08:49
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.

2 participants