Release notes contain information about new and deprecated features, breaking changes, and known issues. The following release notes apply for the most recent Builds releases on OpenShift Container Platform.

Builds is an extensible build framework based on the Shipwright project, which you can use to build container images on an OpenShift Container Platform cluster. You can build container images from source code and Dockerfiles by using image build tools, such as Source-to-Image (S2I) and Buildah. You can create and apply build resources, view logs of build runs, and manage builds in your OpenShift Container Platform namespaces.

Builds includes the following capabilities:

  • Standard Kubernetes-native API for building container images from source code and Dockerfiles

  • Support for Source-to-Image (S2I) and Buildah build strategies

  • Extensibility with your own custom build strategies

  • Execution of builds from source code in a local directory

  • Shipwright CLI for creating and viewing logs, and managing builds on the cluster

  • Integrated user experience with the Developer perspective of the OpenShift Container Platform web console

For more information about Builds, see Overview of Builds.

Compatibility and support matrix

In the table, components are marked with the following statuses:


Technology Preview


General Availability

The Technology Preview features are experimental features and are not intended for production use.

Table 1. Compatibility and support matrix
Builds Version Component Version Compatible Openshift Pipelines Version OpenShift Version


Builds (Shipwright)



0.12.0 (GA)

0.12.0 (GA)

1.12 and later


Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Release notes for Builds General Availability 1.0

Builds General Availability (GA) 1.0 is now available on OpenShift Container Platform 4.14.

New features

The following sections highlight what is new in Builds 1.0.


  • This release supports the buildah and source-to-image build strategies. The Builds for Red Hat OpenShift Operator automatically installs these strategies for use.

    The buildpacks build strategy is currently in Developer Preview. Red Hat plans to make this strategy generally available for use in a future release.

  • With this release, you can define volume mounts in your BuildStartegy resource. When defining a strategy, you can declare volumes which can be shared across build steps and build runs. You can also declare the mount point for the volume which is fixed across all build steps. Volumes can either have a fixed volume source, or an overridable volume source that you can set in a Build or BuildRun resource.

  • With this release, you can embed a complete build specification into your BuildRun resource by using the spec.build.spec field. By embedding specifications, you can build an image without creating and maintaining a dedicated Build resource.

  • This release supports automated cleaning of completed build runs after a specific time or when a certain number of build runs is reached. By using retention parameters, you can specify the duration for which a completed build run can exist and the number of succeeded or failed build runs that can exist.

  • With this release, you can configure a build by defining the source, build strategy, parameter values, builder or docker file, output, retention parameters, and volumes in a Build resource.

  • With this release, you can configure a build strategy by defining strategy parameters, system parameters, step resources definitions, annotations, and volumes in a BuildStrategy or ClusterBuildStrategy resource.

  • With this release, you can configure a build run by defining the build reference, build specification, parameter values, service account, output, retention parameters, and volumes.

  • With this release, you can monitor your build resources by using build controller metrics.

  • With this release, you can add an annotation build.shipwright.io/referenced.secret: "true" to a build secret. Based on this annotation, the build controller takes a reconcile action when an event, such as create, update, or delete triggers for the build secret.


  • With this release, you can create, delete, list, or run a Build resource.

  • With this release, you can create or list a BuildRun resource, or view its logs.