Release notes
Highlights of what is new and what has changed with this OpenShift Builds release
Abstract
Chapter 1. Builds release notes
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
Buildahbuild 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".
1.1. Compatibility and support matrix
In the table, components are marked with the following statuses:
| TP | Technology Preview |
| GA | General Availability |
The Technology Preview features are experimental features and are not intended for production use.
Table 1.1. Compatibility and support matrix
| Builds Version | Component Version | Compatible OpenShift Pipelines Version | OpenShift Version | Support | |
|---|---|---|---|---|---|
| Operator | Builds (Shipwright) | CLI | |||
| 1.9 | 0.20.0+89b237b (GA) | 0.20.0+f302164 (GA) | 1.21-1.23 | 4.18-4.22 | GA |
| 1.8 | 0.19.0 (GA) | 0.19.0 (GA) | 1.20-1.22 | 4.17-4.21 | GA |
In the table above, the Shipwright version is provided with a commit ID. This indicates that Shipwright versions are no longer coupled and can be versioned independently. For the latest Shipwright version information, refer to the Content from github.com is not included.Shipwright upstream repository.
1.2. Release notes for Builds 1.9
Builds 1.9 is now available on OpenShift Container Platform 4.18 and later.
1.2.1. New features
The following sections highlight what is new in Builds 1.9:
- Enhanced network security for Builds operands
-
With this update,
NetworkPoliciesfor operand components in theopenshift-buildsnamespace isolate network traffic to reduce security risks. A default-deny policy restricts network exposure while defining explicit allow rules for Kubernetes API egress, webhook ingress fromopenshift-kube-apiserver, and metrics ingress fromopenshift-monitoring. - Blocked environment variables in build containers prevent code injection
-
Before this update, environment variables that could enable code injection in build containers were not restricted during build execution. With this update, OpenShift Builds blocks key environment variables, such as LD_PRELOAD, BASH_ENV, and NODE_OPTIONS, during build container execution. Validation occurs at the Build specification level and during environment variable merging when
BuildRunexecutes. You can also customize the list of blocked variables to fit your environment. - Environment variables in spec.env are correctly propagated to Source-to-Image Dockerfiles
-
Before this update, when using the Source-to-Image (S2I)
ClusterBuildStrategywith the --as-dockerfile option, environment variables defined in spec.env of a Build resource were silently ignored during the build process. With this update, environment variables defined in spec.env correctly propagate into S2I-generatedDockerfiles.
1.2.2. Fixed issues
- Shallow clone support for Git revisions in OpenShift Builds
- Before this update, specifying a Git revision (branch, tag, or commit SHA) in spec.source.git.revision caused Builds to perform a full Git clone including the entire repository history. Default executions, which did not specify a revision, performed a shallow clone, resulting in inconsistent behavior. With this update, Builds fetches the source code by revision using a shallow clone, regardless of whether you specify a revision. This fix ensures consistent clone behavior, improves build performance, and reduces disk and network usage.
1.2.3. Known issues
There are no known issues in this release.