GETTING STARTED WITH CONTINUOUS DELIVERY. Lana wcgp.co

Transcription

1 GETTING STARTED WITH CONTINUOUS DELIVERY Lana wcgp.co

2 ABOUT ME Lana Kalashnyk BAAS Computer Science minor Business Administration AS in Computer Science emphasis on Networking Cisco CCNA I-IV, Red Hat JAX-RS, NetSuite, WPF, Oracle Java training Houston Java User Group, Houston.Net User Group, Texas DevOps User Group, PuppetConf On Center Software 8+ years enterprise software development for high availability platforms W Consulting Group. Consulting services in cloud platforms design to customers debt trading, auto finance and defense industries. Some of our past projects Debt Trading Defence Auto Finance Construction

3 Continuous Delivery?

4 WHY TALK ABOUT CONTINUOUS DELIVERY? Not a new concept Many not sure what it means Few actually use it

5 WHAT IS CONTINUOUS INTEGRATION? Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. (ThoughtWorks)

6 WHAT IS CONTINUOUS DELIVERY? Continuous Delivery (CD) is a software engineering approach in which teams keep producing valuable software in short cycles and ensure that the software can be reliably released at any time. Techniques such as automated testing and continuous integration (CI) allow software to be developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead. (Wikipedia)

7 WHAT IS DEVOPS? Born of the need to improve IT service delivery agility, the DevOps movement emphasizes communication, collaboration and integration between software developers and IT operations. Rather than seeing these two groups as silos who pass things along but don t really work together, DevOps recognizes the interdependence of software development and IT operations and helps an organization produce software and IT services more rapidly (New Relic)

8 CONTINUOUS DELIVERY IS NOT CONTINUOUS DEPLOYMENT Continuous Delivery doesn't mean every change is deployed to production ASAP. It means every change is proven to be deployable at any time - Puppet ( Carl Caum)

9 While continuous deployment may not be right for every company, continuous delivery is an absolute requirement of DevOps practices. Only when you continuously deliver your code can you have true confidence that your changes will be serving value to your customers within minutes of pushing the "go" button, and that you can actually push that button any time the business is ready for it. (PuppetLabs)

10 STAGES OF CONTINUOUS DELIVERY Theory: Build Module Unit Tests Platform Tests Deliver To Staging Application Acceptance Tests Deploy To Production Post Deploy Tests Fully Automated Steps

11 STAGES OF CONTINUOUS DELIVERY Practice : Write down the actual steps in your Development Process Build Commit Test Stage Deploy Code

12 AGILE & CONTINUOUS DELIVERY Continuous Integration was born in Agile roots Continuous Delivery was born out of CI, hence inherits its Agile qualities

13 REAL WORLD ISSUES Broken deployments Magical servers Exciting releases

14 WHAT IF YOU AREN T A DEVOPS PRO? Engineering approach not tools Scope wisely Be Agile

15 FAST TRACK ROAD MAP Start Small & Simple Think The biggest ROI Monitor your process! Think in abstract terms Educate your team

16 START SMALL & SIMPLE Start with small tasks Automate things you understand Don t automate the automation

17 THINK THE BIGGEST ROI Automate the most re-used components. Automate the most error-prone components. If time / budget are an issue don t automate UI testing. UI changes too frequently

18 MONITOR YOUR PROCESS! Automation has to be monitored! Feedback is the reason we automate

19 ADOPT THE PRINCIPLES NOT TOOLS Speak in CD terms not tools Containers not Docker Automated testing not Cucumber

20 EDUCATE TO BREAK DOWN THE SILOS Introduce CD into Development Agile needs cross team collaboration. Educate the team! Automated testing is a must.

21 BONUS : IMMUTABLE CONTAINERS Immutable - not changeable Don t waste time updating servers. Updating live environments is dangerous Deploy new ones Turn off the old ones when ready

22 BONUS: ONE STEP DEPLOYMENTS Quote If your setup is longer than one line, you are coding in prototype Offload custom steps into scripts

23 REVELATIONS Non DevOps Engineers should be involved in Continuous Delivery! CD lets you re-purpose the Super Stars Boring is good Frequent Releases make Developers happy

24 JOIN THE PARADE Stepping into DevOps / CD can feel like : Stepping out of an office building into a parade Explosive innovation in CD/CI/DevOps space

25 HOW TO SELECT YOUR TOOLS Thinking of Continuous Delivery as an approach rather than a particular tool implementation helps with solving a problem not adopting a hot trend.

26 Puppet JMeter SonarQube Chef Arquillian Jenkins Pyling Salt Selenium Go CD JSHint Ansible TestComplete Cloud Bees New Relic Packer Bamboo Snap Logic Monitor Docker Vagrant CA Release Automation Pager Duty LXD Jenkins Live Rebel Server Spec Rocket GO CD DerbyIT Test Kitchen DrawBridge TeamCity Maven Cucumber Spoon Bamboo Ant Chaos Monkey CodeDeploy RDS for PostGRES Rake BASH Cloud Formation RDS for MySQL Gradle CURL OPSWorks IBM Urban Code Grunt EC2 CLI TeamCity Python Code Climate Code Pipeline Electric Cloud Cucumber Sonar Code Commit Continuous Delivery Tools Continuous Integration Tools DevOps Tools and many many more

27 Configuration/DevOps Puppet SonarQube Chef Arquillian Jenkins Pyling Salt Selenium Go CD JSHint Ansible TestComplete Team City Bamboo Containers Docker Packer LXD Rocket DrawBridge Spoon Amazon AWS CodeDeploy Code Commit Cloud Formation OPSWorks CLI Code Pipeline Test Automation Bamboo Snap Logic Monitor Vagrant Cucumber DB Scripting RDS for PostGRES RDS for MySQL IBM Urban Code TeamCity Electric Cloud CI CI/CD CA Release Automation Live Rebel DeployIT Build Maven Ant Rake Gradle Grunt Pager Duty Server Spec JMeterTest Kitchen Cucumber Chaos Monkey Code Climate Sonar BASH Python CURL Testing Monitoring Infrastructure / Load Scripting

28 REFERENCES Wikipedia ThoughtWorks Docker PuppetLabs New Relic Jenkins CloudBees

29 SAMPLE IMPLEMENTATION First Let s see what we need : 1. Build Tool : Maven 2. CI Tool : Jenkins 3. Automated Testing Arquillian / Selenium / Cucumber Provisioning tool for new Servers :

30 SAMPLE IMPLEMENTATION 5. Container Tool : Docker 6. Monitoring Tool: Logic Monitor Vendors Sample Demos Puppet & Jenkins (CloudBees) GoCD and Docker

31 RAFFLE!

32 THANK YOU!! Lana Kalashnyk W Consulting Group wcgp.co Twitter