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
Scenario: run the s2i and check the maven mirror, proxy (including username and password) and non proxy have been initialised in the default settings.xml, uses http_proxy
24
-
Given s2i build https://github.com/jboss-openshift/openshift-examples from spring-boot-sample-simple
24
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from spring-boot-sample-simple
# proxy auth configuration (fail case: no password supplied)
35
35
Scenario: run the s2i and check the maven mirror, proxy (including username) and non proxy have been initialised in the default settings.xml, uses http_proxy
36
-
Given s2i build https://github.com/jboss-openshift/openshift-examples from spring-boot-sample-simple
36
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from spring-boot-sample-simple
Scenario: run the s2i and check the maven mirror, proxy (including username and password) and non proxy have been initialised in the default settings.xml, uses https_proxy
86
-
Given s2i build https://github.com/jboss-openshift/openshift-examples from spring-boot-sample-simple
86
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from spring-boot-sample-simple
# https proxy auth configuration (fail case: no password supplied)
97
97
Scenario: run the s2i and check the maven mirror, proxy (including username) and non proxy have been initialised in the default settings.xml, uses https_proxy
98
-
Given s2i build https://github.com/jboss-openshift/openshift-examples from spring-boot-sample-simple
98
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from spring-boot-sample-simple
Then XML file /tmp/artifacts/configuration/settings.xml should have 1 elements on XPath //ns:proxy[ns:id='genproxy'][ns:active='true'][ns:protocol='https'][ns:host='127.0.0.1'][ns:port='8080']
106
106
107
107
Scenario: run s2i assemble and check no_proxy is honoured with multiple entries
108
-
Given s2i build https://github.com/jboss-openshift/openshift-examples from spring-boot-sample-simple
108
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from spring-boot-sample-simple
Then XML file /tmp/artifacts/configuration/settings.xml should have 1 elements on XPath //ns:profile[ns:id='myrepo-profile']/ns:repositories/ns:repository[ns:url='http://repo.example.com:8080/maven2/']
170
170
171
171
Scenario: Ensure the environment is cleaned when executing mvn (OPENJDK-1549)
172
-
Given s2i build https://github.com/jboss-container-images/openjdk from tests/OPENJDK-1549 with env using ubi9
172
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from OPENJDK-1549 with env
Copy file name to clipboardExpand all lines: tests/features/java/openjdk_s2i.feature
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -4,16 +4,16 @@
4
4
@ubi9/openjdk-21
5
5
Feature: Openshift OpenJDK-only S2I tests
6
6
Scenario: Check java perf dir owned by default (CLOUD-2070, OPENJDK-91)
7
-
Given s2i build https://github.com/jboss-openshift/openshift-quickstarts from undertow-servlet
7
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from undertow-servlet
8
8
Then run jstat -gc 1 1000 1 in container and check its output for S0C
9
9
And run stat --printf="%U %G" /tmp/hsperfdata_default/ in container and check its output for default root
10
10
11
11
Scenario: Ensure Quarkus CDS doesn't fail due to timestamp mismatch (OPENDJK-1673)
12
-
Given s2i build https://github.com/jerboaa/quarkus-quickstarts from getting-started using quickstart-2.16-s2i-cds
12
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from getting-started
13
13
Then container log should not contain A jar file is not the one used while building the shared archive file
14
14
15
15
Scenario: quarkus fast-jar layout works out-of-the-box (OPENJDK-631)
16
-
Given s2i build https://github.com/jmtd/openshift-quickstarts from quarkus-quickstarts/getting-started-3.0.1.Final-nos2i using OPENJDK-631-quarkus-fast-jar
16
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from quarkus-quickstarts/getting-started-3.0.1.Final-nos2i
17
17
Then container log should contain INFO quarkus fast-jar package type detected
18
18
And container log should contain -jar /deployments/quarkus-app/quarkus-run.jar
19
19
And container log should contain (main) getting-started 1.0.0-SNAPSHOT on JVM (powered by Quarkus
And container log should not contain no main manifest attribute
23
23
24
24
Scenario: quarkus uber-jar layout works out-of-the-box (OPENJDK-631)
25
-
Given s2i build https://github.com/jmtd/openshift-quickstarts from quarkus-quickstarts/getting-started-3.0.1.Final-nos2i with env using OPENJDK-631-quarkus-fast-jar
25
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from quarkus-quickstarts/getting-started-3.0.1.Final-nos2i with env
26
26
| variable | value |
27
27
| QUARKUS_PACKAGE_TYPE | uber-jar |
28
28
Then container log should not contain INFO quarkus fast-jar package type detected
Copy file name to clipboardExpand all lines: tests/features/java/runtime.feature
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
Feature: Openshift OpenJDK Runtime tests
5
5
6
6
Scenario: Ensure JAVA_ARGS is passed through, diagnostic options work correctly, JVM_ARGS not present in run script, OPENJDK-474 JAVA_ARGS not repeated
7
-
Given s2i build https://github.com/jboss-openshift/openshift-quickstarts from undertow-servlet
7
+
Given s2i build https://github.com/jboss-container-images/openjdk-test-applications from undertow-servlet
0 commit comments