Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Devops Days, 2019 - Charlotte

152 views

Published on

Presentation on journey of Continuous Integration and Continuous Deployment at Botsplash

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Devops Days, 2019 - Charlotte

  1. 1. botsplash DevOps Day Ignite Talks – February, 2019 Ramu Pulipati ramu@botsplash.com Engage with your customers across chat platforms
  2. 2. Introduction – Who is Ramu Pulipati? • Co-founder @Botsplash • Botsplash - Omni-channel Messaging platform for Enterprises • Bootstrapped with small team of developers
  3. 3. CI/CD Journey Goals at Botsplash Agility Cost Security Maintain
  4. 4. Extended Goals No Vendor Lock In Approval Process Cross AWS environments Multiple Projects Compliance
  5. 5. CI/CD Challenges • Enterprise clients => HUGE expectations and AUDIT • Do we need it? • When we needed it • Tried hosted solutions and ran into time drain
  6. 6. Start Simple • Shell Scripts & Ansible • They work like magic with proper structure • Share across dev and prod environments
  7. 7. Shell Script Challenges • Deployment takes up to 10 mins • Manually triggered • No status dashboard • Error reporting is weak
  8. 8. Enter Circle CI • Well thought out product • Easy for developers • Centralized dashboard with automatic triggers
  9. 9. Circle CI Implementation • Quickly convert shell scripts to build config files • Ansible/SSH Deployments • We ❤️ it
  10. 10. Circle CI Challenges • IP range is dynamic • Git SSH keys distribution • Pipelines were not available
  11. 11. Moving past Circle CI • It is continually improving • But security and deployment are a big deal • Building hybrid solution with Jenkins/AWS is an option
  12. 12. Also, Our goals have matured • Focused for fintech & proptech companies • Emphasis on security: Better protect the servers/secrets • SOC-2 and ISO compliance compatibility
  13. 13. Team goals • Dev, Staging to Production pipelines • Multiple and parallel releases • Limited cost and maintenance
  14. 14. Enter AWS Code Suite CodeBuild | CodeDeploy | CodePipeline
  15. 15. AWS Code Benefits • Closed network access & security • No extra hardware/servers to manage • Works across AWS accounts (DEV/Stage/Prod)
  16. 16. AWS Code Suite Implementation • Setup staging environment • POC of Everything • Review if this is what you want to do?
  17. 17. Taking it to Production • Evaluate NEW deployment process • Run in staging environment for 2 sprints • Build multiple pipelines for different purposes
  18. 18. AWS Code Challenges • It’s a big time suck, don’t underestimate the effort • Many gotchas, things that work independently does not work • Slow to evolve and fix bugs
  19. 19. Rethinking AWS Code Suite … • We questioned our decision multiple multiple times • For everything else, there is Lambda and do it yourself • Better use Jenkins server to implement complex tasks
  20. 20. Lessons Learned • Setup integrations tests before moving to production • Adding more infrastructure will add complexity, reduce the scope • Some tools are better than others
  21. 21. Conclusion • CI/CD is time consuming • When needed, do minimal • Clearly set the goals and accomplish them incrementally

×