Unverified Commit b431bd4b authored by JJ Kasper's avatar JJ Kasper Committed by GitHub

Leverage VERCEL_CLI_VERSION env for deploy tests (#39823)

This updates our next-e2e test deploy mode to auto pass along the VERCEL_CLI_VERSION env variable to allow testing builder changes easier. cc @nkzawa who encountered this.
parent c172d461
...@@ -74,6 +74,13 @@ export class NextDeployInstance extends NextInstance { ...@@ -74,6 +74,13 @@ export class NextDeployInstance extends NextInstance {
additionalEnv.push(`${key}=${this.env[key]}`) additionalEnv.push(`${key}=${this.env[key]}`)
} }
if (process.env.VERCEL_CLI_VERSION) {
additionalEnv.push('--build-env')
additionalEnv.push(
`VERCEL_CLI_VERSION="${process.env.VERCEL_CLI_VERSION}"`
)
}
const deployRes = await execa( const deployRes = await execa(
'vercel', 'vercel',
[ [
...@@ -81,8 +88,6 @@ export class NextDeployInstance extends NextInstance { ...@@ -81,8 +88,6 @@ export class NextDeployInstance extends NextInstance {
'--build-env', '--build-env',
'NEXT_PRIVATE_TEST_MODE=1', 'NEXT_PRIVATE_TEST_MODE=1',
'--build-env', '--build-env',
'FORCE_RUNTIME_TAG=canary',
'--build-env',
'NEXT_TELEMETRY_DISABLED=1', 'NEXT_TELEMETRY_DISABLED=1',
...additionalEnv, ...additionalEnv,
'--force', '--force',
......
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