This document discusses the importance of treating infrastructure and pipelines as code for software development teams. It notes that while teams often focus on the application code being developed, they should also focus on how the code is built, released, and deployed. Describing these processes as code enables teams to test and assure the quality of their delivery pipelines. The document then outlines examples where infrastructure and pipelines are treated as code, such as with Jenkins Pipelines, configuration as code, and tools like Travis, Gitlab, and others. It invites readers to review examples of building pipelines as code using Jenkins and other related tools.

1. @automatingguy
Your delivery pipelines as code
Jenkins Pipelines in action!

2. @automatingguy
Continuous Delivery

3. @automatingguy
Continuous Delivery
?

4. @automatingguy
Continuous Delivery
?
?

5. @automatingguy
Continuous Delivery
?
? ?

6. @automatingguy
Are we focusing on
all important
elements?

7. @automatingguy
In software development we often focus on
WHAT we build…

8. @automatingguy
In software development we often focus on
WHAT we build…
... why do we not also focus on HOW we
build it?

9. @automatingguy@automatingguy
Why is it
important for us,
QA folks?

10. @automatingguy
By understanding HOW you build, release &
deploy your application,
you can be more sure in assuring quality

11. @automatingguy
…and you may find yet another area
that needs testing :)

12. @automatingguy
We’ve started doing
something about it!

13. @automatingguy
We’ve started doing
something about it!
DevOps

14. @automatingguy
Code & as-code

15. @automatingguy

16. @automatingguy
Code
Code everywhere

17. @automatingguy
Code & as-code
Application code

18. @automatingguy
Code & as-code
Application code
Infrastructure-as-code

19. @automatingguy
Code & as-code
Application code
Infrastructure-as-code
Configuration-as-code

20. @automatingguy
Code & as-code
Application code
Infrastructure-as-code
Configuration-as-code
PIPELINE-AS-CODE!

21. @automatingguy
Pipeline-as-code
Concept mentioned in Thoughtworks’ Tech
Radar

22. @automatingguy
Pipeline-as-code
Supported by:
Travis, Gitlab, Bitbucket, GoCD,
LambdaCD, Drone, Concourse, Bamboo

23. @automatingguy
Pipeline-as-code

24. @automatingguy

25. @automatingguy
What are we going to build?
Jenkins Pipeline (+ Shared library)
Jenkins Configuration as Code
Zalenium
Bobcat

26. @automatingguy
Action time already!

27. @automatingguy
It can get more complicated

30. @automatingguy
Want more?
The whole code with runnable example:
https://github.com/mkrzyzanowski/kraqa-37
My posts about Jenkins Pipelines:
https://automatingguy.com/tag/jenkins/
Official docs:
https://github.com/jenkinsci/docker#official-jenkins-docker-image
https://jenkins.io/doc/book/pipeline/
https://jenkins.io/doc/book/pipeline/shared-libraries/
https://github.com/jenkinsci/configuration-as-code-plugin
https://github.com/zalando/zalenium#getting-started

31. @automatingguy
Thank you!
MICHAŁ KRZYŻANOWSKI
TWITTER: @automatingguy
BLOG: https://automatingguy.com
DEBATQA: https://fb.me/DebatQA/