3.9. Build environments
As with pod environment variables, build environment variables can be defined in terms of references to other resources or variables using the Downward API. There are some exceptions, which are noted.
You can also manage environment variables defined in the BuildConfig with the oc set env command.
Referencing container resources using valueFrom in build environment variables is not supported as the references are resolved before the container is created.
3.9.1. Using build fields as environment variables
You can inject information about the build object by setting the fieldPath environment variable source to the JsonPath of the field from which you are interested in obtaining the value.
Jenkins Pipeline strategy does not support valueFrom syntax for environment variables.
Procedure
Set the
fieldPathenvironment variable source to theJsonPathof the field from which you are interested in obtaining the value:env: - name: FIELDREF_ENV valueFrom: fieldRef: fieldPath: metadata.name
3.9.2. Using secrets as environment variables
You can make key values from secrets available as environment variables using the valueFrom syntax.
Procedure
To use a secret as an environment variable, set the
valueFromsyntax:apiVersion: v1 kind: BuildConfig metadata: name: secret-example-bc spec: strategy: sourceStrategy: env: - name: MYVAL valueFrom: secretKeyRef: key: myval name: mysecret
