28Aug/111
Grails: Speeding up dependency resolution
Something you might want to consider doing in your project is to lock down specific version of your dependencies instead of getting the latest release. The dependencies closure in our BuildConfig.groovy used to look like this:
dependencies { test "org.codehaus.geb:geb-core:latest.release" test "org.codehaus.geb:geb-spock:latest.release" test "org.seleniumhq.selenium:selenium-chrome-driver:latest.release" test "org.seleniumhq.selenium:selenium-firefox-driver:latest.release" test "org.seleniumhq.selenium:selenium-ie-driver:latest.release" test "org.spockframework:spock-core:0.5-groovy-1.7" }
Every script we ran took about 30-45 secs to resolve dependencies before it did anything, which was quite ridiculous. So after some digging around, Ben and I found out that if we specified the version of the plugins we wanted, that would drastically reduce the time spent resolving those dependencies.
This configuration shaved off about 20-35 seconds from our build:
dependencies { test "org.codehaus.geb:geb-core:0.6.0" test "org.codehaus.geb:geb-spock:0.6.0" test "org.seleniumhq.selenium:selenium-chrome-driver:2.4.0" test "org.seleniumhq.selenium:selenium-firefox-driver:2.4.0" test "org.seleniumhq.selenium:selenium-ie-driver:2.4.0" test "org.spockframework:spock-core:0.5-groovy-1.7" }
Contact Me
Archives
- January 2012 (2)
- December 2011 (1)
- October 2011 (1)
- August 2011 (3)
- June 2011 (2)
- March 2011 (1)
- February 2011 (1)
- November 2010 (3)
- September 2010 (1)
- August 2010 (1)
- July 2010 (2)
- June 2010 (1)
- May 2010 (2)
- April 2010 (2)
- March 2010 (4)
- February 2010 (1)
- November 2009 (5)
- October 2009 (4)
- September 2009 (2)
- August 2009 (3)
- July 2009 (2)
- May 2009 (4)
- April 2009 (9)
- March 2009 (1)
- February 2009 (5)
- January 2009 (4)
- December 2008 (6)
- November 2008 (5)
- October 2008 (3)
- September 2008 (1)
- August 2008 (1)
Categories
- .net (3)
- active record (1)
- agile (9)
- band (1)
- books (13)
- c# (3)
- clojure (2)
- coding (2)
- coding practices (8)
- conferences (1)
- consulting (3)
- continuous intergration (2)
- error handling (1)
- flex (3)
- functional programming (2)
- git (1)
- grails (2)
- hibernate (1)
- integration (2)
- java (2)
- lean (2)
- logging (1)
- mocking (1)
- music (1)
- oop (1)
- osx (2)
- pairing (6)
- philosophy (2)
- photography (1)
- rails (1)
- ramble (10)
- ruby (2)
- Sydney (3)
- tdd (2)
- teamwork (5)
- testing (17)
- ThoughtWorks (19)
- twu (2)
- UI (3)
- web (1)
November 28th, 2011 - 00:16
That’s great.
Our mistake that we never tried digging it up. If we would have known that earlier, we would have saved a considerable amount of time on Frontline SMS Legal.