►
From YouTube: Moving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD - Dr. Michael Garbade
Description
Moving from Jenkins to Jenkins X: Scaling and Accelerating CI/CD - Dr. Michael Garbade, Education Ecosystem
Jenkins has served as a continuous integration (CI) tool long before the emergence of Kubernetes and distributed systems running on cloud native platforms.
Working with Jenkins as a stand-alone open source tool has proved to be extremely difficult for distributed systems engineers, as it is designed for small projects and not scalable to bigger projects.
Jenkins X has emerged as a way to both improve and automate continuous delivery pipelines to Kubernetes and cloud native environments.
In this talk, we will discuss the limitations of Jenkins, how Jenkins X addresses those limitations, how it leverages open source and commercial CI/CD tools for easier bug fixes, faster deployments, stability, consistency and improved communication.
A
A
A
Today,
for
those
of
you
who
are
not
familiar
with
jenkins
I'll
talk
a
bit
about
what
jenkins
is
the
best
use
cases
for
jenkins-
and
you
know
the
suitable
environments
for
jenkins
I'll-
also
give
you
some
historical
contests
behind
jenkins,
so
you
can
understand,
you
know
how
jenkins
came
about
and
what
it
was
used
for.
Initially,
then
I'll
move
on
to
the
challenges
posed
by
jenkins
for
engineering
teams
today.
That
means
the
challenges
that
you
know.
There
are
teams
they
face
when
they
try
to
use
junkies.
A
A
The
most
popular
cia
cd
tools
that
I
use
in
devops
today
are
travis
jenkins,
isaiah
and
circle.
Ci
jenkins
emerged
in
the
year
2011
from
oracle's
husband,
ci
too.
Oracle
is
a
strong
java
powerhouse
and
most
of
the
applications
are
written
in
java.
So
it's
no
surprise
that
jenkins
is
also
written
in
java
and
jenkins
runs
in
the
web.
Container
jenkins
is
sometimes
called
the
wordpress
of
continuous
integration
and
engineers
use
it
to
automate
their
ci
cd
pipelines.
A
Jenkins
is
open
source
and
free,
and
therefore
it
is
pretty
popular
jenkins
supports,
like
all
version
controls
and
many
build
automation
tools.
If
you
are
using
jenkins-
and
you
want
to
use
your
version
control
tool
like
gitlab,
github
or
bitbucket,
you
can
use
it
so
jenkins
does
not
tie
you
to
any
specific
version
control.
You
can
use
passion.
Control
too.
You
are
comfortable
with.
You
can
also
use
any
build
automation
tool
you
want
like
if
you
want
to
use
ms
build.
A
A
As
you
can
see
here,
this
is
the
jenkins
website
right.
So
this
is
the
website
for
jenkins,
and
you
can
see
that
it
has
a
strong
community
support
and
there
are
community
support
in
forums.
There's
a
mailing
list.
You
know
there
are
meetup
groups,
so
if
you
have
a
specific
issue,
you're
taking
care
of
issues
with
jenkins,
you
can
ask
in
those
groups.
A
Jenkins
also
has
strong
language
support
for
german,
english,
spanish
and
even
chinese.
So
if
english
is
not
your
native
language,
you
can
go
into
the
specific
groups
and
ask
any
questions.
You
have
right.
Jenkins
is
very
popular
on
github,
as
you
see
on
the
github
page,
it
has
over
6
000
folks
and
over
16
000
likes.
So
if
you
want
to
explore
jenkins
like
if
you
wanna
just
check
out
jenkins
what
it
is
and
what
it's
used
for,
you
can
kind
of,
like
you
know,
check
it
out
on
one
of
these
pages.
A
So
here
we
have
a
visual
representation
of
a
typica
jenkins
core
pipeline
and
that
is
used
for
building
testing
and
deployment
of
code.
So,
as
you
can
see
here,
it's
like
a
standardized
process
where
you
know
we
have
like
three
different
development
environments
that
projects
normally
have.
So
we
have
the
depth
environment,
the
development
environment.
We
have
the
staging
environment,
we
have
the
production
around
it.
So
for
each
of
these
environments,
what
we
do
is
that
we
set
up
jenkins
right
and
we
set
up
jenkins.
A
You
know
in
the
same
way,
because
we
want
to
replicate
the
same
environment,
the
same
processes
just
to
have
the
same
testing
environment
right.
We
don't
want
to
have
like
different
system
and
environment
in
each
environment.
You
want
to
have
the
same
unique.
You
know,
you
know
ci
cd
environment,
so
that
like
when
we
deployed
to
production,
we
don't
get
any
surprises.
So
this
is
the
typica.
You
know
use
case
for
jenkins,
as
you
see
here
in
this
image
right-
and
this
is
how
jenkins
normally
is
used.
A
A
A
So
people
at
that
time
were
deploying
the
applications
mainly
on
the
defeated
servers
right,
so
they
will
just
buy
the
cables,
have
a
server
hosting
company,
and
then
they
will
deploy
the
application
right,
so
virtual
private
service
and
cloud
service
well
in
common
at
the
time,
but
today
the
dev
ops,
where
you
know
the
hosting
of
applications
it
looks
very
different
right
jenkins,
is
not
suitable
for
big
teams.
It's
also
not
suitable,
for
you
know
like
any
large-scale
software
development.
A
It
lasts
tools
that
team
members
can
use
for
collaborating
on
testing.
It
also
lacks
analytics.
Recording
jenkins
has
customization
limitations
compared
to
other
ci
tools
and
cv
tools,
so
these
are
some
of
the
shortcomings
of
jenkins
right
and
one
of
the
main
important
things
like
when
jenkins
was
developing
years
ago.
Things
that
we
take
for
granted
in
the
software
world
like
cloud
services
like
aws
asia,
google
cloud
it
didn't
exist
at
that
time
and
you
know
containerized
deployments,
you
know
with
docker,
with
kubernetes,
docker
images,
etc.
A
A
Normally,
if
engineers
want
to
manage
multiple
containers
right,
that
means,
if
you
want
to
manage
like
multiple
docker,
you
know
images,
you
will
need
to
know
kubernetes
right
and
you
need
to
know
how
to
learn,
how
to
run
kubernetes
commands
and
with
jenkins.
You
do
not
need
to
know
the
specific
details
about
kubernetes,
but
you
can
still
use
kubernetes.
You
know
features
I
see
if
you
know
kubernetes,
because
jenkins
provides
a
gui
interface.
A
That
kind
of
like
goes
slower,
slow.
It
can
get
there
as
well,
but
it's
going
to
take
you
a
long
time.
It's
going
to
waste
your
time.
It's
going
to
waste
efficiency
and
you're
going
to
you
know,
be
frustrated
with
your
testing
and
deployment
process
right
so
with
jenkins.
You
can
automate
pull
requests
and
preview.
The
development
environment
right
we're.
A
You
can
automate
a
lot
of
the
commands
that
before
you
need
to
kind
of,
like
you
know,
do
manually
in
jenkins
now
everything
is
kind
of
like
pre-set
up
and
you
just
kind
of
like
do
two
or
three
things
and
you're
ready
to
go.
So
if
you
have
to
run
to
three
steps
in
jenkins
to
do
something
now,
those
three
steps,
you
know
they
are
cut
into
just
one
single
step
right.
So
let's
look
at
the
jenkins
x
website.
A
So
let's
go
back
and
look
at
the
game's
next
website.
So
if
you
want
to
download
jenkins
x,
if
you
want
to
kind
of
play
with
jenkins
x,
you
can
see
it
here.
This
is
the
jenkins
x
website
and,
as
you
can
see
here
I
mean
it
looks
fresh,
but
they
have
a
lot
of
documentation
right.
They
have
a
lot
of
explanation.
They
have
explained
you
know,
preview
environments,
how
you
can
do
automated
tool
requests
and
they
have
like
a
community.
A
A
So
now,
let's
look
at
you
know,
jenkins
x.
You
know
the
components
of
jenkins,
you
know
the
architecture
for
jenkins
x
and
how
we
can
set
up
jenkins
x
and
how
we
can
install
it
and
play
with
it.
So
we're
just
gonna
dig
a
bit
deeper
into
it,
like
you
know
how
you
can
do
this
right,
so,
let's
go
into
it.
Let
me
just
pull
on
my
image
that
will
show
us
how
jenkins
actually
architecture
looks
like
right.
A
So
if
you
want
to
kind
of
like
use,
gen
connection
just
download
the
binaries
and
the
binaries
comes
with
something
called
the
js
script
right
and
that
js
script
kind
of,
like
simplifies
the
whole
work
for
us,
because
it's
going
to
simplify
the
jenkins
setup,
it's
going
to
simplify
the
creation
of
kubernetes
clusters
right,
so
the
jsp
will
do
the
whole
setup
for
you,
as
mentioned
it
will
create
new
kubernetes
cluster
with
jenkins,
already
jenkins
x,
already
included
right.
So
it's
already
installed.
A
You
don't
have
to
do
anything,
so
they
really
didn't
bring
you
in
a
smart
way
and
just
to
save
the
lock
this
time
right
so
taking
this
x
works
with
like
with
every
version
control
tool.
You
want
to
use
just
like
jenkins.
So
if
you
are
using
gitlab,
if
you're
using
github,
either
vs
code
connect,
you
can
still
you
know,
use
it
to
change
my
sense
right.
Github
is,
I
mean
the
dominant
and
most
established
version
control
tool.
A
So
github
is
what
most
people
use
right,
but
it's
of
course
elevation
control
too,
as
well
right.
You
can
interact
with
jenkins
x
right
using
a
gui
or
you
can
interact
with
future
very
comfortable
like
normal
command
line
tools
right,
you
can
kind
of
play,
write
your
commands
and
send
you
know,
so
you
don't
have
to
kind
of
like
you
know,
just
use
command
line.
You
can
just
use
three
if
you
are
not
interested
in
understanding
the
command
line
tools
right.
A
Even
if
you
do
not
know
how
people
networks,
you
can
still
run
kubernetes
commands
right
and
deploy
containers.
So
this
is
one
of
the
beauty
and
one
of
the
simplification
of
kubernetes.
That
jenkins
provides
right,
so
the
commands
are
sent
to
the
js
api
and
the
js
api
sends
the
command
to
the
kubernetes
api
server
yeah.
So
the
kubernetes
api
server
like
this
in
the
middle
of
everything
right
and
it
does
the
magic
right.
A
A
We
have
our
three
development
environments
and
the
build
controller,
just
controls
the
builder-
and
you
can
use
this
with
any
build
tool
that
you
use
automation,
tool
that
you
want
to
use
right.
We
talked
about
some
of
those
build
automation.
Tools
before
right,
so
using
jenkins
is
actually
pretty
straightforward
right
and
it
kind
of
like
saves
you
a
lot
of
time
compared
to
jenkins.
A
With
the
steps
you
have
to
take
on
to
a
release,
I
love
those
processes
I
kind
of
like
to
automate
it
right.
So,
as
you
can
see
here,
this
is
how
you
know.
Jks
architecture
looks
like,
and
if
you
have
any
questions,
we
will
talk
about
those
specific
questions
in
this
q.
A
right.
The
other
thing
you
need
to
remember
is
that
you
can
use
jenkins
user
interface
and
agree,
and
you
can
use
jenkins
command
line
all
right
and
there's
the
js
api.
A
You
know
tools
that
they
are
working
with,
that
they
have
set
up
that
the
whole
team
is
using,
so
jenkins
x
is
built
from
the
ground
up
for
cloud
environments,
so
if
you're
using
aws,
if
you're
using
asia,
if
you
are
using
google
cloud
jenkins
x,
is
perfect
because
it
was
built
layer
from
the
architecture
idea
from
the
design
of
the
jenkins
exponent
teams
were
kind
of
like
thinking
about
it.
They
thought
about
cloud
deployment
right.
A
You
know,
so
everything
that
you
want
to
do
in
a
cloud
environment
with
jenkins
x
is
already
pretty
set
up
for
you.
You
can
run
things
faster,
unlike
jenkins,
right.
The
big
advantage
for
jenkins
is
that
is
developed
from
the
ground
up
with
cloud
deployment
in
mind
right.
So
that's
one
big
advantage.
Another
big
advantage
that
you
have
with
jenkins
x
over
jenkins
is
that
jenkins
x
was
built
where,
with
intent
or
distributed,
distributed
deployment.
Nowadays,
companies
don't
just
launch
the
applications.
A
Just
on
you
know
one
server
they
launch
it
on
one
support
service:
one
you
know
deployment
will
serve
as
backup
for
the
other
and
jenkins
x
supports
that
easily
right.
Another
advantage
that
you
have
with
jenkins
x
is
thinking
it's
supports,
like
naturally
and
easily
the
fly
mate.
So
if
you
want
to
kind
of
deploy,
multiple
docker
containers
right,
you
can
use
jenkins
compared
to
jenkins
jenkins,
doesn't
naturally
support
container
containerized
deployments.
A
So,
if
you're
using
jenkins
x,
you
can
see
that
any
team
using
jenkins
vs
jenkins,
and
if
that
team
is
working
like
on
aws,
if
that
team
is
working
with
containers,
if
that
team
is
working
with
distributed
deployment,
they
can
save
a
lot
of
time
right
and
the
advantage
of
also
using
jenkins
over
jenkins
is
normally
in
a
software
team.
Like
you
know,
be
the
distributed
team
across
the
world,
or
even
in
one
place,
the
skills
are
not
the
same.
Not
everybody
knows
kubernetes
right
and
even
those
that
know
to
the
next.
A
A
You
can
make
them
feel
comfortable
by
giving
them
they
can
kind
of
run
like
humanx
commands
right
because
they
can
run
their
cicd
process
and
they
can
issue
commands
to
the
next
api
all
right
using
the
gui
and
the
commands
will
go
to
the
gx
api
and
then
to
jsbi
sends
the
commands
to
the
kubernetes
server
api
right.
So
these
are
some
of
the
advantages
of
jenkins
x
over
jenkins,
right
and
jenkins.
X
also
makes
it
easier
for
people
you
know
to
collaborate.
A
If
there's
a
big
team,
they
want
to
kind
of
like
collaborate
on
their
testing
on
their
decline
on
their
bills,
and
all
of
that
is
made
easy
out
of
jenkins
right.
So
jenkins
is
like
a
feather
development.
It's
a
feather!
It's
a
significant
improvement
of
jenkins,
and
these
are
the
advantages
of
using
jenkins
x
over
jenkins,
and
if
you
are
thinking
about
whether
you
know
you
should
move
to
jenkins
or
you
should
speak
of
jenkins,
we
are
gonna
kind
of
like
talk
about
that.
A
A
and
now
to
yeah
to
the
next
slide-
and
you
know
where
I'll
just
read
captions.
You
know
why
you
should
kind
of
like
move
to
jenkins
x
if
you're
already,
you
know
running
on
jenkins,
if
you
see
icv
teams,
your
company
is
running
on
jenkins.
Like
you
know,
one
of
the
way
you
can
convince
the
whole
team
and
the
company
to
look
to
genuine
some
of
the
benefits,
advantages
that
we
discussed
I
mean
before,
but
if
you
are
thinking
about
you
know,
I'm
not
sure.
A
I
think
that
advantages
and
you
know
the
cost
savings
or
the
time
savings
in
other
ways,
any
kind
of
like
consideration,
because
jenkins
is
really
a
significant
improvement
of
jenkins
right.
It's
not
just
a
tiny
small
improvement.
Sometimes,
like
you
know,
cicd
tools
are
released
and
they
are
just
like
you
know,
a
tiny
improvement
and
because
jenkins
is
a
significant
improvement,
they
didn't
just
call
it
like.
You
know
they
could
have
called
just
a
higher
version
of
jenkins,
but
because,
like
you
know,
this
is
like
really
a
new
product.
A
This
is
like
really
a
completely
game
changer.
It
was
called
jenkins
and
the
x
means
that
it's
actually
they
want
to
showcase
that
they
want
to
show
that
this
is
like
really
not
the
same
as
jenkins
as
you
know,
but
it's
something
much
better.
It's
something
like
you
know,
significant
improvement
right.
A
So
you
can,
you
know
I'll
make
my
presentation
available
if
you
want
to
kind
of
use
it
to
kind
of
like
convince
your
team
to
move
to
jenkins
x,
and
if
you
want
to
convince
your
team
that
jenkins
x
is
really
easy
to
use.
It
will
save
you
time
to
save
your
money.
It
will
you
know
all
team
members
that
you
have
in
engineering
can
be
more
confident
using
jenkins
x
right
and
just
to
convince
your
team
that
the
learning
curve
is
pretty
fast
right.
A
So,
if
you
have
to
move
your
team
from
jenkins
to
jenkins,
there's
gonna
be
some
resistance
right
and
you
need
to
prepare
yourself
away
because
nobody
wants
to
let
you
start
like
you
know,
change
what
they
know:
change
like
tools
that
they're
running
change
processes
they
have
set
up.
They
don't
want
to
do
that.
They
want
to
kind
of
like
keep
the
systems
they
are
running
so
that
they
don't
have
to
kind
of
spend
time
learning
something
new.
A
So
the
architecture
of
jenkins,
this
image
actually
showcases
how
easy
it
is
and
how
smooth
it
is
to
work
with
jenkins
it's
in
a
team
right
now,
if
your
team
is
using
other
cicd
tools,
I
will
surely
advise
you
to
kind
of
check
out
jenkins.
It's
really
really
really
nice
the
icd
tool
and
compared
to
travis
compared
to
updater
compared
to
certain
ci.
This
is
a
significant
improvement
all
right
if
your
team
is
not
using
any
ci
cd2
at
all-
and
you
are
thinking
of
you
know,
using
a
ci
cd
tool.
A
A
They
will
stop
developing
jenkins
and
they
will
focus
on
basically
mainly
junction
6.,
and
I
mean
they
haven't
mentioned
that
now
I
haven't
read
it
anywhere,
but
I
think
that's
going
to
happen
because
they're
not
going
to
provide
two
cicd
tools
at
the
same
time,
they're
gonna
kind
of
like
you
know,
combine
everything
into
one
and
that'll
be
jenkins
x,
which
is
gonna,
replace
jenkins.
So
that's
it
and
I'm
gonna
be
around
well
the
q
a
session.
A
If
you
have
any
questions,
you
can
kind
of
ask
me
all
right
and
I'll
also
leave
my
contact
details
here.
So
this
is
the
website
of
my
company
education
ecosystem,
and
this
is
my
email,
and
this
is
my
skype.
If
you
want
to
reach
out
to
me
the
best
race
email,
I
prefer
email
and
in
case
we
need
to
talk,
we
can
jump
on
skype
right.
So
these
are
my
contact
details.
I'm
gonna
stick
around
a
bit
for
q
a
so.