continuous integration - step by step
DESCRIPTION
Continuous integration (CI) allows you to check the quality of your project on every developer commit. It's a key part of any Agile environment. We will start with a 5 year old ASP.NET WebPages application and put it under CI with unit testing and other key metrics. The web project, has no modern best practices at all. This talk will demonstrate, step-by-step and line-by-line, adding a project to a continuous integration (CI) server. The end result will be a project with the following: - Automatic build on check-in - Automatic reporting of unit tests - Code duplication reporting - Warning analysis - REM: Automatic database upgrade This will be great if you work with legacy code and feel the CI hurdle is big.TRANSCRIPT
About Me
Software Developer
Agile Team Member
Team Lead
Agile Advocate
SDLC Implementer
The measurement process
Take ActionIdentify ProblemsMeasure
SDLC
What is Continuous Integration?
The practice of merging all developer working copies with a shared mainline several times a day.
Ingredients• A Server• CI Software• Jenkins, TeamCity, TFS, CruiseControl.NET
• Revision Control• A little patience … or consultant
What it looks like?
Revision Control
CI ServerDeveloper
Step 1• You MUST be able to build from the command line
Step 2• Configure CI
Step 3• Enjoy.
Contact MeBarrett [email protected]://wbsimms.comTwitter: @wbsimmsPhone: 781.405.4686