November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23417) [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23417?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23417: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23417 > URL: https://issues.jboss.org/browse/JBIDE-23417 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, integration-test, openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: services-and-routing-settings-wizard-page.png > > > We should create/add integration tests for the "Services and Routing Settings" wizard page which recently got a new column to set the port for the route added. > !services-and-routing-settings-wizard-page.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23463: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23490) Provide ability to link pods when no service is available

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23490: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > Provide ability to link pods when no service is available > --------------------------------------------------------- > > Key: JBIDE-23490 > URL: https://issues.jboss.org/browse/JBIDE-23490 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: new_and_noteworthy > Fix For: 4.4.3.AM1 > > > When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application. > The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23315) Connection wizard: "Advanced >>" Button is cropped

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23315: ------------------------------------------ [~jeffmaury] I agree with [~scabanovich] about the cropping that's done when you manually resize the dialog. The empty space that crops the dialog area is the prioritized space reserved for the progress bar. The most we could do is to have the dialog area providing scroll bars in case it does not show all of its content. > Connection wizard: "Advanced >>" Button is cropped > -------------------------------------------------- > > Key: JBIDE-23315 > URL: https://issues.jboss.org/browse/JBIDE-23315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.x > > Attachments: 2016-11-23 at 15-04-44.mp4, screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4201: ----------------------------- Component/s: installer Fix Version/s: 10.3.0.AM1 > CLI-only installation is available but does not provide necessary info > ---------------------------------------------------------------------- > > Key: JBDS-4201 > URL: https://issues.jboss.org/browse/JBDS-4201 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.2.0.GA > Reporter: Misha Ali > Fix For: 10.3.0.GA > > > I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected. > Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it. > My questions here are: > - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens. > - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion. > Any thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4201: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM1) > CLI-only installation is available but does not provide necessary info > ---------------------------------------------------------------------- > > Key: JBDS-4201 > URL: https://issues.jboss.org/browse/JBDS-4201 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.2.0.GA > Reporter: Misha Ali > Fix For: 10.3.0.GA > > > I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected. > Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it. > My questions here are: > - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens. > - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion. > Any thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23321: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.2.Final) > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.3.AM1 > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23321: ------------------------------------ We have been trying hard making the infrastructure (to run the tests on jenkins) ready, but we are blocked: * for cdk by CDK-30 bug * for minishift by several issues (EAP templates, start stop issue, some ssh error). I'll write the tests in next sprint and then deploy when above issues are fixed. > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.2.Final > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23184. --------------------------------- Updated follow up issue. Verified in DevStudio 10.2.0.GA Build id: GA-v20161122-1842-B6526. > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23513) OpenShift Explorer: Projects created outside of eclipse are not watched

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23513?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23513: ---------------------------------- Summary: OpenShift Explorer: Projects created outside of eclipse are not watched (was: [watcher] projects modified out of workspace not represented in eclipse) > OpenShift Explorer: Projects created outside of eclipse are not watched > ----------------------------------------------------------------------- > > Key: JBIDE-23513 > URL: https://issues.jboss.org/browse/JBIDE-23513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Labels: explorer, openshift_v3 > > See https://issues.jboss.org/browse/JBIDE-23184 for info -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2016