Difference between revisions of "Long Builds"
From CitconWiki
Jump to navigationJump to search| Line 1: | Line 1: | ||
==Long Builds== | ==Long Builds== | ||
| − | + | * Fast tests run at 100 per second | |
| − | + | * Selective testing | |
| − | + | * running tests in parallel | |
| − | + | * test ordering | |
| − | + | * profiling tests | |
| − | + | * people do checkstyle before functional tests as feedback is quicker | |
| − | + | * Clover now offers selective testing and test re-ordering to FAIL a build faster. [http://blogs.atlassian.com/developer/2009/05/40_7_how_we_sped_up_confluences_build_by_5.html Blog Post] | |
| + | * question as to when static analysis checks should be run in the build – the consensus that running them first means you get the quickest feedback | ||
| + | * longer builds should be run nightly so as not to hold up developers | ||
| + | * prioritising build queues or using different machines sounds like a good idea, but nobody is doing it | ||
| + | * you can reuse functional tests for performance tests, but targeting specific tests seems to work better | ||
| + | * Atlassian use JMeter for performance tests and have a variety of Maven and Ant builds, but use Maven for managing repositories | ||
| + | * Ant is still well regarded, Idea support is awesome, many people do not understand the power of custom ant tasks or the ant idoms | ||
| + | * the build should be regarded as part of your code | ||
| + | * discussion about using a Java build tool, such as Hammer and why we can’t articulate why it seems wrong | ||
| + | * not enough people understand Maven, usually there is “one guy” on the team | ||
| + | * Vizant is a good tool to graph the build | ||
| + | * EasyAnt combines all of the Ant idioms plus Ivy | ||
Latest revision as of 05:13, 6 July 2009
Long Builds
- Fast tests run at 100 per second
- Selective testing
- running tests in parallel
- test ordering
- profiling tests
- people do checkstyle before functional tests as feedback is quicker
- Clover now offers selective testing and test re-ordering to FAIL a build faster. Blog Post
- question as to when static analysis checks should be run in the build – the consensus that running them first means you get the quickest feedback
- longer builds should be run nightly so as not to hold up developers
- prioritising build queues or using different machines sounds like a good idea, but nobody is doing it
- you can reuse functional tests for performance tests, but targeting specific tests seems to work better
- Atlassian use JMeter for performance tests and have a variety of Maven and Ant builds, but use Maven for managing repositories
- Ant is still well regarded, Idea support is awesome, many people do not understand the power of custom ant tasks or the ant idoms
- the build should be regarded as part of your code
- discussion about using a Java build tool, such as Hammer and why we can’t articulate why it seems wrong
- not enough people understand Maven, usually there is “one guy” on the team
- Vizant is a good tool to graph the build
- EasyAnt combines all of the Ant idioms plus Ivy
