Where in the application source code do you place S2I scripts to override the build process?

Unlock all questions

This demo includes only 20 questions. Upgrade to access hundreds of questions, flashcards, exam simulations, and disable ads.

Full question bankExam simulationsFlashcards
From $25.99Unlock all

Prepare for the Red Hat Openshift Developer EX288 Exam. Study with comprehensive quizzes and flashcards. Each question includes hints and explanations to enhance your understanding. Ace your exam with confidence!

Multiple Choice

Where in the application source code do you place S2I scripts to override the build process?

Explanation:
Place your override scripts in a hidden directory at the root of the application source named .s2i/bin. S2I looks for these scripts there and uses them in place of the builder image’s defaults, so you can customize steps like assemble and run for your specific build. The scripts should be named the standard S2I script names and be executable. The other locations don’t get picked up by S2I for overriding build behavior: s2i/bin is not the override path, .docker/s2i isn’t recognized by S2I, and scripts/.s2i isn’t the conventional location for overrides.

Place your override scripts in a hidden directory at the root of the application source named .s2i/bin. S2I looks for these scripts there and uses them in place of the builder image’s defaults, so you can customize steps like assemble and run for your specific build. The scripts should be named the standard S2I script names and be executable.

The other locations don’t get picked up by S2I for overriding build behavior: s2i/bin is not the override path, .docker/s2i isn’t recognized by S2I, and scripts/.s2i isn’t the conventional location for overrides.

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy