This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 181351 - Unable to clone NetBeans repository
Summary: Unable to clone NetBeans repository
Status: RESOLVED WORKSFORME
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: PC Other
: P1 normal (vote)
Assignee: rnovak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-01 05:40 UTC by Adam Sotona
Modified: 2010-10-13 07:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Sotona 2010-03-01 05:40:02 UTC
Today morning I started clonning of hg.netbeans.org/main, after 4 hours was clonning still in progress. After my return from lunch was my computer asleep and the transaction was rolled back when the computer woke up. Now it is afternoon and I have to start again with turned off my power management and pry for operation to finish.
The performance and usability of our versioning system is back to StartTeam times 10 years ago.
Comment 1 Jesse Glick 2010-03-01 09:24:51 UTC
Why are you doing a fresh clone, anyway? This puts a lot of load on the server. You should have created one clone of main a couple of years ago and never need to again, since you can make local clones and then update them as needed. Unless of course your hard drive crashed, etc.
Comment 2 rnovak 2010-03-01 09:28:27 UTC
If you are cloning from sun network and it take too long time, you should report the network problem as I described you in the email.
Comment 3 Adam Sotona 2010-03-01 09:57:02 UTC
Jesse almost hit it - OS change. And I do not backup my Mercurial clones.

It is right, it is heavy load on the server, Internet lines and 2GB of HG
metadata + 1GB of workdir sources is big piece of something laying on every
developers drive. Such big transaction that could not be interrupted and I even
had to do it twice because it failed for the first time. I can report a network problem, our network lines should be faster, but is it really necessary? 

The true is I don't even need it. I had to fix just one single file. I had to
transfer almost 4GB of data and spend 6 hours to access Mobility sources (15MB)
and fix one file. These times were usual before Jesse migrated NetBeans to CVS.
Now I think we've probably outgrown the single HG repository.
Comment 4 rnovak 2010-03-05 06:26:41 UTC
As a build engineer I need to clone more often then other people and it never takes more then 3 hours. If it is taking 4 and more hours this is really network issue not related to Hg server.

I'm closing this ticket as works for me, since I didn't see other report that cloning takes significantly long. 

In you case it would probably help if you could clone only a part of the repository, but this is not supported scenario for now.