GitOps, Jenkins & Jenkins X Tracy Miranda, Director of Open - - PowerPoint PPT Presentation

▶

Feb 06, 2024 122 likes •438 views

GitOps, Jenkins & Jenkins X Tracy Miranda, Director of Open Source Community | CloudBees tmiranda@cloudbees.com | @tracymiranda @tracymiranda What is DevOps? @tracymiranda DevOps is the new legacy @tracymiranda Cloud Native

SLIDE 1

GitOps, Jenkins & Jenkins X

Tracy Miranda, Director of Open Source Community | CloudBees tmiranda@cloudbees.com | @tracymiranda

@tracymiranda

SLIDE 2

What is DevOps?

@tracymiranda

SLIDE 3

DevOps is the new legacy

@tracymiranda

SLIDE 4

Cloud Native Technologies

On demand self-service
Broad network access
Resource pooling
Rapid elasticity
Measured service

SLIDE 5

DORA State

f DevOps

Reports

@tracymiranda

SLIDE 6

The Science of Lean Software and DevOps

@tracymiranda

SLIDE 7

Building and scaling high performance technology organisations

@tracymiranda

Throughput

Frequent deployments Low lead time from commit to deploy

Stability

Fast mean time to recovery (MTTR) Low change failure rate

SLIDE 8

GitOps

@tracymiranda

Operation by pull request Git as the single place where we operate All changes are

bservable

SLIDE 9

https://www.weave.works/blog/what-is-gitops-really

@tracymiranda

SLIDE 10

@tracymiranda

SLIDE 11

Jenkins

@tracymiranda

SLIDE 12

JENKINS PIPELINE JENKINS EVERGREEN CONFIGURATION AS CODE CLOUD NATIVE JENKINS JENKINS X

SLIDE 13

CONFIGURATION AS CODE

SLIDE 14

WHAT IF …

CONFIGURATION AS CODE

You can apply a sane change control practice to Jenkins configuration? Jenkins stops being a snowflake? You can safely roll back a failed upgrade? You could cookie cutter lots of identical Jenkins instances?

SLIDE 15

jenkins: securityRealm: ldap: configurations:

server: ldap.acme.com

rootDN: dc=acme,dc=fr managerPasswordSecret: ${LDAP_PASSWORD} cache: size: 100 ttl: 10 userIdStrategy: CaseSensitive groupIdStrategy: CaseSensitive

SLIDE 16

1 This is

happening

Launch Docker container with said config file

SLIDE 17

Getting Started with config-as-code

https://www.praqma.com/s

tories/start-jenkins-config- as-code/

SLIDE 18

@tracymiranda

SLIDE 19

@tracymiranda

SLIDE 20

JENKINS X

SLIDE 21

COMMON PLATFORM IN ALL CLOUDS AWS, Microsoft Azure, Google Cloud Platform, OpenShift, Cloud Foundry FUNCTIONALITY Cluster scheduler, service discovery, load balancer EXTENSIBILITY

NEW Cloud Operating System

SLIDE 22

You can have fun

tinkering

SLIDE 23

Or you can just get

productive

SLIDE 24

Jenkins X Vision

Figure out the best practice of how to CD cloud native apps

Not just build and test, but review, promote, changelog, collaborate, etc.

Integrate best of breed software in this ecosystem to achieve it Democratize it by building a pleasant CLI that represents high-level steps Be opinionated on how to do things Kubernetes is a means to the end

SLIDE 25

@tracymiranda

SLIDE 26

@tracymiranda

SLIDE 27

@tracymiranda

SLIDE 28

@tracymiranda

SLIDE 29

Best Practice We Preach

Use cloud to develop, keep your laptop for what it needs to do Promote apps through multiple environments GitOps: deployment should be recorded and tracked in Git Develop/collaborate changes in PR, review/test before merge Keep master always releasable Inform other people about where changes are Deploy often and in small increments

SLIDE 30

Wrap-up

SLIDE 31

Conclusions

Configuration as code is a best practice to follow.
If you are using cloud native technologies, GitOps has essential

techniques and practices to help you go faster without costing you stability.

There are some problems your tools won’t fix, for everything else

there’s Jenkins X.

@tracymiranda