[
https://issues.jboss.org/browse/JBIDE-11361?page=com.atlassian.jira.plugi...
]
Burr Sutter commented on JBIDE-11361:
-------------------------------------
One of the end-user workaround to a timeout is to:
1) Cancel the wizard and go about your business
2) Check the
openshift.com express console a few minutes later
3) When they see their app provisioned, click on its URL to double check the default app
is loading correctly
4) Restart the OpenShift Application Wizard
5) Select Existing Application (created during the first phase)
6) Select Existing Project
Another solution for step 2 above is to use the OpenShift Express Console inside of
JBDS/Tools to "monitor" the application and see when its default pages have been
provisioned.
Does that sound about right?
Increase OpenShift wizards timeouts
-----------------------------------
Key: JBIDE-11361
URL:
https://issues.jboss.org/browse/JBIDE-11361
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
OpenShift takes a lot more time to create applications lately. Where 10 seconds where
enough initially, 2 minutes and more are needed since the end of last year. For the user
this is kinda annoying: when he's creating a new app in the wizard, he gets the
message that we timeouted while waiting for the new application to become ready. He then
has to close the wizard, check if the application was created (in the console or in an
import wizard). He'll then be able to import the existing application and get the git
repo cloned to his local workspace. We can improve this considerably by increasing the
timeout to 2 or even 3 minutes. The user would then eventually have to wait for much more
time but he'll be able to follow the normal workflow in many more cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira