Continuous Delivery Flashcards

1
Q

What does Continuous Delivery (CD) do?

A

Automatically moves a software product from a source code repository through to the staging environment, and at the press of a ‘release’ button, it can be moved to production.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does Continuous Deployment (CD) do?

A

Automatically moves a software product from a source code repository to the production environment, without the need to press a ‘release’ button.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is the first principle of Continuous Delivery?

A

1 - Create a Repeatable Process: A process that has been done hundreds of times before, quickly becoming a routine one.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the second principle of Continuous Delivery?

A

2 - Automate Almost Everything: No mistakes (if automation is correct), it’s cheaper, faster, and can record logs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the third principle of Continuous Delivery?

A

3 - Version Control For Everything: Documents, scripts, code, libraries, etc. If something breaks, you can return to the exact previous working state.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is the fourth principle of Continuous Delivery?

A

4 - If It Hurts, Do It More Frequently: Build frequently to improve the process. Eventually, it won’t be painful and smaller changes will be easier to manage.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the fifth principle of Continuous Delivery?

A

5 - Build Quality In: Defects should be fixed as soon as found. Testing should be obsessive, and defects caught early are cheaper to fix.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the sixth principle of Continuous Delivery?

A

6 - Done Means Released: A feature is only considered ‘done’ once it has been released to a production-like environment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the seventh principle of Continuous Delivery?

A

7 - Everyone Is Responsible: The team succeeds or fails as a unit, not as individuals. Collaboration prevents blame-shifting.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the eighth principle of Continuous Delivery?

A

8 - Continuous Improvement: Teams reflect on successes and failures to improve processes and prevent future errors.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is A/B Testing in production?

A

A small percentage of customer traffic is sent to a new interface. If customers are unhappy, all traffic is sent to the old interface.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is Canary Testing in production?

A

A small percentage of customer traffic is sent to a new version. If customers are unhappy, all traffic is sent to the old version.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is Blue/Green Testing in production?

A

The production environment (blue) is swapped with the staging environment (green). If customers are unhappy, the swap is reversed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How can we achieve continuous delivery?

A

Through fast, automated feedback on the production readiness of your applications, every time there is a change (to code/infrastructure/configuration)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What condition should software always be in?

A

Production ready, or releasable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How does continuous delivery help avoid the biggest source of waste in software development?

A

Because its much easier to get new, experimental features into production

17
Q

When should testing be done?

A

All the time, not just once the software has been developed

18
Q

Who is responsible for quality?

19
Q

What is more important than delivering functionality?

A

Keeping the system working and in a good state

20
Q

How does continuous delivery reduce the risk of release?

A

Releasing a small, extensively tested, change - and being able to revert immediately - is not a risky thing to do