Downloaded 11 times
More Related Content
Similar to Usg Web Tech Day 2016 - Continuous Integration, Deployment, and Delivery
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and Delivery
- 1. CI, CD, CD STEPHENGARRETT - GEORGIA TECH
- 3.
- 4. DEPLOYMENT TYPE PUBLISH FROMIDE https://host4asp.net/visual-studio-publish-application accu web hosting: https://goo.gl/Lv0wO9
- 5. DEPLOYMENT TYPE PUBLISH FROMIDE https://host4asp.net/visual-studio-publish-application accu web hosting: https://goo.gl/Lv0wO9
- 6. DEPLOYMENT TYPE PUBLISH FROMDESIGNER https://helpx.adobe.com/dreamweaver
- 7. DEPLOYMENT TYPE FILE SYSTEMCOPY howtogeek.com - http://goo.gl/L074EZ
- 8. NOT DEPLOYMENT EDIT CODEON PRODUCTION bitnami - https://goo.gl/9TZ0KP
- 9. NOT DEPLOYMENT EDIT CODEON PRODUCTION http://transithistory.org/ccreynolds/page.php-wordpress-code-i16.jpg
- 10.
- 11. ALL IT TAKESIS 1 MISSED STEP
- 12. STRESSFUL SO STRESSFUL netdoctor.co.uk -http://goo.gl/6yIDiy
- 13.
- 14. RITUAL Navajo Fire Danceby William R Leigh
- 15.
- 16. STRESSFUL NO LUNCH clipartpanda.com- http://goo.gl/rqp006
- 17. HOW MANY PROJECTS DOYOU HAVE?
- 18. WE CAN FIXTHIS!
- 19.
- 20.
- 21. FEELINGS TO AVOID LET’SGO FROM THIS burkewilliamsspa - http://goo.gl/tzLixX Big Bang Theory
- 22. FEELINGS TO AVOID LET’SGO FROM THIS burkewilliamsspa - http://goo.gl/tzLixX Big Bang Theory
- 23.
- 24.
- 25. WITH COMPUTERS OUR PROCESSESBECOME… ▸ Rapid ▸ Reliable ▸ Repeatable
- 26. ADVANTAGES ▸ Improved softwareor product quality ▸ Higher confidence ▸ Better quality of life
- 27.
- 28.
- 29.
- 30.
- 31.
- 32. SO HOW DOWE GET THERE?
- 33.
- 34. I SEE CIAS PRIMARILY GIVING BIRTH TO A RELEASE CANDIDATE AT EACH COMMIT. THE JOB OF THE CI SYSTEM AND DEPLOYMENT PROCESS IS TO DISPROVE THE PRODUCTION-READINESS OF A RELEASE CANDIDATE. THIS MODEL RELIES ON THE NEED TO HAVE SOME MAINLINE THAT REPRESENTS THE CURRENT SHARED, MOST UP TO DATE PICTURE OF COMPLETE. Dave Farley CONTINUOUS INTEGRATION
- 35. CONTINUOUS INTEGRATION MARTIN FOWLER'SBULLET POINTS:
- 36. CONTINUOUS INTEGRATION MARTIN FOWLER'SBULLET POINTS:
- 37. CONTINUOUS INTEGRATION MARTIN FOWLER'SBULLET POINTS:
- 38. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 39. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 40. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine ▸Fix Broken Builds Immediately CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 41. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine ▸Fix Broken Builds Immediately ▸Keep the Build Fast CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 42. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine ▸Fix Broken Builds Immediately ▸Keep the Build Fast ▸Everyone can see what's happening CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 43. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine ▸Fix Broken Builds Immediately ▸Keep the Build Fast ▸Everyone can see what's happening CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 44. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine ▸Fix Broken Builds Immediately ▸Keep the Build Fast ▸Everyone can see what's happening CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 45. ▸Maintain a SingleSource Repository ▸Automate the Build ▸Make Your Build Self-Testing ▸Everyone Commits To the Mainline Every Day ▸Every Commit Should Build the Mainline on an Integration Machine ▸Fix Broken Builds Immediately ▸Keep the Build Fast ▸Everyone can see what's happening CONTINUOUS INTEGRATION MARTIN FOWLER'S BULLET POINTS:
- 46.
- 47. CONTINUOUS INTEGRATION CI TOOLS ▸TeamCity ▸ Jenkins ▸ TravisCI ▸ Bamboo ▸ Visual Studio Team Services ▸ CircleCI ▸ Codeship ▸ BuildMaster
- 48.
- 49.
- 50.
- 51. CONTINUOUS DELIVERY CHANGE INMINDSET @thisisnkp https://twitter.com/lukegb/status/539744763071979520
- 52. CONTINUOUS DELIVERY CHANGE INMINDSET /u/CodeTheInternet https://redd.it/2xxstj
- 53. THE KEY TESTIS THAT A BUSINESS SPONSOR COULD REQUEST THAT THE CURRENT DEVELOPMENT VERSION OF THE SOFTWARE CAN BE DEPLOYED INTO PRODUCTION AT A MOMENT'S NOTICE - AND NOBODY WOULD BAT AN EYELID, LET ALONE PANIC. Martin Fowler CONTINUOUS DELIVERY
- 54.
- 55. CONTINUOUS DEPLOYMENT -CONTINUOUS DELIVERY TOOLS ▸ Octopus Deploy ▸ Chef ▸ Ansible ▸ Go ▸ Codeship ▸ ElectricFlow ▸ VSTS
- 56.
- 57. QUESTIONS? THANK YOU! Stephen Garrett SeniorApp Services Manager Campus Services - Information Technology Group Georgia Institute of Technology stephen.garrett@itg.gatech.edu