[JBoss JIRA] (JBIDE-24675) install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24675?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24675:
------------------------------------
New error:
{code}
14:22:07 Debug options:
14:22:07 file:/mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/2a8c2014/eclipse/.options not found
14:22:07 Time to load bundles: 40
14:22:10 Starting application: 2651
14:22:13 Application Started: 5656
14:22:13 Testsuite: org.jboss.tools.tests.installation.InstallTest
14:22:15 log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher).
14:22:15 log4j:WARN Please initialize the log4j system properly.
14:22:16 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.061 sec
14:22:16
14:22:16 Testcase: testInstall took 2.914 sec
14:22:16 Caused an ERROR
14:22:16 The widget was null.
14:22:16 org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: The widget was null.
14:22:16 at org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBot.<init>(AbstractSWTBot.java:110)
14:22:16 at org.eclipse.swtbot.swt.finder.widgets.AbstractSWTBotControl.<init>(AbstractSWTBotControl.java:48)
14:22:16 at org.eclipse.swtbot.swt.finder.widgets.SWTBotShell.<init>(SWTBotShell.java:53)
14:22:16 at org.eclipse.swtbot.swt.finder.widgets.SWTBotShell.<init>(SWTBotShell.java:42)
14:22:16 at org.eclipse.swtbot.swt.finder.SWTBotFactory.activeShell(SWTBotFactory.java:461)
14:22:16 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.activeShell(SWTWorkbenchBot.java:1)
14:22:16 at org.eclipse.swtbot.swt.finder.SWTBotFactory.menu(SWTBotFactory.java:204)
14:22:16 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.menu(SWTWorkbenchBot.java:1)
14:22:16 at org.eclipse.swtbot.swt.finder.SWTBotFactory.menu(SWTBotFactory.java:233)
14:22:16 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.menu(SWTWorkbenchBot.java:1)
14:22:16 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:82)
14:22:16 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78)
14:22:16 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47)
14:22:16 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.runChild(SWTBotJunit4ClassRunner.java:75)
14:22:16 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60)
14:22:16 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
14:22:16 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
14:22:16 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120)
14:22:16 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73)
14:22:16 at java.lang.Thread.run(Thread.java:748)
{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24675
> URL: https://issues.jboss.org/browse/JBIDE-24675
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: install-tests
> Affects Versions: 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 4.5.0.Final
>
>
> {code}
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0040f (Add Reposi)
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:38 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:38 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:56 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0008e (workspace )
> 15:51:56 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:52:02 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.816 sec
> 15:52:02
> 15:52:02 Testcase: testInstall took 26.254 sec
> 15:52:02 Caused an ERROR
> 15:52:02 Internal error
> 15:52:02 java.lang.RuntimeException: Internal error
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:213)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:147)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:133)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBothttps://dev-platform-jenkins.rh...
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120)
> 15:52:02 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73)
> 15:52:02 at java.lang.Thread.run(Thread.java:748)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:472)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntilWidgetAppears(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shells(SWTBotFactory.java:116)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shells(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:106)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:97)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:156)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:522)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:496)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:484)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:466){code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBTIS-1045) Drools plugin version doesn't match the appropriate bundle version
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1045?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1045:
-----------------------------------
Hi [~apodhrad] - can you paste in the exact URL that has the incorrect version?
> Drools plugin version doesn't match the appropriate bundle version
> ------------------------------------------------------------------
>
> Key: JBTIS-1045
> URL: https://issues.jboss.org/browse/JBTIS-1045
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: drools/ jBPM
> Affects Versions: 4.4.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> JBTIS 4.4.1.Final / DevstudioIS 10.1.0.GA contains drools plugins in the following version
> {code}
> 6.5.1.Final-v20161109-054101-B1259
> {code}
> All related features and plugins also contain the above versions such as
> {code}
> org.drools.eclipse.feature_6.5.1.Final-v20161109-054101-B1259
> org.drools.eclipse_6.5.1.Final-v20161109-054101-B1259.jar
> {code}
> But if you unzip the drools plugin and look at its bundle version in MANIFEST file you will see
> {code}
> Bundle-Version: 6.5.0.20161109-054101
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24675) install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24675?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24675:
------------------------------------
No need to bump the version.
Built your PR. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=14
Now checking if it works in downstream job:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24675
> URL: https://issues.jboss.org/browse/JBIDE-24675
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: install-tests
> Affects Versions: 4.5.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 4.5.0.Final
>
>
> {code}
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0040f (Add Reposi)
> 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:38 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install )
> 15:51:38 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:51:56 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0008e (workspace )
> 15:51:56 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> 15:52:02 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.816 sec
> 15:52:02
> 15:52:02 Testcase: testInstall took 26.254 sec
> 15:52:02 Caused an ERROR
> 15:52:02 Internal error
> 15:52:02 java.lang.RuntimeException: Internal error
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:213)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:147)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:133)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47)
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBothttps://dev-platform-jenkins.rh...
> 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208)
> 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120)
> 15:52:02 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73)
> 15:52:02 at java.lang.Thread.run(Thread.java:748)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:472)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntilWidgetAppears(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shells(SWTBotFactory.java:116)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shells(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:106)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:97)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1)
> 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:156)
> 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find shell matching: with text 'Installing Software'
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:522)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:496)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:484)
> 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1)
> 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:466){code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24682) Reflect changes in minishift's version command
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24682?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24682:
---------------------------------------
[~rob.stryker] I have checked that devstudio 11.0.0 GA build: GA-v20170731-0116-B659 is consuming correctly output from 'minishift version' within a couple of builds of CDK.
Here are complete results (even for older version to be able to compare the outputs):
||CDK/minishift builds||Devstudio 11.0.0.GA v20170725-0331-B596||Devstudio 11.0.0.GA v20170731-0116-B659||
|19-Jun-2017.cdk-3.0.0-CVE-2|OK|OK|
|13-Jul-2017|X|OK|
|27-Jul-2017|X|OK|
|minishift-1.3.1|X|OK|
> Reflect changes in minishift's version command
> ----------------------------------------------
>
> Key: JBIDE-24682
> URL: https://issues.jboss.org/browse/JBIDE-24682
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.0.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.5.0.Final
>
>
> Due to changes in upstream project the 'minishift version' command returns different lines.
> CDK result from http://cdk-builds.usersys.redhat.com/builds/weekly/19-Jun-2017.cdk-3.0.0-... build:
> {code}
> Minishift version: 1.0.0+4f8cb6d
> CDK Version: 3.0.0-2
> {code}
> vs.
> CDK result from nightly http://cdk-builds.usersys.redhat.com/builds/nightly/13-Jul-2017 build:
> {code}
> minishift v1.2.0+001371f
> CDK Version:3.0.0-13072017-1
> {code}
> And this change results in error while creating CDK 3 server adapter with newer CDK nightly build as it ends with "Unknown error while checking minishift version" as we expect the string to contains "Minishift Version".
> We should get in touch with cdk team to check whether they plan to change the output 'CDK Version' to something else as well, in case we are going to distinguish between minishift and cdk. If we accept in CDK 3 server adapter both cdk and minishift binary maybe we should create a CDK jira that would ask for changing output from 'minishift version' from 'CDK Version: X.X.X' to 'cdk vX.X.X'. I do not know if we plan to do so, it is just an idea...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBTIS-1045) Drools plugin version doesn't match the appropriate bundle version
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1045?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1045:
---------------------------------
Assignee: Paul Leacu
> Drools plugin version doesn't match the appropriate bundle version
> ------------------------------------------------------------------
>
> Key: JBTIS-1045
> URL: https://issues.jboss.org/browse/JBTIS-1045
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: drools/ jBPM
> Affects Versions: 4.4.1.Final
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> JBTIS 4.4.1.Final / DevstudioIS 10.1.0.GA contains drools plugins in the following version
> {code}
> 6.5.1.Final-v20161109-054101-B1259
> {code}
> All related features and plugins also contain the above versions such as
> {code}
> org.drools.eclipse.feature_6.5.1.Final-v20161109-054101-B1259
> org.drools.eclipse_6.5.1.Final-v20161109-054101-B1259.jar
> {code}
> But if you unzip the drools plugin and look at its bundle version in MANIFEST file you will see
> {code}
> Bundle-Version: 6.5.0.20161109-054101
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1150?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky commented on JBTIS-1150:
------------------------------------------
Hey [~pleacu] could you have a look at JBTIS-1045, please? There was a trick where the bundles pretend the correct version but in fact the version was incorrect.
> Incorrect version of Drools plugins
> -----------------------------------
>
> Key: JBTIS-1150
> URL: https://issues.jboss.org/browse/JBTIS-1150
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, drools/ jBPM
> Affects Versions: 4.5.0.CR2, 11.0.0.CR2
> Reporter: Andrej Podhradsky
> Assignee: Kris Verlaenen
>
> Drools plugins are in the following version
> {code}
> 7.0.1.Final
> {code}
> which doesn't follow our rules for versions (JBTIS-471)
> {code}
> x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B###
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1150?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1150:
-----------------------------------
HEy [~KrisVerlaenen] - I can build again. The local build results look good:
i.e. org.drools.eclipse.feature_8.0.0.Final-v20170801-1309-B1.jar
This should be resolved for your 8.0 build. We'll keep it open to remind us until it's available. Thanks for looking into it.
> Incorrect version of Drools plugins
> -----------------------------------
>
> Key: JBTIS-1150
> URL: https://issues.jboss.org/browse/JBTIS-1150
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, drools/ jBPM
> Affects Versions: 4.5.0.CR2, 11.0.0.CR2
> Reporter: Andrej Podhradsky
> Assignee: Kris Verlaenen
>
> Drools plugins are in the following version
> {code}
> 7.0.1.Final
> {code}
> which doesn't follow our rules for versions (JBTIS-471)
> {code}
> x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B###
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months
[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24501:
-------------------------------------
Steps to Reproduce:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The deploy fails with 2 error dialogs, the wizard stays open.
One that tells you that the lookup failed and one that tells you about an NPE that happened:
!screenshot-1.png!
!image-2017-05-23-12-10-06-694.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
was:
# ASSERT: have the CDK with the registry that's not publicly reachable
# ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git)
# ASSERT: have a connection to the docker daemon in the CDK3
# EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK
# EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..."
# EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard
# ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer
!image-2017-05-23-12-00-51-733.png!
# EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..."
# ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix
!image-2017-05-23-12-07-14-028.png!
# EXEC: hit "Next"
Result:
The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened:
!image-2017-05-23-12-10-06-694.png!
!screenshot-1.png!
In the Eclipse log you'll find the following:
{code}
java.lang.NullPointerException
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356)
at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
{code}
> Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24501
> URL: https://issues.jboss.org/browse/JBIDE-24501
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.0.Final
>
> Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png, screenshot-1.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 11 months