Anthill Pro and CI
Anthill Pro and CI
Anthill Pro and CI
Benefits
Reduces Risk Ensure Quality Ensure Quality Ensure Quality
Separation of Duties
Hashing Artifacts Managing Dependencies Process Automation
Reduces Risk
Reduces Risk Reduces Risk Increased Efficiency
CI Best Practice
Before Continuous Integration:
Numerous development changes over long period of time without SCM commit
Test scenarios often fail and not run often due to manual intervention
Dev Team must now find and fix the code Delays to the project schedules occur.
CI Best Practice
AnthillPro implementing Continuous Integration 1. Dev Team integrates source code changes continuously. 2. Dev Team receives quick feedback of build, test, and analysis results. 3. Since the changes were just made, the problems are much easier found and fixed. 4. Code base becomes stable, quality increased, and project risk decreases.
SCM Repository
Build Server
2. Trigger DEV Build
Developer
Anthill Server
3. Build
Tool
SCM Build JUnit NUnit Cobertura Emma FindBugs PMD CheckStyle Instant Feedback
Details
Harvest, CVSNT, Clearcase, Subversion Ant, NAnt, Maven http://junit.sourceforge.net/ http://sourceforge.net/projects/nunit http://cobertura.sourceforge.net http://emma.sourceforge.net/ http://findbugs.sourceforge.net http://pmd.sourceforge.net/ http://checkstyle.sourceforge.net/ Email IM
Unit Tests
Code Coverage
Bug Scan
Savings
Action Triggered Build Unit Tests Type Reduces Risk Ensure Quality Savings Increases Build Success Promotes Frequent Check-ins Fewer Production issues
AnthillPro and CI
Demo
Builders
Ant/NAnt Make Maven MSBuild
Defect Tracking
Bugzilla ClearQuest JIRA Maven PVCS Tracker Quality Center Rally TeamTrack Version One Team Foundation Server ViewVC VMWare Lab Manager
Automated Testing
Agitar CppUnit JUnit Mercury NUnit Selenium Silk Central Test Manager
Test Coverage
Clover Cobertura Emma
Tools not listed can still be executed and have their reports published by AnthillPro
http://www.anthillpro.com