1 / 10

Using a Continuous Integration Server

Using a Continuous Integration Server. Sean Chambers. About Sean. Senior Developer at Flagler County Schools for 5 years Owner Hybrid Software, Educational Software Contributor to various open source projects (Castle Project, NHibernate , NUnit , NBehave )

caine
Télécharger la présentation

Using a Continuous Integration Server

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using a Continuous Integration Server Sean Chambers

  2. About Sean • Senior Developer at Flagler County Schools for 5 years • Owner Hybrid Software, Educational Software • Contributor to various open source projects (Castle Project, NHibernate, NUnit, NBehave) • Practicing TDD,DDD,BDD for 2 years • Blog: http://schambers.lostechies.com •  Twitter: schambers

  3. What is CI? • Software package to integrate the development of software on a daily process

  4. Where? • CI was originated from the XP community • Developed by Martin Fowler and Kent Beck

  5. How can it help me? • Instant feedback of bugs • Executes tests, reports automatically • Like having another developer present to compile • Automates the build process • Automates report generation • Constant monitor for TDD code coverage

  6. What do I need? • CI Server • TeamCity • CruiseControl.NET • Source Control software • SVN • VSS • CVS • Build script • Nant • msbuild

  7. Nant/MsBuild • Use a build script to leverage CI • Bootstrap report generation via build script • NCover • Ndepend • NUnit

  8. Commit early, commit often • Make sure every developer commits everyday

  9. Label your builds • Create label/tag for each published version • Label/tag a nightly build

  10. TeamCity Sample

More Related