[JBoss JIRA] (JBIDE-11367) Run jobs outside of Wizards instead of within container (wizard launches background jobs and closes)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11367?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11367:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Run jobs outside of Wizards instead of within container (wizard launches background jobs and closes)
> ----------------------------------------------------------------------------------------------------
>
> 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
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBIDE-12255) Biggest usability issue for OpenShift when presenting
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12255?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12255:
-------------------------------------
Description:
Biggest problems when using and presenting OpenShift:
* "waiting to be reachable" is waay to slow to detect the app - the app is running, but still waiting to be reachable
-> solved when JBIDE-13569 removed the health check, waiting for application now only waits for successfull DNS-resolution
* Creation of application blocks the UI - we should make it possible to put in the background to be able to show other things.
-> adressed in JBIDE-11367
* Progress for push is showing nothing of all the text output - egit commit/push dialog does this; we should too.
-> adressed in JBIDE-12137
was:
Biggest problems when using and presenting OpenShift:
* "waiting to be reachable" is waay to slow to detect the app - the app is running, but still waiting to be reachable
* Creation of application blocks the UI - we should make it possible to put in the background to be able to show other things.
-> adressed in JBIDE-11367
* Progress for push is showing nothing of all the text output - egit commit/push dialog does this; we should too.
-> adressed in JBIDE-12137
> Biggest usability issue for OpenShift when presenting
> -----------------------------------------------------
>
> Key: JBIDE-12255
> URL: https://issues.jboss.org/browse/JBIDE-12255
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.x
>
>
> Biggest problems when using and presenting OpenShift:
> * "waiting to be reachable" is waay to slow to detect the app - the app is running, but still waiting to be reachable
> -> solved when JBIDE-13569 removed the health check, waiting for application now only waits for successfull DNS-resolution
> * Creation of application blocks the UI - we should make it possible to put in the background to be able to show other things.
> -> adressed in JBIDE-11367
> * Progress for push is showing nothing of all the text output - egit commit/push dialog does this; we should too.
> -> adressed in JBIDE-12137
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12098?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12098:
------------------------------------------
postponed to 4.2.x
> OpenShift Explorer: Timeout exception when forcing domain deletion
> ------------------------------------------------------------------
>
> Key: JBIDE-12098
> URL: https://issues.jboss.org/browse/JBIDE-12098
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: deletedomain.png
>
>
> Tried to force domain deletion while having (medium geared) application on OpenShift.
> Screenshot:
> !deletedomain.png|thumbnail!
> Stack trace:
> {code}
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:89)
> at com.openshift.internal.client.RestService.request(RestService.java:74)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329)
> at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166)
> at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBIDE-12116) Cannot cancel Verifying SSH session job's dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12116?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-12116:
------------------------------------------
postponed to 4.2.x
> Cannot cancel Verifying SSH session job's dialog
> ------------------------------------------------
>
> Key: JBIDE-12116
> URL: https://issues.jboss.org/browse/JBIDE-12116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: dialog.jpg
>
>
> When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway.
> !dialog.jpg!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBIDE-12098) OpenShift Explorer: Timeout exception when forcing domain deletion
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12098?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12098:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> OpenShift Explorer: Timeout exception when forcing domain deletion
> ------------------------------------------------------------------
>
> Key: JBIDE-12098
> URL: https://issues.jboss.org/browse/JBIDE-12098
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: deletedomain.png
>
>
> Tried to force domain deletion while having (medium geared) application on OpenShift.
> Screenshot:
> !deletedomain.png|thumbnail!
> Stack trace:
> {code}
> com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/rhdomain, connection timed out
> at com.openshift.internal.client.RestService.request(RestService.java:109)
> at com.openshift.internal.client.RestService.request(RestService.java:89)
> at com.openshift.internal.client.RestService.request(RestService.java:74)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137)
> at com.openshift.internal.client.DomainResource$DeleteDomainRequest.execute(DomainResource.java:329)
> at com.openshift.internal.client.DomainResource.destroy(DomainResource.java:166)
> at org.jboss.tools.openshift.express.internal.ui.action.DeleteDomainAction$1.run(DeleteDomainAction.java:94)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBIDE-12116) Cannot cancel Verifying SSH session job's dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12116?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12116:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Cannot cancel Verifying SSH session job's dialog
> ------------------------------------------------
>
> Key: JBIDE-12116
> URL: https://issues.jboss.org/browse/JBIDE-12116
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: dialog.jpg
>
>
> When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway.
> !dialog.jpg!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months