Skip to content

Commit 6eba225

Browse files
committed
README.md: indent code lines, remove ref to namespaces
Signed-off-by: Jonathan Dowland <[email protected]>
1 parent 612d017 commit 6eba225

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

templates/jlink/jlink-builder/README.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -12,45 +12,45 @@ Steps to produce the imagestream and image:
1212

1313
1. Switch to the openshift project and install the template
1414

15-
oc project openshift
16-
oc create -f templates/jlink/jlink-builder/jlink-builder-template.yaml
15+
oc project openshift
16+
oc create -f templates/jlink/jlink-builder/jlink-builder-template.yaml
1717

1818
This will create a Template called jlink-builder-template, you should see
1919

20-
template.template.openshift.io/jlink-builder-template created
20+
template.template.openshift.io/jlink-builder-template created
2121

2222
and after running oc get template, it should be in the list as
2323

24-
jlink-builder-template Template to produce an imagestream and buildconfig for a Jlink builder image 1 (all set) 2
24+
jlink-builder-template Template to produce an imagestream and buildconfig for a Jlink builder image 1 (all set) 2
2525

2626
2. Set the parameters and create the imagestream and buildconfig from the template.
2727

2828
The template for now defines a single parameter, JDK_VERSION. Setting this will set the version of the builder image used in the BuildConfig. Currently suppoted values are 11, 17, and 21. By default this will be 11.
2929

30-
oc process --parameters jlink-builder-template
31-
32-
NAME DESCRIPTION GENERATOR VALUE
33-
JDK_VERSION JDK version to produce a jmods image for 11
30+
oc process --parameters jlink-builder-template
31+
32+
NAME DESCRIPTION GENERATOR VALUE
33+
JDK_VERSION JDK version to produce a jmods image for 11
3434

3535
In order to set the JDK version, you will need to use the -p flag of oc process. To process the template and create the imagestreams, simply run
3636

37-
oc process -n openshift jlink-builder-template -p JDK_VERSION=11 | oc create -f -
38-
39-
imagestream.image.openshift.io/ubi9-openjdk-11-jlink created
40-
buildconfig.build.openshift.io/jlink-builder-jdk-11 created
37+
oc process -n openshift jlink-builder-template -p JDK_VERSION=11 | oc create -f -
38+
39+
imagestream.image.openshift.io/ubi9-openjdk-11-jlink created
40+
buildconfig.build.openshift.io/jlink-builder-jdk-11 created
4141

4242
3. Start and observe the build
4343

4444
Start the build using
4545

46-
oc start-build jlink-builder-jdk-11
47-
48-
build.build.openshift.io/jlink-builder-jdk-11-1 started
46+
oc start-build jlink-builder-jdk-11
47+
48+
build.build.openshift.io/jlink-builder-jdk-11-1 started
4949

5050
Then observe it by using
5151

52-
oc logs -f bc/jlink-builder-jdk-11
52+
oc logs -f bc/jlink-builder-jdk-11
5353

5454
## Stage 2: build and analyse application with OpenShift source-to-image (S2I)
5555

56-
TODO
56+
TODO

0 commit comments

Comments
 (0)