Unverified Commit ced39776 authored by Tobias Koppers's avatar Tobias Koppers Committed by GitHub

ci: don't run non-adapter + cache components deploy tests in PRs (#100824)

### What?

Drop the non-adapter builder + cache components combination from the
"Test new and changed tests when deployed" PR matrix. The matrix had 20
entries (group × builder × cache components); it now has 15:

- adapter, cache components off
- adapter, cache components on
- non-adapter, cache components off

### Why?

#100591 added the full builder × cache-components product. The release
deploy tests never run cache components with the non-adapter Turbopack
builder, so PR CI was testing a combination that release testing doesn't
cover.

### How?

The job gets a matrix `exclude` entry with a comment explaining why. The
remaining 15 entries keep their names, `stepName`s, env and commands, so
their report history continues. Nothing else in the workflow changes.

Verified by parsing the workflow and expanding the matrix with GitHub's
exclude rules. Every remaining rendered script was run with `node`
stubbed, and each one matches canary's env and command. The `exclude`
entry is the only difference from canary.

<!-- NEXT_JS_LLM -->


<!-- fleet 115592cd-38e9-4ec3-904b-f1c778e1e1d9 -->
Co-authored-by: 's avatarvercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
Co-authored-by: 's avatarTobias Koppers <1365881+sokra@users.noreply.github.com>
parent 4084a0f4
......@@ -908,6 +908,11 @@ jobs:
builder: [adapter, non-adapter]
# Run without and with cache components (__NEXT_CACHE_COMPONENTS=true).
cache-components: [false, true]
exclude:
# The release deploy tests don't run cache components with the
# non-adapter builder.
- builder: non-adapter
cache-components: true
permissions:
contents: read
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment