DevOpsDays Cuba 2016: Ignite - Identifying integration problems in a complex solution

Author: Duviel Rodríguez Rodríguez
Summary:
Identifying integration problems in a complex Solution, highlighting the importance of continuous integration for avoid unexpected problems close to deadlines dates and strengthening the DevOps’s culture in communication, collaboration and integration between software developers and IT operation professionals.

Transcript

1. Identifying Integration Problems in a Complex Solution Study case DevOpsDays Cuba October 2016
2. Who Am I ? Duviel Rodríguez Rodríguez Graduate in Computer Science at UCLV Ops Team at @DuvielRodriguez www.linkedin.com/in/duviel-rodriguez
3. The Problem Continuous delivery for a distributed legacy Solution • Components developed by different teams • Different release’s evolution
4. Components involved
5. Components • Independents components with diferent complex levels • Are parts of Solution, not dependencies (Gemfile, POM, …)
6. Release’s evolution ETL-1.3.0 SparkTasks- 0.4.5 AppWebRails- 1.3.4 ETL-1.4.0 SparkTasks- 0.4.6 AppWebRails- 1.3.5 ETL-1.4.1 SparkTasks- 0.4.7 AppWebRails- 2.0.0
7. Integration problems ETL-1.3.0 SparkTasks- 0.4.5 AppWebRails- 1.3.4 ETL-1.4.0 SparkTasks- 0.4.5 AppWebRails- 1.3.4 ETL-1.4.0 SparkTasks- 0.4.6 AppWebRails- 2.0.0
8. Artifacts
9. Solution: Version control
10. Gitlab-CI Pipeline Master (Version file) A B C
11. Gitlab-CI Pipeline STAGING Master (Version file) A B C Releases (Tag) A B C Solution v1.1.0
12. Benefits • Integration bugs are detected early • Avoids last-minute chaos at release dates
13. Benefits • Constant availability of a "current" build for testing, demo, or release purposes
14. Devops: Why Should You Care?
15. Thanks! duvrod@gmail.com @DuvielRodriguez www.linkedin.com/in/duviel-rodriguez