[jbosstools-issues] [JBoss JIRA] (JBIDE-12812) Provide user-friendly way to increase Git timeout

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12811475#comment-12811475 ] 

Andre Dietisheim commented on JBIDE-12812:
------------------------------------------

I just looked it up. We can provide a specific timeout when cloning. The CloneOperation that we use to clone offers a constructor which allows us to provide a timeout. The timout will affect connects and reads.

{code:title=org.eclipse.egit.core.op.CloneOperation}
	public CloneOperation(final URIish uri, final boolean allSelected,
			final Collection<Ref> selectedBranches, final File workdir,
			final String refName, final String remoteName, int timeout) {
{code}
                
> Provide user-friendly way to increase Git timeout
> -------------------------------------------------
>
>                 Key: JBIDE-12812
>                 URL: https://issues.jboss.org/browse/JBIDE-12812
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.0.0.Alpha1
>            Reporter: Stefan Bunciak
>            Assignee: Andre Dietisheim
>            Priority: Critical
>             Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>         Attachments: pushtimeout.png
>
>
> With the default timeout (30s) everytime I follow these steps I get an TimoutException:
> * Import rich-faces project from JBoss Central
> * Create application on OpenShift and merge it with the rich-faces project
> * Select the project - context menu - Team - Push to Upstream
> * Timeout Exception:
> !pushtimeout.png|thumbnail!
> So we should provide a link to 
> {code}Preferences - Team - Git - Remote connection timeout{code} to prevent JBIDE-12430 with some basic explanation of the most probable situation - that the timeout is set too small (like when timed out while creating app).

--
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