Custom Env. Vars did not override App Env Vars or Workflow env vars

[dvdchr-tvlk]

Hi Bitrise Team,

I noticed that custom environment var defined in the Start build > Advanced section did not override the ones that was defined in the App Env Vars.

For example, I have a default App Env Var for $FOO containing value “bar”.
When I start a build using Advanced section, I added custom environment variable for"FOO", with the value “baz”.

The result is when reading FOO, the predefined value (i.e. “bar”) is always read.

Is this intended?

[viktorbenei]

Please see

How to override environment variables through the Build Trigger API

Environment Variables are set (processed) in a specific order. An environment variable processed before another one can’t override the second one, but the second one can use the first one. If you use the Build Trigger API and you specify one-off environment variables as parameters of the build, those will be processed after the Secret Env Vars, but before App Env Vars. This means that simply specifying the same environment variable this way which is also defined in the build configuration (bit…

and feel free to ask any questions there!

[dvdchr-tvlk]

Ah, I missed that one.

Thanks, Victor!

Best,
David