September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24764: ------------------------------- Attachment: dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png, fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png, fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24764: ------------------------------------ After using the new settings.xml and updating the job to look nearly the same as the fusesource version we get ... the same test failures. {code} 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.projecttemplates.tests.integration: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.jmx.camel.tests.integration: An unexpected error occured while launching the test runtime (return code 1). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.server.tests: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.fuse.ui.bot.tests: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24764 at 9/22/17 1:06 PM: ------------------------------------------------------------- After using the new settings.xml and updating the job to look nearly the same as the fusesource version we get ... the same test failures. {code} 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.projecttemplates.tests.integration: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.jmx.camel.tests.integration: An unexpected error occured while launching the test runtime (return code 1). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.server.tests: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.fuse.ui.bot.tests: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was (Author: nickboldt): After using the new settings.xml and updating the job to look nearly the same as the fusesource version we get ... the same test failures. {code} 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.projecttemplates.tests.integration: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.jmx.camel.tests.integration: An unexpected error occured while launching the test runtime (return code 1). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.fusesource.ide.server.tests: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] 17:01:14 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.0.0:test (default-test) on project org.jboss.tools.fuse.ui.bot.tests: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1] {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > Attachments: fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25074) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25074?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25074. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [central] > ----------------------------------------------------------------- > > Key: JBIDE-25074 > URL: https://issues.jboss.org/browse/JBIDE-25074 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [central]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25081) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [livereload]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25081?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25081. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [livereload] > -------------------------------------------------------------------- > > Key: JBIDE-25081 > URL: https://issues.jboss.org/browse/JBIDE-25081 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [livereload]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for livereload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25079) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [jsf]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25079?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25079. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [jsf] > ------------------------------------------------------------- > > Key: JBIDE-25079 > URL: https://issues.jboss.org/browse/JBIDE-25079 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsf > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [jsf]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for jsf task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25080) For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [jst]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25080?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25080. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM3: Prepare for 4.5.1.AM3 / 11.1.0.AM3 [jst] > ------------------------------------------------------------- > > Key: JBIDE-25080 > URL: https://issues.jboss.org/browse/JBIDE-25080 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > For JBIDE 4.5.1.AM3 [jst]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.1.AM3-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM3-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.3.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.3.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.71.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.71.0.AM3-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for jst task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25093) IT: create tests for the

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25093: ------------------------------------- Description: in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk: !image-2017-09-22-17-35-34-902.png! We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046). We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered. was: in JBIDE-24994 we introduced the ability to look up the docker registry in the cdk: !image-2017-09-22-17-35-34-902.png! We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046). We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered. > IT: create tests for the > ------------------------- > > Key: JBIDE-25093 > URL: https://issues.jboss.org/browse/JBIDE-25093 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Labels: cdk, integration-test, openshift_v3 > Fix For: 4.5.x > > Attachments: image-2017-09-22-17-35-34-902.png > > > in JBIDE-24491 we introduced the ability to look up the docker registry in the cdk: > !image-2017-09-22-17-35-34-902.png! > We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046). > We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25093) IT: create tests for the

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25093: ---------------------------------------- Summary: IT: create tests for the Key: JBIDE-25093 URL: https://issues.jboss.org/browse/JBIDE-25093 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.5.1.AM2 Reporter: Andre Dietisheim Fix For: 4.5.x Attachments: image-2017-09-22-17-35-34-902.png in JBIDE-24994 we introduced the ability to look up the docker registry in the cdk: !image-2017-09-22-17-35-34-902.png! We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046). We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25093) IT: create tests for the

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25093: ------------------------------------- Labels: cdk integration-test openshift_v3 (was: ) > IT: create tests for the > ------------------------- > > Key: JBIDE-25093 > URL: https://issues.jboss.org/browse/JBIDE-25093 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Labels: cdk, integration-test, openshift_v3 > Fix For: 4.5.x > > Attachments: image-2017-09-22-17-35-34-902.png > > > in JBIDE-24994 we introduced the ability to look up the docker registry in the cdk: > !image-2017-09-22-17-35-34-902.png! > We should also test that the docker registry in the connection is updated when the cdk starts up (see JBIDE-25046). > We should now also have this covered by bot-tests. Especially the bugs found in JBIDE-25046 and JBIDE-25049 should be covered. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2017