Bug 373071 - When materializtion needs to clone a Git repository, but the clone operation fails, all future attempts fail
Summary: When materializtion needs to clone a Git repository, but the clone operation ...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-02 06:50 EST by Matthew Webber CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Webber CLA 2012-03-02 06:50:38 EST 
Build Identifier: Eclipse 3.7.1 with Buckminster 1.4.0 and Egit/JGit 1.2.0

This seems to be a common problem for us:

I run Buckminster materialization. The RMap tells it to clone a remote repository, but the clone operation fails. This can happen for a variety of reasons: user is not authorised to access the remote repository, there is a network issues, certificate problem,  etc.

So, I fix up the problem and run materialization again. This should work, but fails.

The cause is that the initial attempt at cloning creates a directory to hold the local clone. This directory is partially populated by the failed clone operation, and is not deleted when the operation fails.

This incomplete directory causes all subsequent materialize attempts to fail (even though git.auto.fetch=true). This is because the local clone is in a partial, invalid state. The user needs to delete the directory in order for materialization to work, but it's not at all obvious that this needs to be done.

Either Buckminster or JGit should delete the directory resulting from a failed clone operation.


Reproducible: Always