November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25197) Integration Tests: StoreConnectionTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25197?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25197: ---------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > Integration Tests: StoreConnectionTest > -------------------------------------- > > Key: JBIDE-25197 > URL: https://issues.jboss.org/browse/JBIDE-25197 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25281) IT: Edit resource limits wizard stabilize and add in suites

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25281?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25281: ---------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > IT: Edit resource limits wizard stabilize and add in suites > ----------------------------------------------------------- > > Key: JBIDE-25281 > URL: https://issues.jboss.org/browse/JBIDE-25281 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.x > > > Test has been created in JBIDE-25090 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25317) Add Fedora 27 to Central Ci slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25317?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25317: ---------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > Add Fedora 27 to Central Ci slaves > ---------------------------------- > > Key: JBIDE-25317 > URL: https://issues.jboss.org/browse/JBIDE-25317 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.2.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.2.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25093: ---------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > IT: create tests for the Docker discovery feature > ------------------------------------------------- > > 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 > Assignee: Ondrej Dockal > 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.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25067) jsf itests job is failing

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25067?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25067: ---------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > jsf itests job is failing > ------------------------- > > Key: JBIDE-25067 > URL: https://issues.jboss.org/browse/JBIDE-25067 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, jsf > Reporter: Pavol Srna > Assignee: Ondrej Dockal > Fix For: 4.5.x > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25093?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-25093 at 11/22/17 6:21 AM: ----------------------------------------------------------------- Same start for all test cases: 0. EXEC: CDK 3 Server adapter is created, state is Stopped. Base case: 1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up. 2. EXEC: Clicking discover button fills up the Image Registry URL label with value 3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?) Registy URL not found case (JBIDE-25049): 1. EXEC: Start CDK 3 server adapter, OS 3 connection is created 2. EXEC: Remove CDK 3 Adapter without stopping it 3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig) 4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up. 5. EXEC: Click the Discovery button 6. ASSERT: Registry URL not found dialog is active, proper message is at place Another case 1: Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url. Another case 2: Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (JBIDE-25014) - resolved was (Author: odockal): Same start for all test cases: 0. EXEC: CDK 3 Server adapter is created, state is Stopped. Base case: 1. EXEC: CDK 3 adapter is started, OS 3 connection created and OS 3 edit connection wizard is opened. Advanced section is shown up. 2. EXEC: Clicking discover button fills up the Image Registry URL label with value 3. ASSERT: The filled up value is the same as output from calling 'minishift openshift registry' (can be done via Java process?) Registy URL not found case (JBIDE-25049): 1. EXEC: Start CDK 3 server adapter, OS 3 connection is created 2. EXEC: Remove CDK 3 Adapter without stopping it 3. EXEC: Add new CDK 3 server adapter that is in state Stopped (but minishift is runnig) 4. EXEC: Have OS 3 edit connection wizard opened. Advanced section is shown up. 5. EXEC: Click the Discovery button 6. ASSERT: Registry URL not found dialog is active, proper message is at place Another case 1: Check the image registry url is updated for more OS 3 connections than one when CDK 3 server adapter is started (JBIDE-25120, JBIDE-25121) and button Discovery fills up the url of image registry url. Another case 2: Check warning if image registry url would be overwritten by clicking the Discover button. Do not know, how to reproduce (JBIDE-25014) > IT: create tests for the Docker discovery feature > ------------------------------------------------- > > 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 > Assignee: Ondrej Dockal > 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.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25319) fix failing aerogear.it job

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25319?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-25319: ------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > fix failing aerogear.it job > --------------------------- > > Key: JBIDE-25319 > URL: https://issues.jboss.org/browse/JBIDE-25319 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, integration-tests > Affects Versions: 4.5.2.AM1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.x > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25321) Fix failing jst.itests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25321?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-25321: ------------------------------- Sprint: devex #141 December 2017 (was: devex #140 November 2017) > Fix failing jst.itests > ---------------------- > > Key: JBIDE-25321 > URL: https://issues.jboss.org/browse/JBIDE-25321 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, jst > Affects Versions: 4.5.2.AM1 > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.x > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > Failed tests: > 12:24:59 NodeJSDebuggerTest.testDebuggerStopsAtBreakpoint:187 Debugger hasn't stopped on breakpoint > 12:24:59 > 12:24:59 Tests in error: > 12:24:59 NodeJSDebuggerTest.debugAs:104 » WaitTimeoutExpired Timeout after: 60 s.: tree... > 12:24:59 > 12:24:59 Tests run: 32, Failures: 1, Errors: 1, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25375: ------------------------------- Story Points: 10 Sprint: devex #141 December 2017 > Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25375 > URL: https://issues.jboss.org/browse/JBIDE-25375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > {code:java} > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520 > java.version=1.8.0_144 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25375: ---------------------------------- Assignee: Jeff MAURY > Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25375 > URL: https://issues.jboss.org/browse/JBIDE-25375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > {code:java} > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520 > java.version=1.8.0_144 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017