Added Oracle GraalVM for JDK 21

Author: sachin-pikle

oci-build-examples/oci_devops_build_with_graalenterprise/README.md

@@ -77,7 +77,7 @@ Allow dynamic-group  <YOUR_DynamicGroup_NAME> to use ons-topics in compartment <
 ![](images/oci_buildpipeline_managedbuild.png)
 
 - Click `Next` and provide the details.
-- In the `Build spec file path`, enter `build_spec.yaml` to use the [GraalVM Enterprise 22.x Java 17 build spec](build_spec.yaml). Alternatively, you can enter `build_spec_oracle_graalvm_jdk17.yaml` to use the [Oracle GraalVM for JDK 17 build spec](./build_spec_oracle_graalvm_jdk17.yaml) or `build_spec_oracle_graalvm_jdk20.yaml` to use the [Oracle GraalVM for JDK 20 build spec](./build_spec_oracle_graalvm_jdk20.yaml).
+- In the `Build spec file path`, enter `build_spec_oracle_graalvm_jdk21.yaml` to use [Oracle GraalVM for JDK 21](./build_spec_oracle_graalvm_jdk21.yaml) or `build_spec_oracle_graalvm_jdk17.yaml` to use [Oracle GraalVM for JDK 17](./build_spec_oracle_graalvm_jdk17.yaml). Alternatively, you can enter `build_spec.yaml` to use the legacy [GraalVM Enterprise 22.x Java 17](build_spec.yaml). 
 
 ![](images/oci_buildstage_1.png)
 
@@ -99,17 +99,17 @@ To install and use Oracle GraalVM in the DevOps build pipeline, the build specif
     ```shell
     steps:
       - type: Command
-        name: "Install Oracle GraalVM Enterprise 22.x Native Image for Java17"
+        name: "Install Oracle GraalVM for JDK 21 (Native Image and JDK)"
         command: |
-          yum -y install graalvm22-ee-17-native-image
+          yum -y install graalvm-21-native-image
     ```
 
 2. Set the JAVA_HOME environment variable.
 
     ```shell
     env:
       variables:
-        "JAVA_HOME" : "/usr/lib64/graalvm/graalvm22-ee-java17"
+        "JAVA_HOME" : "/usr/lib64/graalvm/graalvm-java21"
     ```
 
 3. Set the PATH environment variable.
@@ -139,15 +139,13 @@ To install and use Oracle GraalVM in the DevOps build pipeline, the build specif
 
 5. The executable file can be found under `target/my-app`.
 
-```markdown
-  - name: app_native_executable
-    type: BINARY
-    location: target/my-app
-```
+    ```markdown
+      - name: app_native_executable
+        type: BINARY
+        location: target/my-app
+    ```
 
-Here's the complete [build specification for GraalVM Enterprise 22.x Java 17](build_spec.yaml) file. Alternatively, you can use the 
-[build specification for Oracle GraalVM for JDK 17](./build_spec_oracle_graalvm_jdk17.yaml) or
-[build specification for Oracle GraalVM for JDK 20](./build_spec_oracle_graalvm_jdk20.yaml).
+Here's the complete [build specification for Oracle GraalVM for JDK 21](./build_spec_oracle_graalvm_jdk21.yaml). Alternatively, you can use the [build specification for Oracle GraalVM for JDK 17](./build_spec_oracle_graalvm_jdk17.yaml) or the legacy [build specification for GraalVM Enterprise 22.x Java 17](build_spec.yaml) file. 
 
 
 ## How to export the executable file outside of the build pipeline stage.
@@ -171,7 +169,7 @@ The following instructions will help you to export the `executable app file` to
 
 - Use option `Set Custom Location` as Artifact location.
 - Provide a path and version as `${BUILDRUN_HASH}`, this is to maintain immutable artifacts.
-- The variable `BUILDRUN_HASH` is derived during managed build stage and exported as an exportedVariables.You may use any other name ,but ensure to update the file [build_spec.yaml](build_spec.yaml).
+- The variable `BUILDRUN_HASH` is derived during managed build stage and exported as an exportedVariables.You may use any other name, but ensure to update the corresponding build specification file.
 - Select `Yes, substitute placeholders` as an option and click `Add`.
 
 ![](images/oci_devops_artifact_3.png)
@@ -186,7 +184,7 @@ The following instructions will help you to export the `executable app file` to
 
 
 - Use `app_native_executable` result artifact name.
-- The name `app_native_executable` is a reference to the outputArtifact defined under the the file [build_spec.yaml](build_spec.yaml).
+- The name `app_native_executable` is a reference to the outputArtifact defined under the corresponding build specification file.
 - Click `Add` and add the stage.
 
 ![](images/oci_upload_artifact.png)
@@ -217,7 +215,7 @@ The following instructions will help you to export the `executable app file` to
 ## Optional - Run build with more verbose output.
 
 - An additional build instruction file as [build_spec_verbose.yaml](build_spec_verbose.yaml)
-  can be used for more verbose output with the managed build.
+  can be used for more verbose output with the managed build. 
 - To do so, switch to `OCI DevOps project` > `OCI Build pipeline ` > Click `3 dots` on the `Managed Build` stage and click on `View details` and then `Edit Stage`.
 
 ![](images/oci_buildstage_details.png)
@@ -298,7 +296,7 @@ Contributors
 
 - Author: [Rahul M R](https://github.com/RahulMR42).
 - Collaborators: [Sachin Pikle](https://github.com/sachin-pikle)
-- Last release: July 2022
+- Last updated: July 2025
 
 ### Back to examples.
 ----

oci-build-examples/oci_devops_build_with_graalenterprise/build_spec_oracle_graalvm_jdk21.yaml

@@ -0,0 +1,44 @@
+version: 0.1
+component: build
+timeoutInSeconds: 600
+runAs: root
+shell: bash
+env:
+  exportedVariables:
+    - BUILDRUN_HASH
+  variables:
+    "JAVA_HOME" : "/usr/lib64/graalvm/graalvm-java21"
+    # PATH is a reserved variable and cannot be defined as a variable.
+    # However, PATH can be changed in a build step and the change is visible in subsequent steps.
+steps:
+  - type: Command
+    name: "Define unique  tag"
+    timeoutInSeconds: 40
+    command: |
+      export BUILDRUN_HASH=`echo ${OCI_BUILD_RUN_ID} | rev | cut -c 1-7`
+      echo "BUILDRUN_HASH: " $BUILDRUN_HASH
+
+  - type: Command
+    name: "Install Oracle GraalVM for JDK 21 (Native Image and JDK)"
+    command: |
+      yum -y install graalvm-21-native-image
+  - type: Command
+    name: "Set PATH Variable"
+    command: |
+      export PATH=$JAVA_HOME/bin:$PATH
+  # - type: Command
+  #   name: "Build a Jar"
+  #   command: |
+  #     mvn --no-transfer-progress clean package
+  - type: Command
+    name: "Build a native executable "
+    command: |
+      mvn --no-transfer-progress -Pnative -DskipTests package
+
+outputArtifacts:
+  # - name: app_jar
+  #   type: BINARY
+  #   location: target/my-app-1.0-SNAPSHOT.jar
+  - name: app_native_executable
+    type: BINARY
+    location: target/my-app

oci-build-examples/oci_devops_build_with_graalenterprise/build_spec_verbose.yaml

@@ -10,7 +10,7 @@ env:
   exportedVariables:
     - BUILDRUN_HASH
   variables:
-    "JAVA_HOME" : "/usr/lib64/graalvm/graalvm22-ee-java17"
+    "JAVA_HOME" : "/usr/lib64/graalvm/graalvm-java21"
     # PATH is a reserved variable and cannot be defined as a variable.
     # However, PATH can be changed in a build step and the change is visible in subsequent steps.
 steps:
@@ -24,15 +24,15 @@ steps:
   - type: Command
     name: "Pre-yum repo checks"
     command: |
-      printf "\n\n Contents of graal_spec.yaml file:\n $(cat graal_spec.yaml) \n\n"
+      printf "\n\n Contents of build_spec_verbose.yaml file:\n $(cat build_spec_verbose.yaml) \n\n"
       printf "Contents of /etc/pki/rpm-gpg/:\n $(ls -alh /etc/pki/rpm-gpg/) \n"     
       printf "Contents of /etc/yum.repos.d/:\n $(ls -alh /etc/yum.repos.d/) \n"
       printf "Contents of etc/yum.repos.d/oci-included-ol7.repo file:\n $(cat "etc/yum.repos.d/oci-included-ol7.repo") \n"
-      printf "Output of yum list graalvm22-ee-17* :\n $(yum list graalvm22-ee-17*) \n"
+      printf "Output of yum list graalvm-21* :\n $(yum list graalvm-21*) \n"
   - type: Command
-    name: "Install GraalVM 22.x Native Image for Java17"
+    name: "Install Oracle GraalVM for JDK 21 (Native Image and JDK)"
     command: |
-      yum -y install graalvm22-ee-17-native-image
+      yum -y install graalvm-21-native-image
   - type: Command
     name: "Set PATH Variable"
     command: |
@@ -49,7 +49,7 @@ steps:
       printf "Maven version:\n $(mvn --version) \n"
       echo "Current dir: $(pwd)"
       printf "Current dir contents:\n $(ls -alh)"
-      printf "Output of yum list graalvm22-ee-17* :\n $(yum list graalvm22-ee-17*) \n"
+      printf "Output of yum list graalvm-21* :\n $(yum list graalvm-21*) \n"
   - type: Command
     name: "Build a Jar"
     command: |