Link Details

Link 919387 thumbnail
User 1059809 avatar

By egregory
Published: Feb 06 2013 / 09:33

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.
  • 6
  • 2
  • 549
  • 583


Add your comment
User 226303 avatar

devdanke replied ago:

0 votes Vote down Vote up Reply

User 226303 avatar

devdanke replied ago:

1 votes Vote down Vote up Reply

* "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.

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.

Voters For This Link (6)

Voters Against This Link (2)

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java