Pipelining quality best practices, lessons learned and tools for - - PowerPoint PPT Presentation

▶
pipelining quality
SMART_READER_LITE
LIVE PREVIEW

Pipelining quality best practices, lessons learned and tools for - - PowerPoint PPT Presentation

Jun 05, 2023 131 likes •297 views

Pipelining quality best practices, lessons learned and tools for continuous delivery processes 25. Oktober 2017, Markus Tiede Basler Versicherungen AG Wir machen Sie sicherer. Wir machen Sie sicherer. @MarkusTiede Wir machen Sie sicherer.

slide-1
SLIDE 1

Wir machen Sie sicherer.

Pipelining quality

best practices, lessons learned and tools for continuous delivery processes

  • 25. Oktober 2017, Markus Tiede – Basler Versicherungen AG

Wir machen Sie sicherer.

slide-2
SLIDE 2

Wir machen Sie sicherer.

@MarkusTiede

slide-3
SLIDE 3

www.baloise.ch 3 25.10.17

Bird's eye view

http://www.datacenterjournal.com/wp-content/uploads/2016/11/devops111116.png

slide-4
SLIDE 4

www.baloise.ch

01 Galileo

„ OOTB approach

25.10.17 4

n large-scale insurance enterprise project n 4 products

CM

n 8 Scrum teams for "customization"

n ± 75 people n POs, SMs, Architects, Developer, Tester, Business Analysts n 1-2 team(s) per product n cross-functional team(s): integration, release

Portal

slide-5
SLIDE 5

www.baloise.ch

02 Overall process

„ "classic" SCRUM

25.10.17 5

n two week sprints (sync) n but: harmonized releases

n decoupled from sprint(s)

n everything digital

n knowledge / documentation base

n deeply integrated / coupled

n application lifecycle

n CRs, User Stories, Bugs, …

n SourceCodeManagement n Continuous Integration

slide-6
SLIDE 6

www.baloise.ch

03 A journey to production

„ knowledge and automation is key: Confluence Dashboard

25.10.17 6

slide-7
SLIDE 7

www.baloise.ch

04 Jenkins pipelines (scripted and declarative)

„ orchestration of environment(s) – CI as code (Job DSL)

25.10.17 7

LB / SSO

PC

  • 1
  • 2

coo BC

  • 1
  • 2

coo CM

  • 1
  • 2

coo Portal

  • 1
  • 2
  • 3
slide-8
SLIDE 8

www.baloise.ch

05 Agile testing pyramid (per coordinate)

„goal: fail fast / fail early

25.10.17 8

slide-9
SLIDE 9

www.baloise.ch

06 Coordinates (stack : env)

„allow (massive) parallism + bubbling

25.10.17 9

Project+0

TEST INT ACC PROD

Project+1

TEST INT ACC

Project+2

TEST INT ACC

Project+3

TEST INT

LB / SSO

PC

  • 1
  • 2

coo BC

  • 1
  • 2

coo CM

  • 1
  • 2

coo Portal

  • 1
  • 2
  • 3

12 x 12 = 144 individual nodes

slide-10
SLIDE 10

www.baloise.ch

07 Releases

„different flavours

25.10.17 10

n MAJ.MIN.MIC.FIX

n HOTFIX (e.g. 4.0.1.2)

n 8 – 12h (full regression)

n MICRO

n < 1 week

n MINOR

n < 1 month

n MAJOR

n < 1 year

Project+0

TEST INT ACC PROD

Project+1

TEST INT ACC

Project+2

TEST INT ACC

Project+3

TEST INT

slide-11
SLIDE 11

www.baloise.ch

08 Change and data flow

„multi-master branches and tags per repo

25.10.17 11

2.3.2.0.rc1 2.4.0.0.rc1 2.4.0.0.rc2

slide-12
SLIDE 12

www.baloise.ch

09 Change and data flow

„"Golden master / copy"-approach

25.10.17 12

Project+3

TEST INT

Project+2

TEST INT ACC

Project+1

TEST INT ACC

Project+0

TEST INT ACC PROD

slide-13
SLIDE 13

www.baloise.ch

10 Tools

„inspection, analysis, monitoring

25.10.17 13

n low level – log mining n high level – "pure path" analysis n custom level – knowledge graph

slide-14
SLIDE 14

www.baloise.ch

11 2do

„aka – pain points

25.10.17 14

n Environment as code

n Puppet, Anisble & Co

n Code Review per Feature Branch n automated and manual n (Test) Data Management

n all or nothing – x TB of data n Highly interconnected data

n Legacy systems / processes (Batches)

slide-15
SLIDE 15

www.baloise.ch

12 Summary

„ take away

25.10.17 15

n 100% digital – linked resources; knowledge base n simultanuous release (train) vs. agile shippable artifact n Multi-(Stack)-(Jenkins)-Pipelines n Agile Test-Pyramid n SCM „tag“ driven deployments n Data Management: Golden Data / Master approach n Build your own knowledge graph: neo4j

slide-16
SLIDE 16

Making you safer.

https://github.com/baloise