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.
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.
Builds Version | Component Version | Compatible Openshift Pipelines Version | OpenShift Version | Support | |
---|---|---|---|---|---|
Operator |
Builds (Shipwright) |
CLI |
|||
1.1 |
0.13.0 (GA) |
0.13.0 (GA) |
1.13, 1.14, and 1.15 |
4.12, 4.13, 4.14, 4.15, and 4.16 |
GA |
1.0 |
0.12.0 (GA) |
0.12.0 (GA) |
1.12, 1.13, 1.14, and 1.15 |
4.12, 4.13, 4.14, 4.15, and 4.16 |
GA |
1.2 |
GA |
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.