This document discusses setting up continuous integration with Teamcity. It defines continuous integration as making builds small and frequent, visualizing the build process, minimizing broken build time, and enabling continuous integrated and automated testing. It provides an overview of Teamcity's capabilities for continuous integration including running builds, unit tests, acceptance tests, code reviews, and automated deployments. It also demonstrates these features through a live demo and discusses how Teamcity helps new developers identify and fix errors.

1. Continuous Integration with
Teamcity

2. • Did you ever get broken build from TFS?

3. Did you ever
get unexpected exceptions on the page
after someone checked-in?

4. Did you ever
get unexpected exceptions in sublayouts
after someone checked-in?

5. Did you?
• Get errors on dev env which are not on local?
• How frequent you run unit test?
• What about acceptance tests?
• How do you perform code review?
• Do you always have dev env up to date?
• …

6. Continuous Integration
But what is it???

8. Why we need CI?
• Big and long integration to small and frequent
• Visualize the build process, !!!Alarm!!!
• Minimize ”broken build time”
• Continuous Integrated testing
• Continuous Auto deployment
• Continuous code inspection

9. What systems do we know?
• Cruise Control .NET (open source)
• TFS Builds (Microsoft TFS)
• Bamboo (Atlassian)
• TeamCity (JetBrains)
• …

10. TeamCity

11. Download and Install

12. Open and Register Admin Account

13. Create a project

14. Build configuration

15. VCS settings

16. Build triggers

17. Step1 - Build Sources

18. Step2 - UnitTests run

19. Deployment configuration
• Create new configuration “Deployment”
• Trigger “Deployment” if Trunk build succeeded
• Setup Artifact dependencies to Trunk build and
copy them to Dev site.

20. Step1 – Acceptance tests run

21. What you can do more?
• Code Coverage (ncover/dotCover/…)
• Find Duplicates
• Code inspections (FxCop, Inspections)
• HTML/css validation W3C
• Run nAnt / Powershel / Command line
operations

22. What we have to install?
• Visual Studio 2010 (MSBuild, MSTest)
• TeamCity 6.5
• Entity Framework 4.1
• Firefox (for Acceptance tests)

23. Live demo
• TFS checking trigger
• Running build
• UnitTests results
• Build logs
• Code Review - changeset
• Auto Deployment to dev
• Acceptance Tests results

24. I’m New developer
• Subayouts Error
• Page Error
• Source Code Error
• Run build
• See logs, status, screenshot
• Fix errors
• Run build
• See status

25. Look a bit more
• Test Performance history
• Code Coverage
• Code Inspection
• Code Duplication
• …