POSIX does not permit =
in environment variable names: http://pubs.opengroup.org/onlinepubs/009695399/functions/setenv.html however, it is not filtered on bitrise leading to weird states.
Examples:
- Envman fails with not so user-friendly message
setenv: invalid argument
- Script step just fails without any message: https://www.bitrise.io/build/b5c947f0057f2f49
- CLI fails on
EnvmanJSONPrint
: https://www.bitrise.io/build/2f02f4f9779941cc
Note that, there are even several errors reported in a single line:
ERRO[15:41:36] Step (activate-ssh-key@3.1.1) failed, error: EnvmanJSONPrint failed, err: Error: exit status 1, details: FATA[15:41:36] Failed to convert envs, error: setenv: invalid argument
Starting build with =
in env variable name should be probably disallowed. E.g. Build trigger API should return an error instead of starting build as well as online trigger form.