This documentation works through increasingly complex use cases. It is discouraged to open the CDAF code and try to determine it’s purpose from the code (although it’s open source, so you’re most welcome). The framework uses a significant amount of dependeny injection, and without an understanding of the purpose, the code will be quite difficult to follow.
|What CDAF isn’t
|What CDAF is
|The Continuous Delivery Automation Framework Does not give you DevOps
|The Continuous Delivery Automation Framework is optionated to help you achieve DevOps principles for Continuous Delivery
|CDAF is not a replacement of your CI/CD orchestration tool.
|CDAF is loosely coupled, allowing you to test your automation before executing in your orchestration tool.
|It does not replace your build tools, such as MSBuild, Maven, Ant, etc.
|It provides a execution engine for your build tasks, to cater for loggingm, error and exception handling.
|CDAF does not know how to deploy your application nor;
does it know how to manage the configuration.
|CDAF provides delivery helpers for common deployment tasks.
A tabular abstraction engine is provided to support tokenised configuration files
Before jumping in, we recommend reading the Introduction to understand the core objectives of CDAF and the principles appied to reach these goals.