Skip to content

[OPENJDK-3632] update templates/jlink/README.md to reflect all buildConfigs auto-trigger #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 19, 2025
Merged

[OPENJDK-3632] update templates/jlink/README.md to reflect all buildConfigs auto-trigger #551

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions templates/jlink/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,19 +75,19 @@ See all the OpenShift objects that were created:

## Stage 3: Kick off builds

There will be three BuildConfigs, called something like
Instantiating the template will cause 3 separate BuildConfigs to be created and will automatically start their builds in sequence:

1. jlink-builder-jdk-17
2. jlink-s2i-jdk-17
3. multistage-buildconfig
1. $APPNAME-jlink-builder-jdk-$JDK_VERSION
2. $APPNAME-jlink-s2i-jdk-$JDK_VERSION
3. $APPNAME-multistage-buildconfig

Start a build for (1). Once complete, builds for (2) and (3) should be
automatically triggered in sequence.
Where $APPNAME and $JDK_VERSION are the paremeters initially passed to the template.

A build will automatically start for (1). Once complete, builds for (2) and (3) should be automatically triggered in sequence.

## Stage 4: create deployment

The ImageStreamTag `lightweight-image:latest` will be populated with the new
application container image.
The ImageStreamTag `$APPNAME-lightweight-image:latest` will be populated with the new application container image.

Create a deployment to see it work. E.g., in the Developer Perspective, select
"+Add", "Container Images", "Image stream tag from internal registry", ...,
Expand Down