►
From YouTube: Accelerate Software Delivery with CloudBees Jenkins on Red Hat OpenShift Container Platform
Description
Container-based application development platforms and DevOps initiatives are transforming the way enterprises build and deploy software. The latest versions of OpenShift includes Jenkins®, enabling development teams to build, test and deploy their applications in a fully automated manner.
Some of the challenges facing OpenShift users are that they don’t have access to Jenkins expertise, can’t enforce company guidelines, lack fine grained access controls or guarantee plugin compatibility. The answer to these challenges is CloudBees Jenkins Enterprise running natively on OpenShift. Join our session and learn everything CloudBees & Red Hat including solution features, benefits, and more.
A
Now
Jenkins
is
the
number
one
CI
CD
tool
in
the
open-source
community.
It's
been
around
for
a
while.
Now
it
has
become
something
of
a
standard
when
it
comes
to
CI,
CD
automation,
it's
pretty
well
known,
I
won't
spend
a
lot
of
time
talking
about
Jenkins
just
because
this
is
well-trod
ground.
Suffice
it
to
say
that
cloudBees
is
the
Jenkins
company.
So
what
is
the
the
the
power
of
Jenkins?
Really,
though,
is
the
is
the
Jenkins
community.
Jenkins
has
a
pluggable
architecture,
so
we
really
encourage
folks
to
create
plugins
to
connect
their
favorite
software
they're.
A
You
know
favorite
source
control
tools
and
various
other
kinds
of
tools
to
Jenkins.
As
of
last
count,
we
had
over
1400
plug-ins.
That
number
increases
everyday,
not
sure
what
the
latest
figure
is,
but
I
expect
that
to
keep
growing.
So
there
are
some
challenges,
though,
when
we
talk
about
Jenkins
in
an
enterprise
context,
we
run
into
a
couple
of
anti-patterns
that
kind
of
develop
organically
as
organizations
start
to
use
Jenkins.
So
the
first
pattern
or
anti-pattern,
we
might
say
the
first
stab
at
using
Jenkins
in
an
organization,
usually
consists
of
one
or
more
teams.
A
In
an
organization
standing
up
an
open-source
Jenkins
master
and
beginning
to
create
jobs
and
to
to
build
on
on
Jenkins,
this
results
in
something
that
we
could
the
the
the
name
we've
given.
This
anti-pattern
is
Jenkins
sprawl
and
the
reason
it's
an
anti-pattern
is
because
there's
a
lot
of
repeated
work,
there's
a
lot
of
repeated
effort
and
therefore
wasted
effort,
as
each
team
is
essentially
reinventing
various
wheels
as
they're
getting
Jenkins
going
and
getting
their
their
pipelines
and
their
jobs
going.
A
So
the
the
this
usually
leads
to
the
second
anti-pattern,
which
is
something
we
call
skyscraper
Jenkins
skyscraper
Jenkins
happens
when
somebody
says
hey:
we've
got
all
these
Jenkins
masters
everybody's
kind
of
doing
their
own
thing.
It's
the
Wild
West
we're
repeating
all
this
effort.
It's
not
very
efficient.
It's
not
very
manageable!
There's,
not
a
lot
of
visibility
into
what's
going
on
in
our
Jenkins
environment.
So
let's
bring
everybody
together
on
one
Jenkins
master
and
and
I
see
some
heads
nodding,
yeah.
The
folks
most
folks
that
have
used
Jenkins
in
an
enterprise
context
have
encountered
this.
A
A
They're
talking
to
us
about
things
like
how
can
we
tune
our
garbage
collection
to
to
collect
old
jobs
faster
and
free
up
some
memory
and
we're
like
okay,
really,
what
you
need
to
do
is
split
this
up,
so
this
is
where
cloudBees
comes
in.
What
we
want
is
you
know
each
of
these
two
anti-patterns
tries
to
achieve
something,
and
in
doing
so,
it
fails
to
achieve
the
other
thing
right
really.
Well,
there
are
two
things
we
want
to
achieve.
A
We
want
manageability
and
central
visibility,
but
we
also
want
scalability
and
autonomy
at
the
team
level,
and
this
is
where
this
is
where
cloudBees
Jenkins
Enterprise
comes
in.
So
the
way
cloud-based
Jenkins
Enterprise
works
is
that
you
have
what's
known
as
cloud
be
as
Jenkins
Operations
Center.
This
is
a
Jenkins
master.
That's
MA,
two
minute
to
manage
other
Jenkins
masters.
It's
the
kind
of
a
master
of
masters
is
what
we
like
to
say.
A
The
creation
of
a
new
managed
master
is
what
we
like
to
call
these
masters
that
are
managed
by
the
operations
center,
so
we
can
create
a
new
managed
master
using
open
shift
and
we're
just
simply
spinning
up
a
pod
and
running
some
configuration
scripts,
configuring
it
connecting
it
back
to
the
Operations
Center,
and
we
can
also
make
use
of
things
like
dynamic,
dynamically
created
agents.
So
this
is
something
that
you
can
also
do
in
kind
of
the
in
the
non
openshift
world.
A
A
So
what
is
this
benefit?
Well,
as
I
said
what
this
does
is
this
cloud-based
Jenkins
Enterprise
really
achieves
the
two
things
that
we're
trying
to
achieve
both
in
the
Jenkins
sprawl
anti-pattern
in
the
skyscraper
Jenkins
anti-pattern
we're
achieving
central
manageability
and
visibility,
but
we're
also
achieving
decentralized,
we're
decentralizing
that
that
management
to
some
extent
we're
centralizing
the
visibility
and
we
have
the
option
of
centralizing
management.
But
when
it
comes
to
things
like
plugins,
each
individual
team
can
install
its
own
suite
of
plugins.
It
can
configure
Jenkins
how
it
needs
to
to
configure
Jenkins.
A
So
what
you
get
with
Jenkins
on
top
or
excuse
me
what
you
get
with
cloudBees
Jenkins
Enterprise.
On
top
of
these,
these
great
enterprise
features
that
are
not
available
in
the
in
the
open
source
version.
You
also
get
cloudBees
support,
so
cloudBees
engineers
contribute
about
80%
of
the
code
to
to
the
open
source
Jenkins
prod
project.
A
In
short,
we
are
the.
We
are
the
company
that
that
facilitates
the
development
of
Jenkins.
Much
like
Red
Hat
facilitates
the
ongoing
development
of
Linux
and
kubernetes,
and
all
these
other
great
projects
that
Red
Hat
is
involved
with,
and
our
CTO
is
co-state
Kawaguchi
or
kk.
For
short,
kk
was
the
engineer
at
sun
microsystems
who
developed
jenkins.
Initially
it
was
just
an
under
the
desk
project
and
it
was
known
as
Hudson
in
those
days
at
at
some
point.
A
Jenkins
was
forked
from
the
original
hudson
project
and
became
jenkins
that
we
know
today
and
as
I
mentioned
already
at
that
data
point
okay,
so
we
have.
In
addition
to
support
from
our
great
support
engineers,
we
also
have
things
such
as
online
training.
We
have
a
great
portal
for
that.
We
also
have
an
amazing
global,
consulting
professional
services
team
that
can
help
you
get
going
with
Cloud
Beach
Jenkins
Enterprise
and
ensure
that
you're
successful
with
that,
and
we
also
have
a
jenkins
certification.
A
In
addition,
we
also
make
use
of
the
the
blue
ocean
interface.
We
kind
of
extend
that
a
little
bit
into
creating
a
very
simplified
experience
for
creating
a
team.
If
you
want
more
detail
about
that,
we
have
a
demo
playing
on
a
loop
in
in
our
booth.
I
won't
have
time
to
get
to
a
demo
today,
but
if
you're
interested
in
that,
please
stop
by
the
booth
and
I'll
be
happy
to
walk
you
through
it.
A
So,
as
I
mentioned,
cloudBees
Jenkins,
Operations
Center,
we
also
have
a
number
of
features
available
in
cloud
base.
Jenkins
Enterprise
and
some
of
these
are
pretty-
are
pretty
essential
to
really
doing
Jenkins
in
a
scalable
enterprise
way.
One
of
those
is
pipeline,
checkpoints,
so
let's
say
I'm
running
a
build
and
let's
say
my
build
and
test
fit.
The
test
stages
take
two
hours
right
and
then,
following
that
I
have
a
deploy
stage.
A
This
is
a
simplified
model,
I
realize,
but
for
the
sake
of
argument,
let's
say
that's
my
architecture
and
let's
say
I,
do
a
build
and
test.
But
then
my
deployment
fails
just
because
of
a
some
transient
network
error
or
a
DNS
server
goes
down.
In
other
words,
it
fails
for
some
reason
that
has
nothing
to
do
with
the
input
to
the
build.
It
has
nothing
to
do
with
the
changes
to
the
source
code
that
triggered
the
build
or
whatever
event
triggered
the
build.
It
really
just
has
to
do
with
something
totally
random.
A
I
don't
want
to
necessarily
rerun
my
entire
pipeline
really
I
want
to
just
start
from
that
deploy
phase
and
just
deploy
it
because
I
know
it
builds
I
know
that
it
passes
its
tests,
and
so
this
checkpoint
feature
allows
me
to
do
that.
It
allows
me
to
define
a
checkpoint
and
then
replay
a
pipeline
from
that
checkpoint.
Another
great
feature
we
have
here
available
in
cloud
B's,
Jenkins
Enterprise,
is
cross
team
collaboration.
So
I
mentioned
we
have
all
these
these
masters
and
they're
centrally
managed
by
an
operation
center
well.
A
That
operation
center
can
actually
act
as
a
message
broker,
and
so
you
can
set
up
a
publish/subscribe
model
between
pipelines
and
even
between
pipelines
on
different
masters.
So
I
can
have
a
pipeline
on
one
master.
That,
let's
say,
let's
say
it's
a
pipeline
for
a
work
that
a
bunch
of
my
applications
use
so
I
make
some
changes
to
that
framework.
Now
I
want
to
notify
all
of
the
applications
that
depend
on
that
framework
that
hey
there's
a
new
version
available.
A
You
might
want
to
pull
it
in
the
changes
and
build
them
and
test
them
against
your
application
code,
and
so
all
we
have
to
do
with
this
cross
team
collaboration
feature
because
we
have
this
Operations
Center.
We
can
essentially
just
publish
a
message
to
operation
center.
That
says:
hey
this,
this
pipeline
built
and
then
any
pipeline
that
that
has
that
framework
as
a
dependency,
let's
say,
can
define
a
trigger
so
that
anytime,
that
that
event
gets
submitted.
It
will
trigger
a
new
build
for
that
pipeline
and
that's
really
just
one
use
cases.
A
There
are
lots
of
use
cases
for
that,
because
this
is
really
just
a
generic
pub/sub
event
model
that
can
be
used
for
all
kinds
of
things.
Another
great
feature
of
cloudBees,
Jenkins
Enterprise,
is
that
we
have
a
very
granular
security
model,
so
we
extend
the
open-source
Jenkins
security
model.
We
have
a
lot
more
permission
bits
you
can
really.
You
can
really
go
crazy
with
the
the
role-based
access
control
that
you
can
create.
Now
this
is
this
kind
of
gives
you
an
idea
of
what
the
scope
of
this
rback
plugin
I
know.
A
So
another
another
really
killer
feature
of
the
enterprise
product
is
the
cloudBees
assurance
program.
So
one
issue
with
using
any
open
source
project,
especially
one
like
jenkins,
that
has
such
a
huge
ecosystem
of
plug-ins
and
has
so
many
different
options
and
choices
out
there.
As
a
user
of
Jenkins,
it
can
be
really
easy
to
get
decision
fatigue
right,
like
which
of
these
plugins
do
I
use.
There's
you
know
five
get
plugins,
which
one
is
the
one
that
I
want
to
use.
A
Well,
the
cloud
be
assurance
program
is
designed
to
to
kind
of
give
you
an
opinionated
way
of
looking
at
all
of
the
the
plug-in
ecosystem,
so
that
you
can
make
quick
decisions
about
which
plugins
to
use,
because
we
actually
go
out
into
the
community
and
verify
certain
plugins
and
say
yes,
okay,
these
are
these
are
the
plugins
that
we
recommend
that
you
use
and
we
will
distribute
them.
We
actually
distribute
them
to
you
and
we
also
provide
something
called
the
beekeeper
upgrade
assistant
which
allows
us
to
manage
the
upgrade.
A
A
So,
as
I
said,
I
won't
have
time
for
a
demo
today,
but
I
just
want
to
kind
of
reiterate
that
you
know
cloudBees
is
the
Jenkins
company.
We
are
the
Jenkins
experts,
we
are,
you
know
fully
committed
to
the
health
and
well-being
of
the
Jenkins
community
as
an
open-source
community
on,
and
we
believe
that
cloudBees
Jenkins
Enterprise,
which
runs
on
RedHat
OpenShift,
complements
OpenShift
very
well
and
is
a
great
solution
for
folks
that
want
to
run
Jenkins
on
OpenShift
in
a
scalable
and
manageable
way.