I’m encountering a sporadic problem with gradle 1.0 milestone 7.
I have a project with 4 repositories configured, 2 maven and 2 SVN, like this:
mavenRepo name: “internal-repo-site-cache”,
mavenRepo name: “internal-repo”,
mavenRepo name: “svn-repo”,
mavenRepo name: “svn-repo-mirror”,
Since upgrading to m7 a few builds have failed in the CI build system because a jar could not be retrieved from SVN.
Download failed for artifact 'com.atomikos:transactions-essentials-all:3.5.13@jar': Could not GET 'http://svn1:18080/svn/main/repository/com/atomikos/transactions-essentials-all/3.5.13/transactions-essentials-all-3.5.13.jar'.
2 things are strange about this: 1. I know that the jar file is available. All manual tests I’ve done show this. A build never failed with this reason with previous versions of gradle. 2. Why doesn’t gradle attempt to use the next repository, svn-repo-mirror? The svn-repo repository is not situated in the same data center as the CI server, so the response time for this retrieval may be slow. But that is why I have the alternate repository configured. This is in the same data center and I expect would respond well. So why is it not picked up from there?
I am not able to find any open issues about this problem.
Any suggestions on how I could implement a work around?
All help on would be greatly appreciated!