June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23589) Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23589?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23589: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test > --------------------------------------------------------------------------- > > Key: JBIDE-23589 > URL: https://issues.jboss.org/browse/JBIDE-23589 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, openshift > Fix For: 4.5.0.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.openshift.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23589) Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23589?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23589: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.0.Final) > Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test > --------------------------------------------------------------------------- > > Key: JBIDE-23589 > URL: https://issues.jboss.org/browse/JBIDE-23589 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, openshift > Fix For: 4.5.0.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.openshift.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24539: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.Final > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24499) Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24499: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24499 > URL: https://issues.jboss.org/browse/JBIDE-24499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-23-11-20-07-473.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22613: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.0.Final > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24540: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24236) Preferences: "automagically" use the oc that's shipped with the cdk3

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24236: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Preferences: "automagically" use the oc that's shipped with the cdk3 > -------------------------------------------------------------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: oc_binary, openshift_v3 > Fix For: 4.5.0.Final > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23422: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24540: ------------------------------------------ [~jeffmaury] what's the status of this? > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[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 commented on JBIDE-24509: ------------------------------------------ [~jeffmaury] afaik this was discussed in the last milestone. Did we fix this or? > 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

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