15 plus best practices for continuous integration of your software

Here is a list of 15 plus continuous integration tips or do’s and don’ts for your software. If you have more tips, please add them to the comment section. I will pick it up from there and add it to this list.

  1. Maintain single source code repository
  2. Commit code frequently. Ideally have everyone in your team commit their code everyday.
  3. Run all test cases / test suites locally before committing your code to the repository.
  4. Never check-in a broken build – if you found broken test cases, fix those before committing the code.
  5. If you checked in a code that broke the build, fix it. Take responsibility on the build that you broke.
  6. Don’t comment out failing test cases – fix them.
  7. Automate the build process using tools like Ant or Maven.
  8. Automate the unit tests so that on every build whole set of test cases run.
  9. Make a clear separation of Unit Tests and Integratio Tests
  10. Configure the build so that every commit to the repository triggers a build.
  11. Keep the builds fast – fail the build if it runs for too long and optimize the build process.
  12. Replicate production environment as closely as possible on your test environments.
  13. Make the results of your test cases visible to everyone in your team.
  14. Send an email to the team for every build – both for success and failure.
  15. Auotmate your deployment process – ideally set up a trigger to run a deployment once the build is complete.
  16. Run static code analysis tools like checkstyle on your every build and fail the build in case of violations.


[My Video Promotion]
  1. Pair Programming – A Comprehensive Guide To Get You Going
  2. Why The Idea Of Test Driven Development (TDD) Royally Upsets Me
  3. 12 Basic Principles That Underlie The Agile Manifesto With Text From Original Manifesto
  4. 12 Practices That Make Up Extreme Programming In Agile Software Development Methodology
  5. How to build a specific SVN (Subversion) revision in Hudson and Jenkins
  6. 15 Agile Best Practices – Are you following these in your team?
  7. What is the format for writing an agile story card?
  8. How the Agile Teams and Organizations Mature and Become Fluent
  9. N-Things You Can Do With Continuous Integration Tools Hudson and Jenkins
  10. List of some popular agile methodologies of software development practices
  11. The chicken and pig cartoon for Agile Project Management – high resolution version recreated
  12. Configuring Hudson Java Memory Settings When Running It As A Service
  13. Why is Fibonacci series numbers used in Agile Planning and Estimations?
  14. What Makes An Agile Story Good? It’s the INVESTment.
  15. Roles and Responsibilities of Business Product Owner in Agile Teams
  16. 100 Plus Agile Terms – A Comprehensive List
  17. How to manually install Hudson or Jenkins Plugin?
  18. 15 plus best practices for continuous integration of your software
  19. Iterative development benefits in the Agile software development
Tagged , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.