spec:
output:
to:
kind: "ImageStreamTag"
name: "sample-image:latest"
Builds that use the Docker or Source strategy result in the creation of a
new container image. The image is then pushed to the container image registry
specified in the output section of the Build specification.
If the output kind is ImageStreamTag, then the image will be pushed to the
integrated OpenShift Origin registry and tagged in the specified image stream. If
the output is of type DockerImage, then the name of the output reference
will be used as a Docker push specification. The specification may contain a
registry or will default to DockerHub if no registry is specified. If the output
section of the build specification is empty, then the image will not be pushed
at the end of the build.
spec:
output:
to:
kind: "ImageStreamTag"
name: "sample-image:latest"
spec:
output:
to:
kind: "DockerImage"
name: "my-registry.mycompany.com:5000/myimages/myimage:tag"
Docker and Source strategy builds set the following environment variables on output
images:
| Variable | Description |
|---|---|
|
Name of the build |
|
Namespace of the build |
|
The source URL of the build |
|
The Git reference used in the build |
|
Source commit used in the build |
Docker and Source builds set the following labels on output images:
| Label | Description |
|---|---|
|
Author of the source commit used in the build |
|
Date of the source commit used in the build |
|
Hash of the source commit used in the build |
|
Message of the source commit used in the build |
|
Branch or reference specified in the source |
|
Source URL for the build |
You can also use the BuildConfig.spec.output.imageLabels field to specify a
list of custom labels that will be applied to each image built from the
BuildConfig.
spec:
output:
to:
kind: "ImageStreamTag"
name: "my-image:latest"
imageLabels:
- name: "vendor"
value: "MyCompany"
- name: "authoritative-source-url"
value: "registry.mycompany.com"
Built images can be uniquely identified by their digest, which can later be used to pull the image by digest regardless of its current tag.
Docker and Source builds store the digest in
Build.status.output.to.imageDigest after the image is pushed to a registry.
The digest is computed by the registry. Therefore, it may not always be present,
for example when the registry did not return a digest, or when the builder image
did not understand its format.
status:
output:
to:
imageDigest: sha256:29f5d56d12684887bdfa50dcd29fc31eea4aaf4ad3bec43daf19026a7ce69912