Continuous Integration Optimizing Your Release Management Process

Transcription

1 Continuous Integration Optimizing Your Release Management Process

2 Continuous Integration? Why should I care? What s in it for me?

3 Continuous Integration? Why should I care? What s in it for me? The cost of development is only a small part in the TCO

4 Continuous Integration? Why should I care? What s in it for me? The cost of development is only a small part in the TCO Huge part of ge ing software to ship is bug remediation

5 Continuous Integration? Why should I care? What s in it for me? The cost of development is only a small part in the TCO Huge part of ge ing software to ship is bug remediation Commercial development you may only get one chance

6 Continuous Integration? Why should I care? What s in it for me? The cost of development is only a small part in the TCO Huge part of ge ing software to ship is bug remediation Commercial development you may only get one chance IT development schedules depend on being done on time, too!

7 Writing Software is a Wicked Problem

8 Writing Software is a Wicked Problem Wicked problems can only be clearly defined by solving them

9 Writing Software is a Wicked Problem Wicked problems can only be clearly defined by solving them Insufficient design and testing have brought down bridges

10 Writing Software is a Wicked Problem Wicked problems can only be clearly defined by solving them Insufficient design and testing have brought down bridges Software can be brought down in the same way

11 Writing Software is a Wicked Problem Wicked problems can only be clearly defined by solving them Insufficient design and testing have brought down bridges Software can be brought down in the same way Writing software is actually harder than building bridges, because has millions more parts than bridges do

12 So How Exactly Do We Get To Quality in Our Code?

13 So How Exactly Do We Get To Quality in Our Code? Agile is more than just a social process in making software

14 So How Exactly Do We Get To Quality in Our Code? Agile is more than just a social process in making software Being Agile also requires be er engineering practices

15 So How Exactly Do We Get To Quality in Our Code? Agile is more than just a social process in making software Being Agile also requires be er engineering practices Technical excellence and good design enhances agility

16 So How Exactly Do We Get To Quality in Our Code? Agile is more than just a social process in making software Being Agile also requires be er engineering practices Technical excellence and good design enhances agility We get there with extreme Programming practices

17 I Thought My Job Was To Write Code. Now I m Told To Right It!

18 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after

19 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after Constantly fixing mediocre code is expensive

20 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after Constantly fixing mediocre code is expensive Unit testing is the right way to write quality code

21 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after Constantly fixing mediocre code is expensive Unit testing is the right way to write quality code Pair programming allows for constant code reviews

22 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after Constantly fixing mediocre code is expensive Unit testing is the right way to write quality code Pair programming allows for constant code reviews TDD allows for continuous design improvements

23 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after Constantly fixing mediocre code is expensive Unit testing is the right way to write quality code Pair programming allows for constant code reviews TDD allows for continuous design improvements Small releases expose code early and often for user review

24 I Thought My Job Was To Write Code. Now I m Told To Right It! Writing code right is what we are after Constantly fixing mediocre code is expensive Unit testing is the right way to write quality code Pair programming allows for constant code reviews TDD allows for continuous design improvements Small releases expose code early and often for user review CI gives us the time to make all of the above possible

25 What sort of testing do we do?

26 What sort of testing do we do? Doesn t work: ad hoc and V model testing

27 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing

28 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing Unsure of what it means: QA (which is usually QC) testing

29 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing Unsure of what it means: QA (which is usually QC) testing Works and should be automated:

30 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing Unsure of what it means: QA (which is usually QC) testing Works and should be automated: Functional testing (black as well as white box)

31 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing Unsure of what it means: QA (which is usually QC) testing Works and should be automated: Functional testing (black as well as white box) Non-functional testing (performance, volume, stress, etc.)

32 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing Unsure of what it means: QA (which is usually QC) testing Works and should be automated: Functional testing (black as well as white box) Non-functional testing (performance, volume, stress, etc.) Smoke testing

33 What sort of testing do we do? Doesn t work: ad hoc and V model testing Hit or miss: alpha and beta testing Unsure of what it means: QA (which is usually QC) testing Works and should be automated: Functional testing (black as well as white box) Non-functional testing (performance, volume, stress, etc.) Smoke testing Deployment testing

34 How does a Continuous Integration server work?

35 How does a Continuous Integration server work? First need to get what we want to do under scripted control

36 How does a Continuous Integration server work? First need to get what we want to do under scripted control Then, we can use scheduled or triggered automation

37 How does a Continuous Integration server work? First need to get what we want to do under scripted control Then, we can use scheduled or triggered automation Scheduled automation works similar to a cron job

38 How does a Continuous Integration server work? First need to get what we want to do under scripted control Then, we can use scheduled or triggered automation Scheduled automation works similar to a cron job Triggered automation works based on something else happening

39 How does a Continuous Integration server work? First need to get what we want to do under scripted control Then, we can use scheduled or triggered automation Scheduled automation works similar to a cron job Triggered automation works based on something else happening Typical triggers are from SCM or other automation tasks

40 What does a Continuous Integration server produce?

41 What does a Continuous Integration server produce? CRISP builds

42 What does a Continuous Integration server produce? CRISP builds Test results to monitor quality from

43 What does a Continuous Integration server produce? CRISP builds Test results to monitor quality from The artifacts generated during the run

44 What does a Continuous Integration server produce? CRISP builds Test results to monitor quality from The artifacts generated during the run Information radiation of the results

45 What does a Continuous Integration server produce? CRISP builds Test results to monitor quality from The artifacts generated during the run Information radiation of the results Safety net to allow us to know that we are ready to ship

46 Wait a minute Some of this seems real hard!

47 Wait a minute Some of this seems real hard! There is no silver bullet product

48 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything

49 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies

50 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies Treat databases like code and match schemas to code versions

51 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies Treat databases like code and match schemas to code versions User interfaces will require frameworks such as Selenium

52 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies Treat databases like code and match schemas to code versions User interfaces will require frameworks such as Selenium CI server based on build agents makes sense

53 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies Treat databases like code and match schemas to code versions User interfaces will require frameworks such as Selenium CI server based on build agents makes sense Proper set of test machines is needed for optimal results

54 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies Treat databases like code and match schemas to code versions User interfaces will require frameworks such as Selenium CI server based on build agents makes sense Proper set of test machines is needed for optimal results Preference is for builds triggered on repository commits

55 Wait a minute Some of this seems real hard! There is no silver bullet product But you can automate just about anything Use good OO practices, such as IoC, for breaking dependencies Treat databases like code and match schemas to code versions User interfaces will require frameworks such as Selenium CI server based on build agents makes sense Proper set of test machines is needed for optimal results Preference is for builds triggered on repository commits Schedule NFR and other long running tests for off-hours

56 The road to Continuous Integration takes us way past testing!

57 The road to Continuous Integration takes us way past testing! Metrics are another factor to indicate quality

58 The road to Continuous Integration takes us way past testing! Metrics are another factor to indicate quality Deployment packaging and testing of the packaging

59 The road to Continuous Integration takes us way past testing! Metrics are another factor to indicate quality Deployment packaging and testing of the packaging Deployments can be tested as well

60 The road to Continuous Integration takes us way past testing! Metrics are another factor to indicate quality Deployment packaging and testing of the packaging Deployments can be tested as well Monitoring of deployed systems may be useful

61 Poor quality? I m not going to take it anymore!

62 Poor quality? I m not going to take it anymore! This is really just a modest proposal that makes sense

63 Poor quality? I m not going to take it anymore! This is really just a modest proposal that makes sense The truth is that quality comes from technical excellence

64 Poor quality? I m not going to take it anymore! This is really just a modest proposal that makes sense The truth is that quality comes from technical excellence Blaming QA and DevOps for poor quality is not fair

65 Poor quality? I m not going to take it anymore! This is really just a modest proposal that makes sense The truth is that quality comes from technical excellence Blaming QA and DevOps for poor quality is not fair That makes as much sense as shooting the messenger on bad news

66 Poor quality? I m not going to take it anymore! This is really just a modest proposal that makes sense The truth is that quality comes from technical excellence Blaming QA and DevOps for poor quality is not fair That makes as much sense as shooting the messenger on bad news Fixing problems late in the cycle is expensive on many fronts

67 Poor quality? I m not going to take it anymore! This is really just a modest proposal that makes sense The truth is that quality comes from technical excellence Blaming QA and DevOps for poor quality is not fair That makes as much sense as shooting the messenger on bad news Fixing problems late in the cycle is expensive on many fronts Take control of the situation and everyone benefits!

68 Fin

69 Continuous Integration Optimizing Your Release Management Process