Build&Pipelines - Callista Enterprisecallistaenterprise.se/assets/presentationer/cadec-2013-build... · – Other"Job" • Plugin"Support Test Deploy" ... • DSL konﬁguraon ""

© 2013 Callista Enterprise | www.callistaenterprise.se Build Pipelines © 2013 Callista Enterprise | www.callistaenterprise.se

Build Pipelines

Quality through Repeatability

Anders Asplund| [email protected] Björn Beskow| [email protected]

1 1


Quality through Repeatability: Enterprise Builds

2


Build Automation

•  SoGware Builds should be CRISP: – Complete – Repeatable – InformaLve – Schedulable – Portable

3


Levels of build automation

Commanded Builds

Scheduled Builds

Triggered Builds

4


Continuous Integration Servers Provides Scheduled and Triggered Builds on top of a Commanded build mechanism

5


Challenge: Modularity

6


Upstream/Downstream Projects

7


Challenge: Externals (servers, environments, …)

8


Challenge: Autonomy & Cohesion

9


Challenge: Autonomy & Cohesion

10


Build Pipelines

11


Build Pipelines

•  Wikipedia: “a set of validaLons through which a piece of soGware must pass on its way to release”

12


Traditional CI scope

13


Build Pipelines scope

14


One-‐click Deploys

15


•  Open Source CI server •  Formerly known as Hudson •  Monitors execuLon of repeated jobs

–  Manually –  Scheduled –  On code change –  Other Job

•  Plugin Support

Test

Deploy

Release

16


Plugin support for Build Pipelines

•  Build Pipeline

•  Build Flow

17


Build Pipeline

18


Build Pipeline Support Plugins Parameterized Trigger Plugin

19


Build Pipeline Support Plugins CondiLonal BuildStep Plugin

20


Build Pipeline Support Plugins Join plugin

21


Build Pipeline Support Plugins More Plugins

•  Clone Workspace SCM Plugin •  Copy ArLfact Plugin

22


Other Plugins JobConfigHistory

23


Plugin support for Build Pipelines

•  Build Pipeline

•  Build Flow

24


Build Flow

25

build(“Test”)!build(“Release”)!

b = build(“Release”)!build(”Deploy to Test”, param: b.build.number)!

build("Test")!build("Release")!parallel (! { build("Deploy to Test") },! { build("Generate docs") }!)!build("Deploy to Staging")!build("Deploy to Production")!


Build Flow

26


Build Pipeline

•  Löst kopplade byggsteg – återanvändbarhet

•  DSL-‐konfiguraLon •  Saknar visuell

presentaLon •  Saknar stöd för

manuella steg

Build Flow

-‐

+ •  Bra visuell överblick •  Läd ad komma igång

•  Hårt kopplade byggsteg -‐ Redundans

27


Case Study: www.papyrus.com

28


TODO: screen shot of Jenkins

29


Effects:

•  Total effort: 1 man week •  Manual effort in packaging and deploying a release: 1 man day -‐> 5 minutes

•  Manual configuraLon and verificaLon points (areas for potenLal errors) +20 -‐> 1

•  ROI: Almost instant

30


Questions?

31

Documents

Build&Pipelines - Callista Enterprisecallistaenterprise.se/assets/presentationer/cadec-2013-build... · – Other"Job" • Plugin"Support Test Deploy" ... • DSL konﬁguraon ""