The challenge facing developers today is to reduce the time between writing code and getting it into production, all while maintaining quality. What's needed is a workflow built upon highly integrated and automated tools so that developers can focus on building new features. This session demonstrates plugging together an end-to-end release workflow, including code review, acceptance testing, branch deployments, and chat ops, all using GitHub and Travis CI.

1. © 2014 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in partwithout the express consent of Amazon.com, Inc.
November 13, 2014 | Las Vegas
Automating Your Software Delivery Pipeline
Corey Donohoe, GitHub
DEV308

2. Introduction

3. I’m @atmos

5. Release Process

6. Change Control Board

7. Ops and Devs

8. Deploy on Sunday

9. Find a better way

10. Automation

11. Org wasn’t ready

12. Fast forward to 2014

13. Different Methods

14. Not All In

15. Experiences to Products
•Scripts
•Testing
•Branch Deployments
•Chat Deployments
•AutoDeployment

16. Buzz Words

17. Delivering Code

18. App Repository

19. A Revision

20. An Environment

21. Continuous Integration

22. Lots of Options

23. Great First Step

24. Continuous Delivery

25. Has Gatekeepers

26. Less Risky

27. Continuous Deployment

28. More Risky

29. GitHub’s Approach

30. What’s the difference again?

31. Deployment Basics

32. Deploy Anytime

33. Reliable Deployment

34. Less Ops Reliance

35. Understanding

36. Consistent Process

37. Empowering Devs

38. Faster to Market

39. Automating

40. Scripting Deploys

41. Deployment Service

42. hubot

43. Chat Deployments

44. Deploying from Chat

45. Deployments API

46. Deployments API State Diagram

47. hubot-deploy

48. Deploying from Chat

49. Links right your deployment dashboard

50. Example hubot-deploy config file
{
"camo": {
"provider": "aws_opsworks",
"repository": "legions/camo",
"environments": ["production", "staging"],
"github_api": "https://enterprise.me.org/api/v3",
"github_token": "<redacted>",
"opsworks": {
"production": {
"app_id": "f59a45e4-59b0-11e4-aa15-123b93f75cba",
"stack_id": "f59a4832-59b0-11e4-aa15-123b93f75cba"
},
"staging": {
"app_id": "f59a4832-59b0-11e4-aa15-123b93f75cba",
"stack_id": "f59a4be8-59b0-11e4-aa15-123b93f75cba"
}
}
}
}

51. Code Review

52. GitHub Flow

53. Push to a Branch

54. Open Pull Request

55. Opening a Pull Request

56. Coworker Signs Off

57. Deploying from Chat

58. Pull Request Merged

59. Deploying from Chat

60. ‘master’ goes out

61. Continuous Integration

62. Settles these kinds of arguments

63. Piece of mind

64. GitHub Status API

65. How the status API works

66. Multiple Services

67. Status Contexts

68. GH Flow Enhanced

69. Pull Request with CI Output

70. Easily bounce to the right build in Travis

71. Iterating on Change

72. Branch Deploys

73. Deploying a branch to verify it

74. Reflected in the pull request

75. Rollback Strategy?

76. Performance Problems?

77. Elevated
Error Rates

78. Revert a
Pull Request?

79. Enable Experiments

80. Removing complex caching

81. Branch Deploy Flow

82. Experiment in environments, document in pull requests

83. Merge and Deploy

84. GitHub Auto-Deploy

85. It’s a service inside of github

86. Uses the Status API

87. Create Deployments

88. Specify Environment

89. Provides Continuous Delivery

90. Provides Continuous Deployment

91. auto-deploy in action

92. auto-deploy in action

93. Other Approaches

94. Environment Locks

95. Service Validation

96. Service Validation Example
hooks:
ApplicationStart:
-location: scripts/verify_functional_tests.sh
timeout: 600
ValidateService:
-location: scripts/verify_new_user_signups.sh
timeout: 600

97. Does new code work

98. Elevated Error Rates

99. Exciting Stuff

100. Continuous Branch Deployments

101. Discussing Performance

102. Schema Changes

103. Lots of Possibilities

104. This model has worked well for me

105. Helping Deliver

106. Thank You 

107. Please give us your feedback on this session.
Complete session evaluations and earn re:Invent swag.
http://bit.ly/awsevals

108. That’s all folks.