Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Release notes

builds for Red Hat OpenShift 1.5

Highlights of what is new and what has changed with this OpenShift Builds release

Red Hat OpenShift Documentation Team

Abstract

The release notes for OpenShift Builds summarize all new features and enhancements, notable technical changes, major corrections from the previous version, and any known bugs upon general availability.

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.

1.1. Compatibility and support matrix
Copy link

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.

Expand
Table 1.1. Compatibility and support matrix
Builds VersionComponent VersionCompatible Openshift Pipelines VersionOpenShift VersionSupport

Operator

Builds (Shipwright)

CLI

   

1.5

0.16.0 (GA)

0.16.0 (GA)

1.17, 1.18, 1.19 and 1.20

4.16, 4.17, 4.18, and 4.19

GA

1.4

0.15.0 (GA)

0.15.0 (GA)

1.16, 1.17, 1.18 and 1.19

4.15, 4.16, 4.17, and 4.18

GA

1.2. Release notes for Builds 1.5.1
Copy link

Builds 1.5.1 is now available on OpenShift Container Platform 4.19.

1.2.1. New features
Copy link

The following sections highlight what is new in Builds 1.5.1.

  • With this update, Builds deployment is FIPS compliant, ensuring that all the cryptographic modules and algorithms meet the security requirements.

1.2.2. Fixed issues
Copy link

The following list highlights fixed issues in Builds 1.5.1.

  • Before this update, adding volumes to Build and Buildrun custom resources (CR) failed due to empty fields in the Custom Resource Definition (CRD). With this update, the empty fields in the CRD are removed.
  • Before this update, using ExtKeyUsageAny field in an x509 certificate disabled policy validation in crypto/x509. This affected certificate chains that contain policy graphs. With this update, using ExtKeyUsageAny field does not disable the policy validation. CVE-2025-22874
  • Before this update, the correct build container images were not pulled in a disconnected cluster because the image SHAs were not synchronized. With this fix, the SHAs of the images are updated and synced between the operator bundle and the build strategies. This ensures that correct build container images are pulled in a disconnected cluster.

1.3. Release notes for Builds 1.5
Copy link

Builds 1.5 is now available on OpenShift Container Platform 4.16, 4.17, 4.18, and 4.19.

1.3.1. New features
Copy link

The following sections highlight what is new in Builds 1.5.

  • With this update, Builds for Red Hat OpenShift Operator deploys Shipwright v0.16 components.
  • With this update, you can use the optional .spec.nodeSelector value with shp CLI to specify the nodes on which build run pods should run.
  • With this update, you can use the optional --scheduler-name flag with shp CLI to specify the scheduler for scheduling build run pods.

  • With this update, the following two buildpacks ClusterBuildStrategy options are available for Builds:

    • buildpacks strategy

    • buildpacks-extender strategy

      Note

      The buildpacks-extender strategy is compatible with the experimental buildpacks extender lifecycle phase. You can use this strategy, for example, for builds based on Node.js. However, the extender phase does not support Quarkus, or any other Java-based builds. For such builds, use the buildpacks strategy instead.

      These strategies introduce new features, enhance compliance with Cloud Native Buildpacks (CNB) 0.12 specifications, and improve the overall stability and usability of the ClusterBuildStrategy buildpacks.

      Important

      Buildpacks is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

      For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

  • With this update, the source.git.depth parameter was added to the Build resource to specify the depth of the Git history. The default value is 1, meaning no history is cloned. This method provides fastest way to clone a Git repository and is suitable for all cases where your build logic doesn’t rely on Git history.

    Any value greater than 1 will create a clone with the specified depth. For a full Git history clone, set the depth to 0.

    Note

    If you specify a commit SHA as a revision, the full history is always cloned before this commit is checked out.

1.3.2. Fixed issues
Copy link

The following list highlights fixed issues in Builds 1.5.

  • Before this update, the build controller had permission to modify CustomResourceDefinitions. This caused the controller to have excessive permissions, resulting in a minor security risk. With this update, the issue is fixed. Before this update, if the Builds for Red Hat OpenShift Operator failed to reconcile the ShipwrightBuild or SharedResource objects but the status update of the build controller succeeded, the controller was not requeued for reconciliation. With this update, the issue is resolved, and the controller is correctly requeued for reconciliation after a failure.

1.3.3. Deprecated features
Copy link

The following section highlights deprecated features in Builds 1.5.

  • With this update, the following channels are deprecated:

    • builds-1.3

Instead, use the builds-1.5 channel.

Legal Notice
Copy link

Copyright © 2025 Red Hat

OpenShift documentation is licensed under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0).

Modified versions must remove all Red Hat trademarks.

Portions adapted from https://github.com/kubernetes-incubator/service-catalog/ with modifications by Red Hat.

Red Hat, Red Hat Enterprise Linux, the Red Hat logo, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the United States and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.

Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat