[KOGITO-710] - Prepare Kogito 0.6.0 images release (#71)

Signed-off-by: Filippe Spolti <[email protected]>
apache · Dec 9, 2019 · 9de4f65 · 9de4f65
1 parent 506869d
commit 9de4f65
Show file tree

Hide file tree

Showing 6 changed files with 28 additions and 28 deletions.
diff --git a/s2i/kogito-imagestream.yaml b/s2i/kogito-imagestream.yaml
@@ -136,18 +136,18 @@ items:
   metadata:
     name: kogito-data-index
     annotations:
-      openshift.io/display-name: Runtime image for the Kogito Data Index Service
+      openshift.io/display-name: Runtime image for the Kogito Data Index Service - Tech preview
       openshift.io/provider-display-name: Kie Group.
   spec:
     tags:
-      - name: '0.6.0'
+      - name: '0.6.0-TP'
         annotations:
-          description: Runtime image for the Kogito Jobs Service
+          description: Runtime image for the Kogito Jobs Service - Tech preview
           iconClass: icon-jbpm
           tags: kogito,jobs-service
-          version: '0.6.0'
+          version: '0.6.0-TP'
         referencePolicy:
           type: Local
         from:
           kind: DockerImage
-          name: quay.io/kiegroup/kogito-jobs-service:0.6.0
+          name: quay.io/kiegroup/kogito-jobs-service:0.6.0-TP
diff --git a/s2i/modules/kogito-data-index/module.yaml b/s2i/modules/kogito-data-index/module.yaml
@@ -3,9 +3,9 @@ name: org.kie.kogito.dataindex
 version: "0.6.0"
 
 artifacts:
-- name: data-index-service-8.0.0-SNAPSHOT-runner.jar
-  url: https://repository.jboss.org/org/kie/kogito/data-index-service/8.0.0-SNAPSHOT/data-index-service-8.0.0-20191203.211509-90-runner.jar
-  md5: bf541da0f17e2c783385c0cfe968cfd0
+- name: data-index-service-0.6.0-runner.jar
+  url: https://repository.jboss.org/org/kie/kogito/data-index-service/0.6.0/data-index-service-0.6.0-runner.jar
+  md5: ce2ef31e37255450d2f3bc891ab66475
 
 execute:
 - script: configure
diff --git a/s2i/tests/features/kogito-data-index.feature b/s2i/tests/features/kogito-data-index.feature
@@ -14,7 +14,7 @@ Feature: Kogito-data-index feature.
 
   Scenario: verify if the binary index is available on /home/kogito
     When container is started with command bash
-    Then run sh -c 'ls /home/kogito/bin/data-index-service-*-runner.jar' in container and immediately check its output for /home/kogito/bin/data-index-service-8.0.0-SNAPSHOT-runner.jar
+    Then run sh -c 'ls /home/kogito/bin/data-index-service-*-runner.jar' in container and immediately check its output for /home/kogito/bin/data-index-service-0.6.0-runner.jar
 
   Scenario: Verify data-index default configuration
     When container is started with env

diff --git a/s2i/tests/features/kogito-quarkus-ubi8-s2i.feature b/s2i/tests/features/kogito-quarkus-ubi8-s2i.feature
@@ -2,7 +2,7 @@
 Feature: kogito-quarkus-ubi8-s2i image tests
 
   Scenario: Verify if the s2i build is finished as expected and if it is listening on the expected port
-    Given s2i build /tmp/kogito-examples from drools-quarkus-example using 0.5.1 and runtime-image quay.io/kiegroup/kogito-quarkus-ubi8:latest
+    Given s2i build /tmp/kogito-examples from drools-quarkus-example using 0.6.0 and runtime-image quay.io/kiegroup/kogito-quarkus-ubi8:latest
       | variable       | value                     |
       | LIMIT_MEMORY   | 2147483648                |
     Then check that page is served
@@ -11,13 +11,13 @@ Feature: kogito-quarkus-ubi8-s2i image tests
       | path            | /hello                   |
       | wait            | 80                       |
       | expected_phrase | Mario is older than Mark |
-    And file /home/kogito/bin/drools-quarkus-example-0.5.1-runner should exist
+    And file /home/kogito/bin/drools-quarkus-example-0.6.0-runner should exist
     And file /home/kogito/ssl-libs/libsunec.so should exist
     And file /home/kogito/cacerts should exist
     And s2i build log should contain -J-Xmx1717986918
 
   Scenario: Verify if the s2i build is finished as expected performing a non native build
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from drools-quarkus-example using 0.5.1 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from drools-quarkus-example using 0.6.0 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
       | variable            | value                     |
       | NATIVE              | false                     |
       | JAVA_OPTIONS        | -Dquarkus.log.level=DEBUG |
@@ -27,12 +27,12 @@ Feature: kogito-quarkus-ubi8-s2i image tests
       | path            | /hello                   |
       | wait            | 80                       |
       | expected_phrase | Mario is older than Mark |
-    And file /home/kogito/bin/drools-quarkus-example-0.5.1-runner.jar should exist
+    And file /home/kogito/bin/drools-quarkus-example-0.6.0-runner.jar should exist
     And container log should contain DEBUG [io.qua.
     And run sh -c 'echo $JAVA_OPTIONS' in container and immediately check its output for -Dquarkus.log.level=DEBUG
 
   Scenario: Verify if the s2i build is finished as expected performing a non native build and if it is listening on the expected port
-    Given s2i build /tmp/kogito-examples from drools-quarkus-example using 0.5.1 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
+    Given s2i build /tmp/kogito-examples from drools-quarkus-example using 0.6.0 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
       | variable | value |
       | NATIVE   | false |
     Then check that page is served
@@ -41,10 +41,10 @@ Feature: kogito-quarkus-ubi8-s2i image tests
       | path            | /hello                   |
       | wait            | 80                       |
       | expected_phrase | Mario is older than Mark |
-    And file /home/kogito/bin/drools-quarkus-example-0.5.1-runner.jar should exist
+    And file /home/kogito/bin/drools-quarkus-example-0.6.0-runner.jar should exist
 
     Scenario: Verify if the multi-module s2i build is finished as expected performing a non native build and if it is listening on the expected port
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from . using 0.5.1 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from . using 0.6.0 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
       | variable          | value                           |
       | NATIVE            | false                           |
       | ARTIFACT_DIR      | drools-quarkus-example/target   |
@@ -55,17 +55,17 @@ Feature: kogito-quarkus-ubi8-s2i image tests
       | path            | /hello                   |
       | wait            | 80                       |
       | expected_phrase | Mario is older than Mark |
-    And file /home/kogito/bin/drools-quarkus-example-0.5.1-runner.jar should exist
+    And file /home/kogito/bin/drools-quarkus-example-0.6.0-runner.jar should exist
 
   Scenario: Perform a incremental s2i build
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from drools-quarkus-example with env and incremental using 0.5.1
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from drools-quarkus-example with env and incremental using 0.6.0
       | variable          | value                  |
       | NATIVE            | false                  |
     Then s2i build log should not contain WARNING: Clean build will be performed because of error saving previous build artifacts
 
   # Since the same image is used we can do a subsequent incremental build and verify if it is working as expected.
   Scenario: Perform a second incremental s2i build
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from drools-quarkus-example with env and incremental using 0.5.1
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from drools-quarkus-example with env and incremental using 0.6.0
       | variable          | value    |
       | NATIVE            | false    |
     Then s2i build log should contain Expanding artifacts from incremental build...
@@ -95,7 +95,7 @@ Feature: kogito-quarkus-ubi8-s2i image tests
     And run sh -c 'echo $GRAALVM_VERSION' in container and immediately check its output for 19.2.1
 
   Scenario: Verify that the Kogito Maven archetype is generating the project and compiling it correctly
-    Given s2i build /tmp/kogito-examples from dmn-quarkus-example using 0.5.1 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
+    Given s2i build /tmp/kogito-examples from dmn-quarkus-example using 0.6.0 and runtime-image quay.io/kiegroup/kogito-quarkus-jvm-ubi8:latest
       | variable          | value                           |
       | NATIVE            | false                           |
       | KOGITO_VERSION    | 8.0.0-SNAPSHOT                  |

diff --git a/s2i/tests/features/kogito-springboot-ubi8-s2i.feature b/s2i/tests/features/kogito-springboot-ubi8-s2i.feature
@@ -3,7 +3,7 @@
 Feature: kogito-springboot-ubi8-s2i image tests
 
   Scenario: Verify if the s2i build is finished as expected
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from jbpm-springboot-example using 0.5.1 and runtime-image quay.io/kiegroup/kogito-springboot-ubi8:latest
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from jbpm-springboot-example using 0.6.0 and runtime-image quay.io/kiegroup/kogito-springboot-ubi8:latest
       | variable            | value        |
       | JAVA_OPTIONS        | -Ddebug=true |
     Then check that page is served
@@ -12,12 +12,12 @@ Feature: kogito-springboot-ubi8-s2i image tests
       | path                 | /orders/1 |
       | wait                 | 80        |
       | expected_status_code | 204       |
-    And file /home/kogito/bin/jbpm-springboot-example-0.5.1.jar should exist
+    And file /home/kogito/bin/jbpm-springboot-example-0.6.0.jar should exist
     And container log should contain DEBUG o.s.boot.SpringApplication.load
     And run sh -c 'echo $JAVA_OPTIONS' in container and immediately check its output for -Ddebug=true
 
   Scenario: Verify if the s2i build is finished as expected using multi-module build
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from . using 0.5.1 and runtime-image quay.io/kiegroup/kogito-springboot-ubi8:latest
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from . using 0.6.0 and runtime-image quay.io/kiegroup/kogito-springboot-ubi8:latest
       | variable            | value                           |
       | JAVA_OPTIONS        | -Ddebug=true                    |
       | ARTIFACT_DIR        | jbpm-springboot-example/target   |
@@ -28,23 +28,23 @@ Feature: kogito-springboot-ubi8-s2i image tests
       | path                 | /orders/1 |
       | wait                 | 80        |
       | expected_status_code | 204       |
-    And file /home/kogito/bin/jbpm-springboot-example-0.5.1.jar should exist
+    And file /home/kogito/bin/jbpm-springboot-example-0.6.0.jar should exist
     And container log should contain DEBUG o.s.boot.SpringApplication.load
     And run sh -c 'echo $JAVA_OPTIONS' in container and immediately check its output for -Ddebug=true
 
   Scenario: Scenario: Perform a incremental s2i build
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from jbpm-springboot-example with env and incremental using 0.5.1
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from jbpm-springboot-example with env and incremental using 0.6.0
     Then check that page is served
       | property             | value     |
       | port                 | 8080      |
       | path                 | /orders/1 |
       | wait                 | 80        |
       | expected_status_code | 204       |
-    And file /home/kogito/bin/jbpm-springboot-example-0.5.1.jar should exist
+    And file /home/kogito/bin/jbpm-springboot-example-0.6.0.jar should exist
 
   # Since the same image is used we can do a subsequent incremental build and verify if it is working as expected.
   Scenario: Perform a second incremental s2i build
-    Given s2i build https://github.com/kiegroup/kogito-examples.git from jbpm-springboot-example with env and incremental using 0.5.1
+    Given s2i build https://github.com/kiegroup/kogito-examples.git from jbpm-springboot-example with env and incremental using 0.6.0
     Then s2i build log should contain Expanding artifacts from incremental build...
     And s2i build log should not contain WARNING: Clean build will be performed because of error saving previous build artifacts
 

diff --git a/s2i/tests/test-apps/clone-repo.sh b/s2i/tests/test-apps/clone-repo.sh
@@ -8,7 +8,7 @@ rm -rf kogito-examples/
 git clone https://github.com/kiegroup/kogito-examples.git
 cd kogito-examples/drools-quarkus-example
 git fetch origin --tags
-git checkout -b 0.5.1 0.5.1
+git checkout -b 0.6.0 0.6.0
 
 # by adding the application.properties file telling quarkus to start on
 # port 10000, the purpose of this tests is make sure that the images