Hi, is it possible that the Cache is located on a different harddrive? I don't know when we had an issue like this with moving files. Maybe it was buildr and not Ivy related. It boiled down to: The move did not work, because it is not implemented as copy/delete but as a real move, this fails for temp dir on a different drive.
This may be complete non sense, but was the first thing that came to my mind. Regards Klaas -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Gesendet: Mittwoch, 24. Februar 2010 17:38 An: [email protected]; Eugene Sajine Betreff: Ivy + hudson CI - problems downloading artifacts, please, help Hi, I'm not subscribed to the list, so, please, make sure you have my address in CC for replies. We are having more than 150 projects in hudson CI with dependencies tracked by Ivy (2.1.0). Lately we are having more and more problems with it because ivy cannot copy/download artifacts correctly. There are two main errors we are getting: 1. size of source file differs from the size of dest file 2. impossible to move part file to definitive one In mailing list i found this answer from Xavier Hanin: When Ivy downloads ivy files from a repository, it first download them to a temporary file (used to be in temp directory until 2.0 beta 1, where the ivy file is downloaded to the cache). Then it moves the temporary file to the final location in the cache, and this is what seems to be failing for your user. Cleaning the cache should fix the problem, if it happens frequently you should try to investigate the issue. Maybe it is due to the use of the same cache by multiple processes concurrently. This use case is supported only with 2.0 beta 1, with the repository cache locking to avoid such concurrency issues. As i mentioned above our version is 2.1.0, but we still have this issue I also saw the same problem reported before, but there was no answer http://www.mail-archive.com/[email protected]/msg03152.html Thanks, Eugene
