You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: oci-build-examples/oci_devops_build_with_graalenterprise/README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Using GraalVM Enterprise in OCI DevOps Build Pipelines
1
+
# Using GraalVM Enterprise in OCI DevOps Build Pipelines to build a Java App
2
2
3
3
This sample shows how to use `Oracle GraalVM Enterprise Edition` in `OCI DevOps build pipelines` to build a Java hello world application. You can use this approach to build any high-performance Java application with GraalVM Enterprise and OCI DevOps.
4
4
@@ -28,7 +28,7 @@ This sample shows how to use `Oracle GraalVM Enterprise Edition` in `OCI DevOps
28
28
29
29
- Create an OCI build pipeline.
30
30
- Make a build using Oracle GraalVM Enterprise edition.
31
-
- Here the focus will be on Build instructions and OCI build pipeline
31
+
- Here the focus will be on the build specification and DevOps build pipeline
32
32
33
33
34
34
## Procedure to use this illustration.
@@ -56,8 +56,6 @@ ALL {resource.type = 'devopsrepository', resource.compartment.id = 'COMPARMENT O
56
56
```markdown
57
57
Allow dynamic-group "NAME OF THE DynamicGroup" to manage repos in compartment "COMPARTMENT NAME"
58
58
Allow dynamic-group "NAME OF THE DynamicGroup" to use ons-topics in compartment "COMPARTMENT NAME"
59
-
60
-
Allow dynamic-group "NAME OF THE DynamicGroup" to manage repos in compartment "COMPARTMENT NAME"
61
59
```
62
60
63
61
- Switch back to OCI DevOps Project and create an OCI Code repo - https://docs.oracle.com/en-us/iaas/Content/devops/using/create_repo.htm#create_repo
@@ -68,7 +66,7 @@ Allow dynamic-group "NAME OF THE DynamicGroup" to manage repos in compartment "C
68
66
69
67

70
68
71
-
- You may use other support version control repos as well (like Github.com,Bitbucket.com, Bitbucket Cloud etc). You may also need to adjust the policies according to connection and setup external connections accordingly - https://docs.oracle.com/en-us/iaas/Content/devops/using/create_connection.htm
69
+
- You may use other supported version control repos as well (like Github.com,Bitbucket.com, Bitbucket Cloud, etc.). You may also need to adjust the policies according to the connection and setup external connections accordingly - https://docs.oracle.com/en-us/iaas/Content/devops/using/create_connection.htm
72
70
73
71
- Create a new build pipeline. - https://docs.oracle.com/en-us/iaas/Content/devops/using/create_buildpipeline.htm
74
72
@@ -93,14 +91,14 @@ Allow dynamic-group "NAME OF THE DynamicGroup" to manage repos in compartment "C
93
91
94
92
## Take a closer look at the build instructions below
95
93
96
-
To install and use GraalVM Enterprise in the DevOps build pipeline, the build specification file is as follows:
94
+
To install and use GraalVM Enterprise in the DevOps build pipeline, the build specification file is as follows:
97
95
98
96
1. Add the following command to install one or more required GraalVM Enterprise components. For example, this command installs Native Image along with the Java Development Kit (JDK) and other necessary dependencies.
99
97
100
98
```shell
101
99
steps:
102
100
- type: Command
103
-
name: "Install GraalVM 22.x Native Image for Java17"
101
+
name: "Install GraalVM Enterprise 22.x Native Image for Java17"
104
102
command: |
105
103
yum -y install graalvm22-ee-17-native-image
106
104
```
@@ -138,16 +136,17 @@ To install and use GraalVM Enterprise in the DevOps build pipeline, the build s
Here's the complete [build specification](build_spec.yaml) file.
142
-
143
-
5. The executable file can be found under path target/my-app.
139
+
5. The executable file can be found under `target/my-app`.
144
140
145
141
```markdown
146
142
- name: app_native_executable
147
143
type: BINARY
148
144
location: target/my-app
149
145
```
150
146
147
+
Here's the complete [build specification](build_spec.yaml) file.
148
+
149
+
151
150
## How to export the executable file outside of the build pipeline stage.
152
151
153
152
The following instructions will help you to export the `executable app file` to OCI Artifactory and which can then be used in the further stage including deployment pipelines.
@@ -174,7 +173,7 @@ The following instructions will help you to export the `executable app file` to
174
173
175
174

176
175
177
-
- Under `Build pipeline` use the `+` icon after the current stage and add a new stage named `Deliver artifacts`
176
+
- Under `Build pipeline` use the `+` icon after the current stage and add a new stage named `Deliver artifacts`
178
177
179
178

180
179
@@ -210,7 +209,7 @@ The following instructions will help you to export the `executable app file` to
210
209
211
210

212
211
213
-
- The exported executable can be used on any of the supporting infrastructures to execute or can use to deploy via `OCI deployment pipeline` to compute, container or functionresources.
212
+
- The exported executable can be used on any of the supporting infrastructures to execute or can use to deploy via `OCI deployment pipeline` to compute, container or functionresources.
214
213
215
214
## Optional - Run build with more verbose output.
216
215
@@ -220,13 +219,13 @@ The following instructions will help you to export the `executable app file` to
220
219
221
220

222
221
223
-
- Change `Build spec file path` as `build_spec_verbose.yaml` and `Save changes`
222
+
- Change `Build spec file path` as `build_spec_verbose.yaml` and `Save changes`
224
223
225
224

226
225
227
-
- Do another manal run for the build pipeline and you will see more verbose build logs.
226
+
- Do another manual run for the build pipeline and you will see more verbose build logs.
228
227
229
-
## Sample Build Logs (Non-verbose mode)
228
+
## Sample Build Logs
230
229
231
230
1. The `yum install` build log statements should be similar to:
232
231
@@ -287,7 +286,8 @@ The following instructions will help you to export the `executable app file` to
0 commit comments