[JBoss JIRA] (JBDS-3490) Include capabilities preference page into jbdevstudio product
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3490:
-------------------------------------
[~nickboldt], thanks for PR :) It seems missing dependency to eclipse bundle where ActivityCategoryPrefrencePage is located.
> Include capabilities preference page into jbdevstudio product
> -------------------------------------------------------------
>
> Key: JBDS-3490
> URL: https://issues.jboss.org/browse/JBDS-3490
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: javascript, target-platform
> Affects Versions: 9.0.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
> Attachments: 3490-error.png, jbds-preferences.png
>
>
> Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug for example tern related issues.
> Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does.
> In current devstudio product package preferences categories looks like
> !jbds-preferences.png!
> as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration.
> It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-20402:
-----------------------------------------------
PR https://github.com/jcantrill/jbosstools-openshift/pull/1 against https://github.com/jcantrill/jbosstools-openshift/tree/20402_deploy_image...
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deploy image WF.bmml, deploy image WF.png, deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, additional env besides those already provided in the image, volumes,
> * Ask about # of replicas, triggers
> * tag and push image to registry (tag=repo/project/stream)
> ** repo is either assumed to be Dockerhub, or the route to the OS registry
> * create a deploymentConfig for the selected image
> * create a service for the image
> * optionally create a route
> Consider running oc new-app on an image to see what it generates
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20402:
---------------------------------------
Please make a PR against https://github.com/jcantrill/openshift-restclient-java/tree/deploy_image_.... I'll merge your changes into the things I'm doing and make a final PR against upstream.
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deploy image WF.bmml, deploy image WF.png, deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, additional env besides those already provided in the image, volumes,
> * Ask about # of replicas, triggers
> * tag and push image to registry (tag=repo/project/stream)
> ** repo is either assumed to be Dockerhub, or the route to the OS registry
> * create a deploymentConfig for the selected image
> * create a service for the image
> * optionally create a route
> Consider running oc new-app on an image to see what it generates
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-20402:
-----------------------------------------------
[~jcantrill], please look at
https://github.com/scabanovich/jbosstools-openshift/tree/jbide-20402-sk,
my commit is
https://github.com/scabanovich/jbosstools-openshift/commit/1dc7a46808cfb9...
Please let me know what I should do another way, and/or what should be done next.
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deploy image WF.bmml, deploy image WF.png, deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, additional env besides those already provided in the image, volumes,
> * Ask about # of replicas, triggers
> * tag and push image to registry (tag=repo/project/stream)
> ** repo is either assumed to be Dockerhub, or the route to the OS registry
> * create a deploymentConfig for the selected image
> * create a service for the image
> * optionally create a route
> Consider running oc new-app on an image to see what it generates
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20026) Explorer: create new connection should default to OpenShift v3 type connection
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20026?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20026:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> Explorer: create new connection should default to OpenShift v3 type connection
> ------------------------------------------------------------------------------
>
> Key: JBIDE-20026
> URL: https://issues.jboss.org/browse/JBIDE-20026
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.3.x
>
> Attachments: new-connection-openshift-v2.png
>
>
> Steps to reproduce:
> # ASSERT: make sure that you have a connection to a v3 server
> # EXEC: in explorer: select your v3 connection and open up the context menu, select "New"->"Connection"
> # ASSERT: The connection wizard pops up with <New Connection> preselected so that you can create a new connection
> Result:
> The suggested connection type is "OpenShift v2"
> !new-connection-openshift-v2.png!
> Expected result:
> The suggested connection type should be "OpenShift v3"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20477) Template presentation is incorrect in New App wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20477?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-20477 at 8/26/15 7:10 PM:
--------------------------------------------------------------
PR applied in master.
!http://content.screencast.com/users/fbricon/folders/Jing/media/0edf92af-8320-4be5-a24c-7ad4ca2ba60b/00000169.png|width=600!
was (Author: fbricon):
PR applied in master.
!http://content.screencast.com/users/fbricon/folders/Jing/media/0edf92af-8320-4be5-a24c-7ad4ca2ba60b/00000169.png!
> Template presentation is incorrect in New App wizard
> -----------------------------------------------------
>
> Key: JBIDE-20477
> URL: https://issues.jboss.org/browse/JBIDE-20477
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.3.0.CR1
>
> Attachments: new app wizard.png
>
>
> Trying to create a new app from template, there are issues in the templates that are displayed and filter which I think are related to being able to choose your project on the first page.
> The addition of the project drop down makes the content of the template pane moot. It should be modified to only include the project selected in the project drop down.
> The templates in all the projects on the server in question:
> {code}
> [root@vagrant vagrant]# oc get templates
> NAME DESCRIPTION PARAMETERS OBJECTS
> [root@vagrant vagrant]# oc get templates -n openshift
> NAME DESCRIPTION PARAMETERS OBJECTS
> amq6 Application template for ActiveMQ brokers. 13 (2 blank) 8
> amq6-persistent Application template for ActiveMQ brokers using persistent storage. 14 (2 blank) 9
> eap6-amq-persistent-sti Application template for EAP 6 A-MQ applications with persistent storage buil... 23 (7 blank) 11
> eap6-amq-sti Application template for EAP 6 A-MQ applications built using STI. 22 (7 blank) 10
> eap6-basic-sti Application template for EAP 6 applications built using STI. 12 (3 blank) 6
> eap6-https-sti Application template for EAP 6 applications built using STI. 16 (5 blank) 8
> eap6-mongodb-persistent-sti Application template for EAP 6 MongDB applications with persistent storage bu... 28 (14 blank) 11
> eap6-mongodb-sti Application template for EAP 6 MongDB applications built using STI. 27 (14 blank) 10
> eap6-mysql-persistent-sti Application template for EAP 6 MySQL applications with persistent storage bui... 29 (16 blank) 11
> eap6-mysql-sti Application template for EAP 6 MySQL applications built using STI. 28 (16 blank) 10
> eap6-postgresql-persistent-sti Application template for EAP 6 PostgreSQL applications with persistent storag... 26 (13 blank) 11
> eap6-postgresql-sti Application template for EAP 6 PostgreSQL applications built using STI. 25 (13 blank) 10
> jws-tomcat7-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5
> jws-tomcat7-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7
> jws-tomcat7-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10
> jws-tomcat7-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9
> jws-tomcat7-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10
> jws-tomcat7-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9
> jws-tomcat7-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10
> jws-tomcat7-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9
> jws-tomcat8-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5
> jws-tomcat8-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7
> jws-tomcat8-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10
> jws-tomcat8-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9
> jws-tomcat8-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10
> jws-tomcat8-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9
> jws-tomcat8-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10
> jws-tomcat8-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9
> [root@vagrant vagrant]# oc get templates -n openshift-dev
> NAME DESCRIPTION PARAMETERS OBJECTS
> [root@vagrant vagrant]# oc get templates -n openshift-infra
> NAME DESCRIPTION PARAMETERS OBJECTS
> [root@vagrant vagrant]#
> {code}
> !new app wizard.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months
[JBoss JIRA] (JBIDE-20477) Template presentation is incorrect in New App wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20477?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-20477 at 8/26/15 7:10 PM:
--------------------------------------------------------------
PR applied in master.
!http://content.screencast.com/users/fbricon/folders/Jing/media/0edf92af-8320-4be5-a24c-7ad4ca2ba60b/00000169.png!
was (Author: fbricon):
PR applied in master.
!http://content.screencast.com/users/fbricon/folders/Jing/media/0edf92af-8320-4be5-a24c-7ad4ca2ba60b/00000169.png1
> Template presentation is incorrect in New App wizard
> -----------------------------------------------------
>
> Key: JBIDE-20477
> URL: https://issues.jboss.org/browse/JBIDE-20477
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.3.0.CR1
>
> Attachments: new app wizard.png
>
>
> Trying to create a new app from template, there are issues in the templates that are displayed and filter which I think are related to being able to choose your project on the first page.
> The addition of the project drop down makes the content of the template pane moot. It should be modified to only include the project selected in the project drop down.
> The templates in all the projects on the server in question:
> {code}
> [root@vagrant vagrant]# oc get templates
> NAME DESCRIPTION PARAMETERS OBJECTS
> [root@vagrant vagrant]# oc get templates -n openshift
> NAME DESCRIPTION PARAMETERS OBJECTS
> amq6 Application template for ActiveMQ brokers. 13 (2 blank) 8
> amq6-persistent Application template for ActiveMQ brokers using persistent storage. 14 (2 blank) 9
> eap6-amq-persistent-sti Application template for EAP 6 A-MQ applications with persistent storage buil... 23 (7 blank) 11
> eap6-amq-sti Application template for EAP 6 A-MQ applications built using STI. 22 (7 blank) 10
> eap6-basic-sti Application template for EAP 6 applications built using STI. 12 (3 blank) 6
> eap6-https-sti Application template for EAP 6 applications built using STI. 16 (5 blank) 8
> eap6-mongodb-persistent-sti Application template for EAP 6 MongDB applications with persistent storage bu... 28 (14 blank) 11
> eap6-mongodb-sti Application template for EAP 6 MongDB applications built using STI. 27 (14 blank) 10
> eap6-mysql-persistent-sti Application template for EAP 6 MySQL applications with persistent storage bui... 29 (16 blank) 11
> eap6-mysql-sti Application template for EAP 6 MySQL applications built using STI. 28 (16 blank) 10
> eap6-postgresql-persistent-sti Application template for EAP 6 PostgreSQL applications with persistent storag... 26 (13 blank) 11
> eap6-postgresql-sti Application template for EAP 6 PostgreSQL applications built using STI. 25 (13 blank) 10
> jws-tomcat7-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5
> jws-tomcat7-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7
> jws-tomcat7-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10
> jws-tomcat7-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9
> jws-tomcat7-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10
> jws-tomcat7-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9
> jws-tomcat7-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10
> jws-tomcat7-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9
> jws-tomcat8-basic-sti Application template for JWS applications built using STI. 11 (3 blank) 5
> jws-tomcat8-https-sti Application template for JWS applications built using STI. 15 (4 blank) 7
> jws-tomcat8-mongodb-persistent-sti Application template for JWS MongoDB applications with persistent storage bui... 27 (11 blank) 10
> jws-tomcat8-mongodb-sti Application template for JWS MongoDB applications built using STI. 26 (11 blank) 9
> jws-tomcat8-mysql-persistent-sti Application template for JWS MySQL applications with persistent storage built... 28 (13 blank) 10
> jws-tomcat8-mysql-sti Application template for JWS MySQL applications built using STI. 27 (13 blank) 9
> jws-tomcat8-postgresql-persistent-sti Application template for JWS PostgreSQL applications with persistent storage... 25 (10 blank) 10
> jws-tomcat8-postgresql-sti Application template for JWS PostgreSQL applications built using STI. 24 (10 blank) 9
> [root@vagrant vagrant]# oc get templates -n openshift-dev
> NAME DESCRIPTION PARAMETERS OBJECTS
> [root@vagrant vagrant]# oc get templates -n openshift-infra
> NAME DESCRIPTION PARAMETERS OBJECTS
> [root@vagrant vagrant]#
> {code}
> !new app wizard.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 7 months