Skip to content

Files

Latest commit

 

History

History
41 lines (16 loc) · 2.16 KB

continuous-delivery-in-java.md

File metadata and controls

41 lines (16 loc) · 2.16 KB

Continuous Delivery in Java

> Home

Forewords

There’s been broad agreement in the Continuous Delivery community that tools don’t matter ever since Dave Farley and Jez Humble wrote Continuous Delivery. (link)

Preface

We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at http://bit.ly/continuous-delivery-in-java. (link)

Supplemental material (code examples, exercises, etc.) is available for download at https://github.com/continuous-delivery-in-java. (link)

As the Japanese poet Matsuo Bashō said, “Do not seek to follow in the footsteps of the wise; seek what they sought.” (link)

1. Continuous Delivery: Why and What

USER ACCEPTANCE TESTS At this stage, testers or actual (link)

Vikram: [bookmark]

The primary goal of the build pipeline is to prove that any changes to code or configuration are production-ready (link)

The core idea behind the shift left is that you move things that are typically done in later stages earlier, which results in a high-quality implementation or less cost to fix issues that would be discovered only far into the delivery process. (link)

In 2010, Jez Humble and Dave Farley published their seminal book Continuous Delivery (Addison- (link)

> Home