Problem:

Builds for OpenShift (Shipwright) offers Shipwright builds for building images on OpenShift but it's not available as a choice in the import flows. Furthermore, BuildConfigs could be turned off through the Capabilities API in OpenShift which would prevent users from importing their applications into the cluster through the import flows, even when they have Shipwright installed on their clusters.

Goal:

As a developer, I want to use Shipwright Builds when importing applications through the import flows so that I can take advantage of Shipwright Build strategies such as buildpacks for building my application.

User should be provided the option to use Shipwright Builds when the OpenShift Builds operator is installed on the cluster.

Why is it important?

To enable developers to take advantage of new build capabilities on OpenShift.

Acceptance criteria:

1. When importing from Git, user can choose Shipwright Build strategies such as S2I, buildpack and Dockerfile (buildah) strategy for building the image

Dependencies (External/Internal):

Design Artifacts:

Exploration:

Note: