The slides for my TeamCity presentation in Malmo, Sweden, 10th Feb 2009

1. TeamCity
Delivering Quality Software, on Time
Vaclav Pech
Software Developer and Product Evangelist
JetBrains, Inc.
www.jetbrains.com

2. Part 1: Continuous integration
Compile Test / Analyse
Report
Trigger (by change)
2
www.jetbrains.com

3. TeamCity is a …
• Continuous integration tool
– Quality control
– Team cooperation
– IDE-independent
– Java + .Net
3
www.jetbrains.com

4. Integration
• CVS, SVN, ClearCase, …
• Ant, Maven 2, IntelliJ IDEA, Nant, …
• Email, RSS, Jabber, IDE, Windows Tray
• Eclipse, IntelliJ IDEA, Visual Studio
• JUnit, TestNG, EMMA, Cobertura
4
www.jetbrains.com

5. Architecture
5
www.jetbrains.com

6. Part 2:
• TeamCity solving problems
6
www.jetbrains.com

7. Problem:
• Administration headaches
– Multiple projects and build
configurations
– Cumbersome administration of multiple
build machines
7
www.jetbrains.com

8. Solution: Distributed builds
8
www.jetbrains.com

9. Solution: Distributed builds
• Multi-platform testing
• Easy administration
• Optimized task distribution
9
www.jetbrains.com

10. Problem:
• Notification spam
– People stop reading notifications
– People stop reading notifications
– People stop reading notifications
– People stop reading notifications
– People stop reading notifications
– People stop reading notifications
– People stop reading notifications
10
www.jetbrains.com

11. Solution: Clean and fast notifications
• Relevant
• Convenient
• Early
11
www.jetbrains.com

12. Problem:
• Nobody fixes the build
12
www.jetbrains.com

13. Solution: Take responsibility
• Indicate explicitly that you’re fixing it
13
www.jetbrains.com

14. Problem:
• Locating failures
14
www.jetbrains.com

15. Solution: IDE integration
• Show results just as if ran locally
• Direct links to the source code
15
www.jetbrains.com

16. Problem:
• Developers don’t check code quality
often enough
– Interrupts work flow
– Takes time, decreases productivity
16
www.jetbrains.com

17. Solution: Server checks for quality
• Inspections
– 700+ rules for Java, JavaScript, HTML,
XML, …
• Code coverage
• Code duplicates
17
www.jetbrains.com

18. Problem:
• Broken builds after commit
– 5 o’clock checkin case
18
www.jetbrains.com

19. Solution: Pre-tested commit
• The server integrates your local
changes before committing to VCS
19
www.jetbrains.com

20. 20
www.jetbrains.com

21. Summary
• CI is a must but has obstacles
• TeamCity makes CI smooth
• Free Professional Edition
– Contact me: vaclav@jetbrains.com
21
www.jetbrains.com

22. Questions
22
www.jetbrains.com