Link Details

For years I've been taught that breaking continuous integration build is something that should be avoided under all circumstances. Let me first quote few classics.

Posted by egregory  |   Feb 06 2013 / 09:33

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Comments

User 226303 avatar

devdanke replied ago:

Reply 0 votes
User 226303 avatar

devdanke replied ago:

* "Avoid breaking the build". * "If you break the build, make it a top priority to fix it ASAP". * "Unit/Integration tests should always pass, unless a pre-arranged, unavoidable breakage is required". These are Best Practices and should continue to be. Someone on your team may think they're so clever, they don't need software development Best Practices. Yes, it can be done. But 95% of the time, doing so will take longer, take more effort, produce more frustration, cost more money, and result in harder to maintain software. Be suspicious of those who think they're too clever to follow Best Practices. Most likely, they're fools looking for a short-term win, while others pay the price for their foolishness later. Deviate from Best Practices (the accumulated wisdom, earned from years of experience, of developers just like you) at your own risk.

Reply 1 votes

Recommended Links

Scala
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone