With an eye to agile development principles and fast-feedback, we want a build system which satisfies the following goals:
* Every SCM change-set committed should result in a potentially shippable release candidate.
* When a defect is introduced, we want to immediately detect and isolate the offending SCM change-set. This is true even if the defect was introduced into a library we depend upon.
* Library management should be so easy as to never impede code changes, even in multi-component architecture.
More details available at: http://teamfruit.github.io/defend_against_fruit/
License: Apache Public License v2
Authors:
James Carpenter jcarpenter621 at yahoo.com LinkedIn: http://www.linkedin.com/in/jamescarpenter1
Matthew Tardiff mattrix at gmail.com LinkedIn: http://www.linkedin.com/in/matthewtardiff