November 2016 - jbosstools-issues

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

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23184: ------------------------------------------ [~mlabuda] if i understand you right, that's a correct behavior. All resources are tied to Project. It's a workspace for all of them. So project (not a connection) is a starting point to watch the resources. That's why when you create the project via oc binary, we are not yet assigned for watching changed in project, because we have no information about it. That's why you need to refresh the connection to let OS explorer know about the project and it will create this "starting point" for watching. I think if we want the watch process to start from connection, it would require a huge refactoring, but i might be wrong. [~jcantrill] [~adietish] [~jeffmaury] what do you think? > 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-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22225: ------------------------------------- [~mlabuda] this might be a fare point, but issues like JBIDE-23422 are *not* debugger related and Node.js debugger just reveals those problems > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Jeff MAURY > Labels: debugging, new_and_noteworthy, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. > steps: https://www.youtube.com/watch?v=1cKPPQrlC4k&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23375) Application wizard: Duplicated templates shown on a project with same name as cluster namespace

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23375?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23375. --------------------------------- Verified in DevStudio 10.2.0.GA, Build id: GA-v20161116-0039-B6472 > Application wizard: Duplicated templates shown on a project with same name as cluster namespace > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23375 > URL: https://issues.jboss.org/browse/JBIDE-23375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: duplicate_templates.png > > > When I change a cluster namespace and I am using this namespace with a user who has a project with same name, templates shown in New OpenShift Application wizard are duplicated. > !duplicate_templates.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22225. --------------------------------- Verified in DevStudio 10.2.0.GA, Build id: GA-v20161116-0039-B6472. Remaining issues are files in follow-up JIRAs. Next time if there exist issues, it would be much better to keep a feature request JIRA opened until everything is done. Partial PRs can be merged but I would not consider things done until they are done. Or break up a feature request JIRA for subtasks and resolved specific subtasks and once all subtasks are completed, mark parent feature request JIRA as done. > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Jeff MAURY > Labels: debugging, new_and_noteworthy, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. > steps: https://www.youtube.com/watch?v=1cKPPQrlC4k&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23300) OpenShift connection created by CDK server adapter does not store password in secure storage

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23300?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23300: ---------------------------------- Component/s: (was: openshift) > OpenShift connection created by CDK server adapter does not store password in secure storage > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23300 > URL: https://issues.jboss.org/browse/JBIDE-23300 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Labels: connection > Fix For: 4.4.2.AM3 > > > OpenShift 3 connection created by a CDK server adapter does not successfully store password in secure storage although a checkbox in the Connection dialog is checked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23379?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23379. --------------------------------- Nothing to verify from QE. > set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23379 > URL: https://issues.jboss.org/browse/JBIDE-23379 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM3 > > > We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22803. --------------------------------- Verified in DevStudio 10.2.0.GA, Build id: GA-v20161116-0039-B6472 > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23353) Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23353?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23353. --------------------------------- Verified in DevStudio 10.2.0.GA, Build id: GA-v20161116-0039-B6472 > Deploy Docker Wizard: Enable checking "Used by route" checkbox by mouse click > ----------------------------------------------------------------------------- > > Key: JBIDE-23353 > URL: https://issues.jboss.org/browse/JBIDE-23353 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > In Deploy Image to OpenShift on wizard page with routing settings there is a table with port mapping. There is a table cell with checkbox to be used by routing. This is not editable by clicking on the cell. User is forced to open dialog to edit port mapping, manually click on a checkbox to use for routing and confirm dialog. This is pretty user unfriendly. It should be enabled to click on the cell and have checkbox checked/unchecked. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16596. --------------------------------- Closing as cannot reproduce anymore, issue fixed itself by changes in GTK 3. > Server Adapter Editor: Timeouts and publishing fields are too small > ------------------------------------------------------------------- > > Key: JBIDE-16596 > URL: https://issues.jboss.org/browse/JBIDE-16596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.4.2.AM3 > > Attachments: server-adapter-openshift2-timeouts.png, server-adapter-openshift3-timeouts.png, small_field.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4169) Integrate OpenShift Server Adapter in Servers view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4169?page=com.atlassian.jira.plugin.... ] Marián Labuda closed JBDS-4169. ------------------------------- > Integrate OpenShift Server Adapter in Servers view > -------------------------------------------------- > > Key: JBDS-4169 > URL: https://issues.jboss.org/browse/JBDS-4169 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: openshift > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 10.2.0.AM3 > > > it is currently in a dedicated view. > It is then hard to find for people used to JBDS and other servers. > I personally wasn't able to find this specific view by myself, I was trying to add/remove application on the CDK server adapter. -- 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