https://DevOpsCloud.io -- Cloud Monk Losang Jinpa

Return to Continuous Delivery by Jez Humble and David Farley, CI/CD, CI/CD Bibliography - CI/CD People, CI/CD, CI/CD and DevOps - CI/CD and SRE - Cloud Native and CI/CD - CI/CD and Microservices - Serverless CI/CD, CI/CD Security - CI/CD and DevSecOps, Functional Programming and CI/CD, CI/CD Concurrency, CI/CD and Data Science - CI/CD and Databases, CI/CD and Machine Learning, CI/CD Courses, CI/CD Glossary, Awesome CI/CD, CI/CD GitHub, CI/CD Topics

Fair Use Source: B003YMNVC0 (CDHumbFarl 2010)

“ (CDHumbFarl 2010)

Footnotes

Preface

1. Implementing Lean Software Development]], p. 59.

Chapter 2

1. Technically, configuration information can be thought of as a set of tuples.

Chapter 4

1. For example, James Shore [dsyXYv].

2. “Exploratory Testing Explained” by James Bach [9BRHOz], p. 2.

3. Section 5.7, pp. 136–140.

Chapter 5

1. The importance of iterative discovery]] based on customer feedback in the product development]] process is empha[[sized in books like Inspired by Marty Cagan and The Four Steps to the Epiphany by Steven Gary Blank.

2. Chris Read came up with this idea [9EIHHS].

3. Evans, 2004.

4. Implementing Lean Software Development]], p. 59.

Chapter 6

1. Buildr also handles Scala, Groovy, and Ruby seamlessly at the time of writing — by the time you read this, we expect it to support more languages that target the JVM.

2. Things are s[[lightly more complex in Java. At the time of writing, Sun’s Javac compiler did not do incremental builds (hence the Ant task), but IBM’s Jikes compiler could. However, the javac task in Ant will perform incremental compilation.

3. See Evans (2003).

4. There are example commit scripts for Ant, Maven, MSBuild, and Psake at the book’s website [dzMeNE].

5. CPAN is one of the better-designed platform packaging systems, in that it is possible to convert a Perl module into a RedHat or Debian package in a fully automated way. If all platform package formats were designed to allow for automatic conversion to system package formats, this conflict would not exist.

6. Unlike Rails, which enforces the directory structure, and the .NET toolchain]], which will also handle some of this for you.

7. Check out Jean-Paul Boodhoo’s blog entry [ahdDZO].

Chapter 7

1. James Carr has a good blog entry with some TDD patterns [cX6V1k].

Chapter 8

1. Bob Martin articulates some of the reasons for why automating acceptance testing is important and should not be outsourced [dB6JQ1].

2. Advocates of this approach include J. B. Rainsberger, as described in his “Integrated Tests Are a Scam” blog entry [a0tjh0], and James Shore, in his “The Problems with Acceptance Testing” blog entry [dsyXYv].

3. That is, they must be independent, negotiable, valuable, estimable, small, and testable.

4. At the time of writing, Flex fell into this category — hopefully by the time you read this, new testing frameworks will have sprung up to drive testing through Flex.

5. Twist, a commercial tool created by Jez’ employer, allows you to use Eclipse’s auto[[complete functionality and parameter lookup on your acceptance criteria scripts directly, and allows you to refactor the scripts and the underlying test implementation layer while keeping the two syn[[chronized]].

6. Nygard, 2007, p. 115.

Chapter 9

1. Nygard, 2007, p. 151.

2. Nygard, 2007, p. 76.

3. Nygard, 2007, p. 142.

4. Nygard, 2007, p. 61.

Chapter 10

1. The Unity 3D web p[[layer software publishes statistics on its site [cFI7XI].

2. For a great analysis of the evolution of Amazon’s shopping cart]], check out [blrMWp].

3. Google created a framework called Protocol Buffers for all its internal services, designed to handle versioning [beffuK].

Chapter 11

1. Some of these are inspired by James White [9QRI77].

2. For the purposes of this chapter, we will consider support to be part of the work of operations, although this is not always the case.

3. Nygard, 2007, p. 222.

4. Microsoft’s Azure provides some services that count as infrastructure in the cloud. However, their virtual machine offering has some of the characteristics of platforms in the cloud, since at the time of writing you do not have administrator access to VMs and thus cannot change their configuration or install [[software that requires elevated privileges.

Chapter 13

1. We discuss branching]] strategies in the next chapter, “Advanced Version Control.”

2. There are caveats here on the use of distributed version control systems, which we’ll discuss in the next chapter.

3. In Windows [[XP, the introduction of registration-free COM allowed applications to store DLLs they require in their own directory.

4. Melvin E. Conway, How Do Committees Invent, Datamation 14:5:28–31.

5. MacCormack, Rusnak, Baldwin, Exploring the Duality between Product and Organizational Architectures: A Test of the Mirroring Hypothesis, government intelligence]] center Harvard Business School [8XYofQ].

6. Local repositories will periodically update from remote repositories — although it is possible to store snapshots in remote repositories, it is not a good idea.

Chapter 14

1. While the distinction]] between open source and commercial system]]s is important for your freedoms as a consumer, it is worth noting that Subversion is maintained by a commercial organization, Collabnet, which provides paid support.

2. For a humorous look at the major open source version control systems, see [bnb6MF].

3. RCS, like SCCS, only works on local filesystems.

4. We prefer the more general term “change set” to “revision,” but Subversion exclusively uses “revision.”

5. Indeed VSS recommends that you run a database integrity checker at least once a week when running VSS [c2M8mf].

6. Taken from Appleton et al., 1998 [dAI5I4].

7. As described in Version Control for Multiple Agile Teams by Henrik Kniberg [ctlRvc].

Chapter 15

1. ACM, 1984, vol. 27 issue 9.

2. As we say above, we believe iterations should be time-boxed to two weeks, not four.

Fair Use Sources:

• Continuous Delivery by Jez Humble and David Farley on DuckDuckGo
• B003YMNVC0 (CDHumbFarl 2010)