June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24509) No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24509?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24509: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final > ------------------------------------------------------------------------ > > Key: JBIDE-24509 > URL: https://issues.jboss.org/browse/JBIDE-24509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Environment: JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Eclipse Neon 4.6.1 > Fedora 24 and Windows 10 > Reporter: Xia Zhao > Priority: Blocker > Fix For: 4.5.0.Final > > Attachments: OpenShift3.png, Screenshot from 2017-05-25 13-37-32.png, Screenshot from 2017-05-25 14-25-53.png, Screenshot from 2017-06-02 10-20-42.png, Screenshot from 2017-06-02 10-39-16.png, Screenshot from 2017-06-02 10-54-54.png > > > Description of problem: > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final, after installation, only these 3 tools exist without having the openshift v3 tools: > JBoss OpenShift 2 Tools > JBoss OpenShift JavaScript Tools > JBoss Tools EGit Integration > Version-Release number of selected component (if applicable): > JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > How reproducible: > Always > Steps to Reproduce: > 1.Install JBT for Openshift v3 Tools according to http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...: > --> Add the following URL to Eclipse Neon 4.6.1 installation via: > Help > Install New Software... > Work with: > http://download.jboss.org/jbosstools/neon/stable/updates/ > Then select all the components, choose to install them. > 2. Restart Eclipse Neon 4.6.1 after JTB installation finished > 3. Go into Openshift Explorer window, click on "New Connections Wizard", choose "Openshift 3" for server type, the Authentication panel is empty > 4. Go to Help > Intallation Details, search for openshift > Actual results: > 4. JBoss OpenShift 3 Tools are not installed, only the following 3 exist: > JBoss OpenShift 2 Tools 3.3.3.v20170510-1453 org.jboss.tools.openshift.express.feature.feature.group JBoss by Red Hat > JBoss OpenShift JavaScript Tools 3.3.3.v20170502-0607 org.jboss.tools.openshift.js.feature.feature.group JBoss by Red Hat > JBoss Tools EGit Integration 3.3.3.v20170405-1252 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat > Expected results: > JBoss OpenShift 3 Tools should be installed if following http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Additional info: > Issue reproduced on both Fedora 24 and Windows 10. > This is a regression, with old JBT build 4.3.3 Final, the openshift 3 tools existed and worked fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21448: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Port Forwarding: Allow port-forwarding of ports not defined on pod metadata > --------------------------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.Final > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24144) When deploying user should be able to tune the memory requirements

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24144?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24144: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > When deploying user should be able to tune the memory requirements > ------------------------------------------------------------------ > > Key: JBIDE-24144 > URL: https://issues.jboss.org/browse/JBIDE-24144 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, wizard > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24184: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24316) Analyze connection management

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24316?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24316: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Analyze connection management > ----------------------------- > > Key: JBIDE-24316 > URL: https://issues.jboss.org/browse/JBIDE-24316 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3 > Fix For: 4.5.0.Final > > > Analyze connection management: is connection/client accessible from resources like it is for the REST client or is there a new pattern needed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24184: ------------------------------------------ Have a fair amount of progress on this, but given all the changes required to fullfill this (changes in UI, in core, in js plugin, lots of cleanups, design changes etc.) I have to postpone a 2nd time unfortunately. See the current PR with +2000/-1000 lines without fixing tests and adding new ones! > Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24184 > URL: https://issues.jboss.org/browse/JBIDE-24184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}: > * nodejs > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > ... > {code} > * eap > {code} > "Labels": { > ... > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > ... > {code} > Our code on the other hand is hard-coding these, not reading the keys from the docker image: > {code} > public class OpenShiftDebugUtils { > private static final String DEBUG_KEY = "DEBUG"; > private static final String DEBUG_PORT_KEY = "DEBUG_PORT"; > ... > {code} > {code} > public class OpenShiftLaunchController extends AbstractSubsystemController > implements ISubsystemController, ILaunchServerController { > ... > private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$ > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24561: ------------------------------- Sprint: devex #134 Jun 2017 (was: devex #133 Jun 2017) > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) Checking console output takes 80 mins?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24561: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Checking console output takes 80 mins? > -------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24572) use M2_HOME=${COMMON_TOOLS}/apache-maven-3.3.9/ instead of hard coding the path to /qa/tools/opt

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24572: ---------------------------------- Summary: use M2_HOME=${COMMON_TOOLS}/apache-maven-3.3.9/ instead of hard coding the path to /qa/tools/opt Key: JBIDE-24572 URL: https://issues.jboss.org/browse/JBIDE-24572 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt Jobs should use global slave-specific variable COMMON_TOOLS to define path to maven binary, eg., this change: https://dev-platform-jenkins-rhel7.rhev-ci-vms.eng.rdu2.redhat.com/job/jb... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24572) use M2_HOME=${COMMON_TOOLS}/apache-maven-3.3.9/ instead of hard coding the path to /qa/tools/opt

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24572?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24572: ---------------------------------- Assignee: Nick Boldt > use M2_HOME=${COMMON_TOOLS}/apache-maven-3.3.9/ instead of hard coding the path to /qa/tools/opt > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24572 > URL: https://issues.jboss.org/browse/JBIDE-24572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Jobs should use global slave-specific variable COMMON_TOOLS to define path to maven binary, eg., this change: > https://dev-platform-jenkins-rhel7.rhev-ci-vms.eng.rdu2.redhat.com/job/jb... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017