In BuildConfig, which strategy uses a builder image to assemble application code?

In BuildConfig, which strategy uses a builder image to assemble application code?

• A. Source-to-Image (S2I) strategy
• B. Docker strategy
• C. Git strategy
• D. Binary strategy

Answer: (A)

Source-to-Image builds rely on a builder image that contains the language runtime and the build tools. In this approach, OpenShift takes your source code, injects it into the builder image, and runs the image’s assemble script to create the final runnable image. This reuse of a dedicated builder image lets you tailor builds by simply swapping the builder for a different language or framework, without altering your source or build steps. In contrast, a Docker strategy builds from a Dockerfile, not from an external builder image executing an assemble process; a Binary strategy uses prebuilt artifacts without an assemble step; and a Git strategy pulls code from a repository and relies on the repository’s own build logic rather than a standardized builder image. So the builder-image–driven assembly is the hallmark of the Source-to-Image strategy.

Source-to-Image builds rely on a builder image that contains the language runtime and the build tools. In this approach, OpenShift takes your source code, injects it into the builder image, and runs the image’s assemble script to create the final runnable image. This reuse of a dedicated builder image lets you tailor builds by simply swapping the builder for a different language or framework, without altering your source or build steps. In contrast, a Docker strategy builds from a Dockerfile, not from an external builder image executing an assemble process; a Binary strategy uses prebuilt artifacts without an assemble step; and a Git strategy pulls code from a repository and relies on the repository’s own build logic rather than a standardized builder image. So the builder-image–driven assembly is the hallmark of the Source-to-Image strategy.