From aa1604bb0bf42eb73a4e97309cbeed2974ddde06 Mon Sep 17 00:00:00 2001 From: Karen Sawrey Date: Thu, 12 Dec 2024 13:01:19 +0100 Subject: [PATCH] Update environment_variables.md Clarification. --- pages/pipelines/configure/environment_variables.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/pages/pipelines/configure/environment_variables.md b/pages/pipelines/configure/environment_variables.md index 07782ca18d..1c39ae8880 100644 --- a/pages/pipelines/configure/environment_variables.md +++ b/pages/pipelines/configure/environment_variables.md @@ -217,9 +217,6 @@ There are two places in a pipeline.yml file that you can set environment variabl Defining an environment variable at the top of your yaml file will set that variable on each of the command steps in the pipeline, and is equivalent to setting the `env` attribute on every step. This includes further pipeline uploads through `buildkite-agent pipeline upload`. -> 📘 -> Top level pipeline environment variables will override what is set in the `env` attribute of an individual step. - #### Setting variables in a Trigger step Environment variables are not automatically passed through to builds created with [trigger steps](/docs/pipelines/configure/step-types/trigger-step). To set build-level environment variables on triggered builds, set the trigger step's `env` attribute.