Tweet
Tweet

Slide 1

Slide 1 text

Identifying Integration Problems in a Complex Solution Study case DevOpsDays Cuba October 2016

Slide 2

Slide 2 text

Who Am I ? Duviel Rodríguez Rodríguez Graduate in Computer Science at UCLV Ops Team at @DuvielRodriguez www.linkedin.com/in/duviel-rodriguez

Slide 3

Slide 3 text

The Problem Continuous delivery for a distributed legacy Solution • Components developed by different teams • Different release’s evolution

Slide 4

Slide 4 text

Components involved

Slide 5

Slide 5 text

Components • Independents components with diferent complex levels • Are parts of Solution, not dependencies (Gemfile, POM, …)

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

Artifacts

Slide 9

Slide 9 text

Solution: Version control

Slide 10

Slide 10 text

Gitlab-CI Pipeline Master (Version file) A B C

Slide 11

Slide 11 text

Gitlab-CI Pipeline STAGING Master (Version file) A B C Releases (Tag) A B C Solution v1.1.0

Slide 12

Slide 12 text

Benefits • Integration bugs are detected early • Avoids last-minute chaos at release dates

Slide 13

Slide 13 text

Benefits • Constant availability of a "current" build for testing, demo, or release purposes

Slide 14

Slide 14 text

Devops: Why Should You Care?

Slide 15

Slide 15 text

Thanks! [email protected] @DuvielRodriguez www.linkedin.com/in/duviel-rodriguez