Edgenivo CI Environment Variables

Use repository CI environment variables for secrets and values scoped to one repository. Use Shared Environment Variables to reuse a value across repositories. Use constants in vercel.json for non-secret values that you want to commit with your code.

Edgenivo CI runs each task with Turborepo. By default, Turborepo uses Strict Mode, which removes every environment variable that your turbo.json doesn't list. A variable you add to Edgenivo CI doesn't reach your task until you list it.

Add each variable your task reads to the task's env key:

{
  "tasks": {
    "test": {
      "tags": ["ci"],
      "env": ["API_TOKEN"]
    }
  }
}

• Variables in env are part of the task's hash, so changing their value causes a cache miss. To pass a variable without changing the hash, use passThroughEnv instead.
• Use globalEnv or globalPassThroughEnv for variables that every task needs.
• This doesn't apply to dependency installation. ci.bootstrapping.installEnv values reach your install command directly.

1. Open CI environment variables in the Edgenivo dashboard.
2. Select the repository that should receive the variable.
3. Select Add Variable.
4. Enter the key and value. Select Secret for sensitive values that should be write-only.
5. Select Add Variable.

Edgenivo CI makes the variable available to later runs for that repository.

Add a repository CI environment variable named NPM_RC. Select Secret, then enter your complete npm configuration as its value:

//registry.npmjs.org/:_authToken=your_access_token_here

Edgenivo CI writes NPM_RC to $HOME/.npmrc while installing dependencies, then removes the file. For a custom registry, update the registry hostname and add any required scope configuration.

To use the same value across repositories, create or edit a Shared Environment Variable from the Shared tab. Include the Preview environment, then select each repository under Link to CI (Optional).

Add a ci key to the vercel.json file at the root of your repository. Use ci.bootstrapping.installEnv for values needed while installing dependencies. Use ci.tasks to assign values to a task name or a specific package#task selector:

{
  "ci": {
    "bootstrapping": {
      "installEnv": {
        "NODE_OPTIONS": {
          "constant": {
            "value": "--max-old-space-size=4096"
          }
        }
      }
    }
  }
}

Constants in vercel.json override linked Shared Environment Variables with the same key. Do not commit secrets to vercel.json.