Build Environment
Overview
As with pod environment variables, build environment variables can be defined in terms of references to other resources/variables using the Downward API. However, there are some exceptions as noted below.
You can also manage environment variables defined in the |
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.
env:
- name: FIELDREF_ENV
valueFrom:
fieldRef:
fieldPath: metadata.name
Jenkins Pipeline strategy does not support |
Using Container Resources as Environment Variables
Referencing container resources using valueFrom
in build environment variables is not supported as the references are resolved before the container is created.
Using Secrets as Environment Variables
You can make key values from Secrets available as environment variables using the valueFrom
syntax.
apiVersion: v1
kind: BuildConfig
metadata:
name: secret-example-bc
spec:
strategy:
sourceStrategy:
env:
- name: MYVAL
valueFrom:
secretKeyRef:
key: myval
name: mysecret