I'm running bamboo cloud and starting my gradle build like this with a script task
chmod +x gradlew ./gradlew clean build
This works, but the resolution of my depencencies is very slow. the network on the other hand is fast (4MB/sec)
but my log says otherwise for jars of less than a megabyte.
My image configuration
Ubuntu: EBS x86_64 (Ubuntu) (stock image) (disabled) | ami-5be8f232 | No EBS | M3 General Purpose Medium |
This is the logging from bamboo, note the timestamps
16-Jan-2015 21:29:26 | Download https://repo1.maven.org/maven2/org/webjars/angularjs/1.2.20/angularjs-1.2.20.pom |
16-Jan-2015 21:33:41 | Download https://repo1.maven.org/maven2/org/sonatype/oss/oss-parent/7/oss-parent-7.pom |
16-Jan-2015 21:37:55 | Download https://repo1.maven.org/maven2/org/webjars/d3js/3.4.11/d3js-3.4.11.pom |
16-Jan-2015 21:46:24 | Download https://repo1.maven.org/maven2/org/webjars/leaflet/0.7.3/leaflet-0.7.3.pom |
Anyone seen this issue? My build runs perfectly on a server instance (but with the gradle plugin)
Same problem here.
If I log on to the bamboo agent and directory download a large dependency (hadoop-yarn-api, which is 1.8MB) with wget, it arrives in under 0.02 seconds. Running gradle from the script task in Bamboo, it sometimes takes several minutes.
However, I think the problem could be to do with Gradle itself, and how long it takes to resolve dependencies.
Have you tried adding the --profile switch to your gradle command, and then creating a new artifact that saves the report (usually it's un build/reports/profile)?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.