May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19095) Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..."

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19095: ------------------------------------------ fixVersion LATER since we wont do any enhancement (but at most critical bug fixes) in v2. > Console: All env. vars are listed as "Snapshot Restore/Deploy for application ..." > ---------------------------------------------------------------------------------- > > Key: JBIDE-19095 > URL: https://issues.jboss.org/browse/JBIDE-19095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Priority: Minor > Labels: environment_variables, openshift_v2 > Fix For: LATER > > Attachments: erroneous-snapshot-restore-title.png > > > While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19654: ---------------------------------------- Assignee: (was: Andre Dietisheim) > Application wizard: Opening the wizard on an account without SSH key opens broken wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19654 > URL: https://issues.jboss.org/browse/JBIDE-19654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v2 > Fix For: LATER > > Attachments: new_app_wizard.png, prompt-to-upload-keys.png > > > If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty > !new_app_wizard.png! > There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19654: ------------------------------------- Fix Version/s: LATER (was: 4.4.x) > Application wizard: Opening the wizard on an account without SSH key opens broken wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19654 > URL: https://issues.jboss.org/browse/JBIDE-19654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v2 > Fix For: LATER > > Attachments: new_app_wizard.png, prompt-to-upload-keys.png > > > If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty > !new_app_wizard.png! > There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3910) Include EAP 7.0 in JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3910?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3910: ----------------------------- Fix Version/s: 10.x > Include EAP 7.0 in JBDS installer > --------------------------------- > > Key: JBDS-3910 > URL: https://issues.jboss.org/browse/JBDS-3910 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Component Upgrade > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.x > > > Include EAP 7.0.0 in JBDS 9.1.0 installer. Once ready, add it to http://www.jboss.org/products/devstudio/download/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19654: ------------------------------------------ fixVersion LATER since we wont do any enhancement (but at most critical bug fixes) in v2. > Application wizard: Opening the wizard on an account without SSH key opens broken wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19654 > URL: https://issues.jboss.org/browse/JBIDE-19654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v2 > Fix For: LATER > > Attachments: new_app_wizard.png, prompt-to-upload-keys.png > > > If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty > !new_app_wizard.png! > There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Auto guess Openshift connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22277: ------------------------------------- Labels: new_and_noteworthy openshift_v3 (was: new_and_noteworthy) > Auto guess Openshift connections > -------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-11367: ------------------------------------- Fix Version/s: LATER (was: 4.4.x) > Application wizard should close and run maven import in background once the application was created > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard > Fix For: LATER > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen. > We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11367) Application wizard should close and run maven import in background once the application was created

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-11367: ------------------------------------------ fixVersion LATER since we wont do any enhancement (but at most critical bug fixes) in v2. > Application wizard should close and run maven import in background once the application was created > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-11367 > URL: https://issues.jboss.org/browse/JBIDE-11367 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Beta1 > Reporter: Xavier Coulon > Labels: application_wizard > Fix For: LATER > > > After 3.3.0.Beta1, most of the operations are run at the end of the wizard (ie, in the performFinish() method) in background jobs. The UI is not blocked but the wizard wont close before the jobs are finished. Since creating the app, adding cartridges, cloning the repo and importing the project within it is a lot of work the user is blocked and condemned to see and watch it happen. > We should free the user to do other tasks by allowing him to close the wizard and get notified once the process finished. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20634) Property gear_profile not added to POST when creating an app using Openshift plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20634?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20634: ------------------------------------- Fix Version/s: LATER (was: 4.4.x) > Property gear_profile not added to POST when creating an app using Openshift plugin > ----------------------------------------------------------------------------------- > > Key: JBIDE-20634 > URL: https://issues.jboss.org/browse/JBIDE-20634 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.Final > Environment: Using Openshift Enterprise v2 and JBDS 8.1.0 > Reporter: Samuel Tauil > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: JSON, gear, openshift_v2 > Fix For: LATER > > > When creating a new application using the Openshift plugin and selecting a different gear profile to create the app seems the attribute gear_profile wasn't added properly to the POST http made in the broker. Checking the the same procedure but using the web console the attribute was added properly. This behavior, when creating thru JBDS, forces the app to be created in a different node that was chosen by the user since the attribute is not added to the post JSON. > This request was generated from JBDS: > 2015-09-08 17:31:33.396 [INFO ] Started POST "/broker/rest/domain/domain1210/applications?include=cartridges" for 108.212.65.14 at 2015-09-08 17:31:33 -0400 (pid:12413) > 2015-09-08 17:31:33.400 [INFO ] Processing by ApplicationsController#create as JSON (pid:12413) > 2015-09-08 17:31:33.400 [INFO ] Parameters: {"name"=>"nanfusecoursetest2", "cartridges"=>[{"name"=>"fuse-1.0.0"}], "include"=>"cartridges", "domain_id"=>"domain1210"} (pid:12413) > 2015-09-08 17:34:33.950 [INFO ] Started GET "/broker/rest/domain/domain1210" for 108.212.65.14 at 2015-09-08 17:34:33 -0400 (pid:12439) > 2015-09-08 17:34:33.966 [INFO ] Processing by DomainsController#show as JSON (pid:12439) > 2015-09-08 17:34:33.966 [INFO ] Parameters: {"id"=>"domain1210"} (pid:12439) > 2015-09-08 17:34:33.999 [INFO ] Completed 200 OK in 32ms (Views: 6.8ms) (pid:12439) > This one was generated by the broker web console: > 2015-09-08 17:22:34.777 [INFO ] Started POST "/broker/rest/domain/domain1210/applications.json" for 127.0.0.1 at 2015-09-08 17:22:34 -0400 (pid:12413) > 2015-09-08 17:22:34.783 [INFO ] Processing by ApplicationsController#create as JSON (pid:12413) > 2015-09-08 17:22:34.783 [INFO ] Parameters: {"cartridges"=>["fuse-1.0.0"], "domain_id"=>"domain1210", "gear_profile"=>"fuse_medium", "initial_git_branch"=>"", "initial_git_url"=>"", "name"=>"nanfusecoursetest1"} (pid:12413) > 2015-09-08 17:24:53.751 [INFO ] Completed 201 Created in 138967ms (Views: 10.9ms) (pid:12413) > 2015-09-08 17:24:56.599 [INFO ] Started GET "/broker/rest/application/55ef519a7577e6d79a000027.json" for 127.0.0.1 at 2015-09-08 17:24:56 -0400 (pid:12413) > 2015-09-08 17:24:56.609 [INFO ] Processing by ApplicationsController#show as JSON (pid:12413) > 2015-09-08 17:24:56.612 [INFO ] Parameters: {"id"=>"55ef519a7577e6d79a000027"} (pid:12413) > 2015-09-08 17:24:56.679 [INFO ] Completed 200 OK in 66ms (Views: 2.3ms) (pid:12413) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20634) Property gear_profile not added to POST when creating an app using Openshift plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20634?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20634: ---------------------------------------- Assignee: (was: Max Rydahl Andersen) > Property gear_profile not added to POST when creating an app using Openshift plugin > ----------------------------------------------------------------------------------- > > Key: JBIDE-20634 > URL: https://issues.jboss.org/browse/JBIDE-20634 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.3.Final > Environment: Using Openshift Enterprise v2 and JBDS 8.1.0 > Reporter: Samuel Tauil > Priority: Critical > Labels: JSON, gear, openshift_v2 > Fix For: LATER > > > When creating a new application using the Openshift plugin and selecting a different gear profile to create the app seems the attribute gear_profile wasn't added properly to the POST http made in the broker. Checking the the same procedure but using the web console the attribute was added properly. This behavior, when creating thru JBDS, forces the app to be created in a different node that was chosen by the user since the attribute is not added to the post JSON. > This request was generated from JBDS: > 2015-09-08 17:31:33.396 [INFO ] Started POST "/broker/rest/domain/domain1210/applications?include=cartridges" for 108.212.65.14 at 2015-09-08 17:31:33 -0400 (pid:12413) > 2015-09-08 17:31:33.400 [INFO ] Processing by ApplicationsController#create as JSON (pid:12413) > 2015-09-08 17:31:33.400 [INFO ] Parameters: {"name"=>"nanfusecoursetest2", "cartridges"=>[{"name"=>"fuse-1.0.0"}], "include"=>"cartridges", "domain_id"=>"domain1210"} (pid:12413) > 2015-09-08 17:34:33.950 [INFO ] Started GET "/broker/rest/domain/domain1210" for 108.212.65.14 at 2015-09-08 17:34:33 -0400 (pid:12439) > 2015-09-08 17:34:33.966 [INFO ] Processing by DomainsController#show as JSON (pid:12439) > 2015-09-08 17:34:33.966 [INFO ] Parameters: {"id"=>"domain1210"} (pid:12439) > 2015-09-08 17:34:33.999 [INFO ] Completed 200 OK in 32ms (Views: 6.8ms) (pid:12439) > This one was generated by the broker web console: > 2015-09-08 17:22:34.777 [INFO ] Started POST "/broker/rest/domain/domain1210/applications.json" for 127.0.0.1 at 2015-09-08 17:22:34 -0400 (pid:12413) > 2015-09-08 17:22:34.783 [INFO ] Processing by ApplicationsController#create as JSON (pid:12413) > 2015-09-08 17:22:34.783 [INFO ] Parameters: {"cartridges"=>["fuse-1.0.0"], "domain_id"=>"domain1210", "gear_profile"=>"fuse_medium", "initial_git_branch"=>"", "initial_git_url"=>"", "name"=>"nanfusecoursetest1"} (pid:12413) > 2015-09-08 17:24:53.751 [INFO ] Completed 201 Created in 138967ms (Views: 10.9ms) (pid:12413) > 2015-09-08 17:24:56.599 [INFO ] Started GET "/broker/rest/application/55ef519a7577e6d79a000027.json" for 127.0.0.1 at 2015-09-08 17:24:56 -0400 (pid:12413) > 2015-09-08 17:24:56.609 [INFO ] Processing by ApplicationsController#show as JSON (pid:12413) > 2015-09-08 17:24:56.612 [INFO ] Parameters: {"id"=>"55ef519a7577e6d79a000027"} (pid:12413) > 2015-09-08 17:24:56.679 [INFO ] Completed 200 OK in 66ms (Views: 2.3ms) (pid:12413) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016