►
From YouTube: GitLab vs Jenkins Cure Your Plugin Overload
Description
GitLab vs. Jenkins: Cure Your PlugIn Overload (Webinar)
No third party plugin headaches
This is a rare opportunity to attend a very informative and interesting webinar from GitLab, presented by Itzik Gan-Baruch, Technical Marketing Manager at GitLab.
Jenkins plugins vary in quality and may lose support without notice, which is a nightmare for you and your team. See how GitLab’s seamless workflow between SCM & CI helps your team do better work at greater speeds.
Reduce Risk
Jenkins users frequently experience service instability from running bigger workloads with a large number of plugins. Learn how GitLab decreases toolchain downtime and eliminates risky integrations.
Lower Cost & Increase Efficiency
Jenkins requires dedicated resources, admins, and maintenance – increasing the total cost of ownership. GitLab requires fewer steps to deploy code and developers spend more time writing code and less time maintaining the toolchain.
A
A
Hello,
everyone
and
very
warm
welcome
to
all
of
you
to
this
webinar
session
with
us
and
our
his
partner
gitlab
on
the
topic
of
github
versus
Jenkins,
Curie
or
a
plug-in
overload.
My
name
is
Peter
and
I
will
be
your
moderator
for
the
session
I
sincerely.
Thank
all
of
you
for
your
participation
in
this
webinar
and
really
can
be
looking
forward
to
an
engaging
session
a
little
bit
about
the
webinar.
A
Let
me
also
take
a
moment
to
introduce
our
speaker
for
the
day
Itzik
GaN
Beru,
it's
it
is
a
technical
marketing
manager
at
gate
lab
with
more
than
20
years
of
experience
working
with
enterprise
software
companies.
It's
it
has
an
engineering
product
and
marketing
background
expert
in
bridging
the
gap
between
business
and
technology.
Itzik
offers
invaluable
guidelines
to
get
lab
customers
by
creating
and
delivering
technical
demos
and
workshops.
Just
a
couple
of
last-minute
house
rules
before
we
get
started
here.
A
All
of
us
will
be
muted
during
the
presentation
and
only
Itzik
will
have
the
right
access
to
present
information.
It's
six
presentations
is
going
to
last
for
roughly
40
minutes
and
then
he
will
open
the
floor
for
questions.
Of
course,
if
you
do
have
some
questions
beforehand,
please
do
not
hesitate
to
use
the
questions
tab
on
the
right
side
panel
on
your
screen.
A
You
may
type
in
the
questions
and
we
will
take
a
note
of
the
same
and
either
we
would
answer
the
questions
right
then,
and
there
in
the
window
or
we'll
ask
it
sit
for
an
answer
during
the
Q&A
part.
In
the
end,
assuming
you
have
good
internet
connectivity,
this
whole
session
should
run
smoothly
without
any
impediments.
A
And,
finally,
this
webinar
session
will
be
recorded
and
a
copy
of
the
recording
will
be
passed
on
to
each
one
of
you
why
an
email,
once
the
session
is
over
by
the
gate,
lab
team
directly
now
without
any
further
delay
I
hand
over
the
floor
to
it
safe
to
run
us
all
through
this
webinar
session
on
gift
lab
versus
Jenkins
cure
your
plug
in
overlooked.
It's
over
to
you
thank.
B
You
and
hi
everyone,
and
thank
you
for
joining
to
the
webinar
today,
so
the
agenda
for
today
is
I
will
share
with
you
some
summer.
Jenkins
pain,
points
that
we
hear
for
me.
Jenkins
had
means
and
the
users
and
then
just
a
point
when
I
speak
about
Jenkins,
say
for
today.
Webinar
I
refer
to
the
open
source
or
free
version
of
Jenkins,
the
more
EF
versions
like
cloudBees
o-genki
X,
which
is
not
the
part
of
today's
session.
B
B
As
a
Technical
Marketing
Manager
I
had
the
chance
to
speak
with
a
few
Jenkins
users
and
admin
and
hear
from
them
why
they
decided
to
do
most
to
github
and
some
of
them
didn't
decide
to
move
to
the
kit
lab
but
I'm
going
to
share
with
you
a
common
things.
Common
pain
points
that
they
they
told
me.
So
everyone
know
the
Jenkins
is
a
free,
but
but
the
end
at
the
end,
the
total
total
cost
of
ownership
is
very
high
of
junkies.
B
So
it's
not
free,
because
Jenkins
has
a
maintenance
and
the
architecture
requires
a
larger
set
of
build
environment
and
say
master
and
slave.
So
you
need
to
manage
a
lot
of
machine.
We
dedicated
people
to
manage
all
of
this
complexity
and
you
need
to
monitor
them.
You
need
infrastructure,
so
at
the
end
of
the
day,
it's
high-
maintenance
and
the
I
and
total
cost
of
ownership,
and
when
I
spoke
with
people
about
upgrade
questions.
B
Like
example,
when
was
the
last
the
last
time
that
you
upgraded
the
jenkins,
I
heard
people
say
three
years
ago
or
three
years
ago
and
when
I
asked
them
why
they
said
it's
not
easy
to
upgrade.
So
if
I
upgrade,
then
there
is
a
chance
that
some
of
the
functionality
will
not
walk
because
of
the
plug-in
compatibility.
B
So
they
are
in
the
situation
that
they
are
scared
to
upgrade
the
versions,
and
they
say
if
it
works,
they
don't
touch
and
when
I
am
talking
about
upgrade
and
referring
to
the
Genny
server
or
to
upgrade
a
plug-in,
because
you
upgrade
plug-in
a
fixed
one
problem.
But
then
you
will
have
other
problems
with
other
plugins
and
and
the
thing
with
jank
is
because
the
customers
they
I
met
people
with
the
hundreds
of
plugins
and
when
they
have
a
problems,
it
really
difficult
to
pinpoint
and
understand.
Where
is
the
problem?
B
It's
hard
to
debug
that
another
thing
that
I
keep
here
is
a
Jenkins
is
used
a
goofy
as
the
language
of
the
configuration.
The
problem
with
the
groovy
is
easy
to
developer
the
skipped
language
and
easy
to
developer,
to
create
complex
logic
that
that
then,
is
hard
to
maintain
and
also
it
out
to
debug.
B
There
is
no
way
to
debug
groovy,
so
what
they
do,
usually
they
print
out
some
text,
some
messages
into
the
console,
and
this
is
the
way
they
find
they
try
to
debug
and
understand
problems
and
also
not
everyone
familiar
with
the
Java
or
groovy.
So
it
said
it's
difficult
for
many
people
to
use
groovy
and
another
point,
as
the
Jenkins
is
not
just
CI
tool
is
the
automation,
tool
and
companies
they
like
it,
because
it
allows
you
to
do
everything
so
any
automation
that
they
need
to
do.
B
Another
big
problem
of
Jenkins
is
the
community
plugins,
so
with
Jenkins
you
can
do
almost
everything,
but
for
everything
that
you
want
to
do
in
a
junkies,
you
need
to
rely
on
a
community
plugins
plugins
that
developed
by
a
third
party.
It
can
be
students
or
part-time
people
and
many
people.
We
need
to
waste
a
lot
of
time
to
understand
which
plugin
they
need
to
use,
because
there
are
many
plugins
for
each
function.
B
B
Plugins
has
at
least
each
plug-in
has
a
list
of
compatibility,
so
each
plug-in
depends
on
some
other
compatibility.
So,
for
example,
if
you
have
a
java-
and
you
need
to
upgrade
this
java
in
order
to
install
one
plug-in,
then
three
other
plugins
will
not
work,
because
they
cannot
be
supported
with
the
newer
version
of
java
and
another
problem
that
impact
a
large
enterprises
is
lack
of
visibility
and
control.
Because
what
happened
in
Jenkins,
there
are
many
teams.
B
B
B
More
issues
with
Jenkins
is
it's
not
its
scalability
issue,
because
it
doesn't
support
a
clustering
or
failover.
It
introduced
security
issue
because
when
people
download
the
third-party
plugins
that
you
don't
know
who
wrote
those
these
plugins
plugins,
do
you
know
if
there
is
secured?
Maybe
they
contain
some
vulnerabilities?
So
this
is
a
bring
security
issue
also
for
large
organization.
There
is
a
access
and
permission,
a
question
who
can
access
Jenkins
to
which?
What
module?
Okay,
you
can
access
and
what
is
the
level
of
permission
you
get
in
each
module?
B
Jenkins
out-of-the-box
doesn't
provide
you
this
and
then
again
you
are
the
owner.
You
need
to
find
a
suitable
plugin
for
that
to
solve
this
problem
and
of
course
there
is
lack
of
end-to-end
auditing
and
compliance,
and
something
which
is
very
important
for
DevOps
is
visibility
and
collaboration,
and
with
Jenkins
user
even
can
see
others,
users
commit
and
the
users
don't
have
any
visibility
to
deployed
applications
and
the
development
lifecycle.
B
Jenkins
is
only
a
CI
tool,
so
CI
is
a
great
to
use
for
DevOps
as
a
beginner,
but
for
mature
DevOps,
a
mature
customers
do
CI
CD
and
if
you
use
Jenkins,
it
allows
you
to
CI,
and
then
you
will
need
to
take
care
for
the
CD,
buy
some
custom
deployment
script
and
again
you
have
on
your
own.
You
want
you
need.
There
is
no
tool,
that's
due
for
you,
the
job.
You
need
to
take
care
for
everything.
B
So
this
is
another
thing
or
the
you
need
also
to
use
a
third
party
and
in
in
this,
in
this
slide,
I
want
to
mention
and
Jenkins
IG's,
because
Jen
connects
is
a
new
version
of
Jenkins
that
come
to
address
the
CD.
It
provides
CD
capabilities
and
containers
and
kubernetes
integration,
but
it
inherits
the
problems
that
the
Jenkins
has
simply
because
Jenkins
X
is
not
in
your
code
is
a
patch
of
functionality
on
top
of
the
Jenkins
2.0,
so
all
of
the
the
problems,
like
maintenance
been
again
upgrade.
B
Another
challenge
that
Jenkins
X
introduces
is
it
requires
high
system
requirement,
so
gun
of
the
day.
Is
that
if
you
have
the
problems
with
Jenkins,
you
have
a
machine
in
your
team.
You
just
install
Jenkins
and
solve
and
make
a
walk
run
by
creating
another
instance
of
Jenkins
with
the
Jenkins
X,
you
will
need
to
find
very,
very
strong.
You
will
not
have
attended
such
a
machine
to
make
walk.
B
B
Companies
is
Android
of
tools
they're
using
different
data
models
which
lead
to
lack
of
transparency.
Different
people
walk
with
different
tools
which
create
silos
team,
but
breaking
down
the
silos
was
the
wall
point
of
DevOps.
In
the
first
place,
more
ever
dedicated
people
need
to
design
build,
maintain
this
fragile
tool
chain.
This
tool,
change
complexity
is
the
problem
that
get
lab
solved.
B
B
Right
so
now,
I
want
to
a
little
bit
expand
about
the
advantages
of
github.
So
first
of
all,
get
lab
is
a
one
tool
for
SEM,
which
is
version,
control,
C,
ICD,
issue,
tracking
security
testing
and
monitoring.
You
don't
need
the
plugins
in
customization.
You
have
one
one
application,
you
get
everything
that
you
need
for
the
your
DevOps.
B
It
is
it's
very
easy
to
maintain
and
update
get
lab.
So,
for
example,
if
you
want
to
upgrade
github,
you
just
need
to
replace
one
docker
image
and
when
you
upgrade
the
this
docker
image
it
up
great
for
you
not
only
the
CI
but
the
CI
CD
issue,
tracking
and
all
of
the
components
by
replacing
one
docker
image
and
very
easy.
Without
the
risk
you
don't
need
to
scare
and
github
release
a
new
version
every
22nd
of
each
month.
B
Another
thing
is
that
github
is
optimized
for
containers.
It
is
building
building
container
registry
and
kubernetes
integration.
Cluster
monitoring
review
up
all
of
the
things
that
you
need
for
developing
cloud
native
in
the
application
you
have
attendee
form
the
application
and
developers
has
visibility
to
the
entire
development
lifecycle,
a.
B
Little
bit
drill
down
in
our
github
walks,
it's
a
little
bit
different
than
Jenkins.
So,
while
in
Jenkins
you
have
the
master
and
slave
was
master
and
slave.
Here
we
have
a
github
runner.
The
one
here
is
the
agent
that
actually
runs
the
CI
CD
run
a
written
in
go
for
portability,
so
you
can
install
it
anywhere
that
support
go
and
it
has
a
native
docker
support
and
when
I
say
docker
support
is
not
for
the
deployed
application,
but
all
of
the
build
run
inside
a
docker.
B
So
if
in
a
Jenkins
you
need
that
you
have
the
built
slave
and
then
you
need
the
on
that
VM
to
make
sure
to
install
off
the
all
of
all
of
the
build
tools
like
Java
and
the
OB,
and
all
of
the
things
that
you
need
in
order
to
run
your
job.
You
don't
have
to
take
care
for
that
in
Gator,
because
in
github,
when
the
job
start,
you
will
download
the
docker
image
local
container
image
and
services
and
run
all
of
the
job
inside
the
container.
B
When
the
job
may
end,
it
will
revert
back
the
machine,
so
in
order
to
set
up
a
rather
machine,
you
just
need
a
machine
to
install
a
little
runner
and
docker
docker
container.
You
need
to
install
no
more
than
that
and,
of
course,
it
has
built
in
a
auto
scaling.
So
I
don't
need
to
have
a
farm
like
in
Jenkins
with
the
many
slaves
waiting
for
your
jobs,
because
the
build
machine
will
be
created
on
demand
for
you
and
also
it
will
set
you
a
lot
of
money.
B
So
while
the
runner
is
running
the
CI
CD
jobs
here
is
a
look
of
how
the
grid
lab
CI
see
the
configuration
it
looks
like
so
it
uses
a
structure
of
the
Apple
format,
easy
to
learn
and
it
prevent
complexity,
because
all
of
the
logic
is
not
exist
in
in
the
UML
format
and,
of
course,
it's
version.
Also
in
Jenkins
is
version
you
can
edit
it
in
your
IDE
and
it's
part
of
the
repository
on
the
right
side.
You
can
see
an
example
of
script,
the
ML
script,
double
file
actually
and.
B
B
This
slide
show
the
one
permission
model
in
github,
so
you
have
a
five
different
level
of
roles:
guest
reporter
developer,
maintainer
and
owner
and
in
the
help
there
the
screen
on
the
right
side,
you
can
see
which
role
can
access
to
which
model.
So
you
define
when
you
define
the
user,
you
give
them
an
assignment
role
and
then
this
role
will
be
good
to
all
of
the
devs
components
and
the
operations
component.
B
B
So,
just
to
summarize
what
we
talked
about-
gentle
kissing
gitlab,
this
is
a
table
that
summarize
the
key
differences
between
Jenkins
and
it
lab.
So,
while
Jenkins
is
the
natively
only
continuous
integration
tool,
github
is
a
complete
DevOps
DevOps
platform.
As
you
get
complete,
depth,
see
ICD
tool
chain
out
of
the
box
with
SCM
security,
testing
issue,
tracking
monitoring
and
thousands
and
features
Jenkins
relies
on
integrating
community
plug-ins
for
basic
capabilities
everything.
So
if
you
need
the
SCM,
if
you
need
issue
tracking
woloson
permissions
docker
for
everything,
you
will
need
the
plugin.
B
While
github
delivered
the
single
application,
you
have
one
installation,
one
interface,
one
conversation,
one
permission
model
and
the
last
one
is
the
time
where
the
be
the
two
products
started.
So
Jenkins,
relatively
old
technology
was
not
designed
for
supporting
cloud
native
development.
What
started
on
2004,
while
github
started
on
to
thousands
of
thousand
14
cloud
and
container
where
there
it
was
known
it
is
the
standard
in
the
future.
B
B
So
so
this
is
a
great
lab,
a
project
you
can
see
the
project.
Id
I
pushed
a
simple
Java
source
code
to
the
project,
nothing
special
in
this
a
Java
code.
Even
does
it
I,
don't
have
a
CI
CD
configuration
file
in
the
project.
You
never
enable
the
auto,
dev,
ops
and
auto
devops
is
a
feature
that,
based
on
a
pre-configured
CI
CD
templates
that
get
lab
a
provide
out
of
the
box.
So
what
it
does,
it
will
do
for
you,
the
all
of
the
CI
CD
automatically
and
I
will
show
you
in
the
demo.
B
Also
in
this
project,
I
configure
the
kubernetes
cluster.
So
this
project
is
there
ever
connected
to
cluster
and
in
grid
lab
you
can
there
is
a
native
support
for
clustering,
so
for
communities.
So
if
you
have
any
cluster
on
any
cloud
vendor
or
even
on
your
bare
metal,
you
can
just
connect
it
and
and
use
it
also.
We
have
with
the
Google
gke.
We
have
better
integration
because
you
can
even
from
github
UI.
You
can
automatically
create
cluster
in
Google.
B
Even
if
you're,
not
you
are
not
familiar
with
cluster
with
cluster,
with
kubernetes
with
the
few
fields
in
github,
simple
fields
like
name
number
of
VMs
number
of
nodes,
and
it
will
create
for
you
the
cluster,
alright.
So,
on
the
left
side,
you
see
you
have
many
with
access
to
different
tools,
because
it's
a
single
application.
The
first
one
is
the
project,
the
details.
This
is
the
page
that
we
see
activity.
You
can
see
all
of
the
activities
that
happened
to
the
team.
For
example,
a
push
merge
even
comment
issue.
B
Everything
that
your
peers
in
the
project
have
done.
You
will
see
it
in
the
activity
shifts
very
similar
to
facebook
notifications,
releases
security.
Dashboard
shows
you
all
of
the
risk
and
the
retest
result
of
all
of
the
of
the
project
in
one
in
one
page,
you
can
see
all
of
the
security
risk
and
test
result
of
that
project
dependency
list
cycle
analytics
inside
another
tab
is
the
repository
access
to
your
gate.
You
can
see
the
repository
commit,
commits
branches
everything
you
can
see
from
this
UI
again
issue
tracking,
which
is
part
of
the
application.
B
Merge
request,
see
I
see
the
pipeline's
click
here.
You
will
see
all
of
the
pipeline's
operations,
all
of
your
environment,
your
kubernetes,
your
VMs,
everything
you
can
see
here,
packages
for
container
registry
github
as
a
built-in
container
registry
support.
It
has
a
wiki
site,
snippets
and
project
settings.
B
B
All
right
now,
I
go
to
planning
and
I
will
go
to
the
issue
boards,
and
this
is
a
new
project.
So
I
don't
have
a
list
for
my
board,
and
here
is
a
nice
thinking
about
gitlab
that
every
time.
Well,
you
don't
know
you
tell
you
what
is
the
next
step,
so,
for
example,
here
it
told
me
tell
me,
welcome
to
your
issue
board
and
they
ask
me:
do
you
want
to
have
your
list
or
use
the
default
list,
which
is
to
do
it
doing
so?
B
B
All
right
so
I
created
issue
and
now
I
can
open
the
web
IDE.
So
this
is
another
feature
in
it.
Lab
is
very
handy.
If
you
want
to
have
the
quick
changes
you
don't
need
to
use.
Even
your
local
ID,
you
open
the
web
ID,
it
opened
the
repository.
You
can
select
the
branch
that
you
want
to
use,
but
now
we
have
only
the
master,
so
I
will
go
to
the
code
and
I
will
make
a
quick.
Where
is
the
text
change.
B
B
So
this
is
the
marriage
request.
Method
quest
is
a
main
thing
in
a
github,
because
this
is
a
place
that
we
request
to
merge
my
feature
branch
into
the
master.
This
is
the
place
that
I
need.
We
will
have
all
of
the
discussions
and
all
of
the
test
result
that
will
help
me
to
get
a
decision
if
to
merge
or
not
to
merge
and
we
mark
it
is
a
work
in
progress
automatically.
B
If
you
want
to
drill
down
to
see
what
happen,
you
can
click
here
and
see
the
build
jobs
currently
use
a
local
build
packs
to
build
a
docker
image
and
push
it
to
the
docker
registry.
I
see
the
bills
pass,
so
I
can
go
now
to
the
container
registry
and
I
see
I
reveal
two
images,
one
is
for
the
master
and
one
is
for
the
bridge
that
they've
just
created
so
automatically
it
creates.
B
We
are
using
a
kubernetes
cluster,
so
this
allows
me
to
create
a
private
instance
of
my
change
so
for
each
commit
for
each
branch
we
have
personal
like
think
about
personal
staging
for
you,
with
only
for
your
change
live
application.
Moreover,
now
you
have
dynamic
application,
security,
testing
and
performance
testing
running
on
a
live
instance
of
your
personal
branch.
This
is
a
huge
shift
left
because,
right
after
immediately,
you
push
your
change.
You
get
a
lot
of
feedback
not
only
on
the
static,
your
code,
but
also
feedback
on
your
live
application.
B
B
I
can
now
send
this
application,
and
this
URL
to
my
colleagues,
like
you
weeks
or
PMP,
any
people
that
I
want
to
get
feedback
before
I
decide
to
merge
it
with
the
master
at
the
bottom
of
the
merge
request.
I
see
some
test
result.
The
code
quality
test
says
there
is
no
change
to
code
quality,
but
the
security
detected
vulnerabilities
I
can
click
on
the
report
and
I
say
a
SAST
and
DAST
and
container
and
dependency
scanning.
So
this
is.
B
This
is
huge
functionality,
so,
if
I
had
to
use
Jenkins,
for
example,
I
needed
to
connect
to
at
least
three
or
four
different
tools
with
three
or
four
different
plugins
and
then
I
need
to
be
I
needed
to
get
three
or
four
different
reports.
Now
in
one
tool,
I
get
immediately
static,
application
security
testing
in
the
Namek
application
security
testing
in
one
place
with
zero
configuration.
B
Let's
see
what
what
he
gave
me
gave
me
all
of
those
vulnerabilities
I
get
a
dialog
with
the
some
details
about
severity.
The
source
code,
I,
can
even
click
on
the
source
code.
It
will
open
the
java
code
and
even
highlight
for
me
the
lines
of
code
that
led
to
this
vulnerability.
I
can
click
here
on
the
identifier
which
tell
me
as
a
developer
and
what
was
the
problem
and
we're
always
where
is
the
solution?
How
to
solve
that?
B
And
because
it's
a
single
application
connected
to
other
tool,
I
will
create
now
an
issue
without
with
work
it
created
for
me
automatically
issue
with
all
of
the
details
that
I
need
I
need
in
order
to
fix
it
very
fast
and
now
what
I
need
to
do
is
just
to
assign
it
to
someone
and
we'll
just
be
careful
design
it
to
myself
and
I
will
later
on,
will
fix
the
issue
I've
a
lot.
The
needed
information
now
to
fix
this
issue.
B
And
then
attica,
purity
testing
also
detected
the
fewer
vulnerabilities
and
here,
for
example,
tected
the
quad
site
scripting
in
here.
It
shows
me
a
instances
of
my
lab
application,
so
let's
click
on
one
instant.
This
is
the
instance
of
my
application
that
he
found.
If,
for
example,
there
is
a
forum,
whatever
I
type
here
and
submit
it
print
it
out,
and
this,
for
example,
can
lead
to
cost
site
scripting.
B
That
shows
me
all
the
licenses
and
all
of
the
dependents
that
I
use
in
my
dependency,
sometimes
organization.
If
it's
you
use
license,
is
that
not
comply
with
the
organization
policy?
You
can
you
can
block
it
here
and
block
the
the
way
that
people
will
not
be
able
to
merge
not
allowed
licenses
into
the
master.
B
B
And
it
merge
it
to
the
master
it
closed.
The
issue
number
one
and
a
new
pipeline
started
immediately
now
this
pipeline
and
run
on
the
master
branch,
it's
a
little
bit
different,
because
now
it
will
deploy
not
to
the
review
up.
It
will
deploy
directly
into
the
production,
because
this
is
the
deployment
strategic.
That
I
did
my
default
deployment
strategy
and
that
I
defined
in
the
auto
DevOps
configuration
I
want
to
show
you
and
that
I
create
an
hour
tag
because
I
released
an
application
I
can
create
a
tag,
give
it
a
name
plate.
B
And
now
I
have
automatically
every
release.
With
the
release
note:
I
have
access
to
the
source
code,
everything
available
to
the
developer
and
again
we
have
also
here
all
of
the
artifacts.
It's
now
it's
a
source
code,
but
any
artifact
that
I
defined
in
my
project
like
test,
result
code,
quality
report
or
anything
or
code
coverage.
We
can
have
here
as
an
artifact
that
you
can
download
it
form
the
project,
and
so
this
is
the
development
lifecycle
and
now
I
want
to
show
you
the
operation
side.
B
So
I
go
here
to
the
operation
standing
environment,
and
here
is
all
of
my
environment.
See
here:
I
have
my
production
environment,
but
if
I
add
here
VMs
or
other
environments,
this
is
the
place
that
I
would
say
it
is
the
dashboard.
So
this
little
green
box
represent
kubernetes
pod
if
I
want
to
click
on
it.
It
opened.
B
B
B
B
B
So
with
the
single
application
single
UI,
we
went
in
when
we
made
the
following
actions.
We
created
an
issue
and
made
code
changes
using
the
web
IDE
CIC
the
pipeline
started
the
including
build
test,
deploy
dust
and
performance
test
stages,
review
up
created
for
me
and
docker
image
pushed
to
the
registry
to
the
building
registry.
We
reviewed
the
test
results
and
accepted
the
mayor's
request.
A
new
pipeline
started
and
deployed
the
code
to
production
in
the
production
who
access
the
production,
environment,
UID
logs
the
monitors
and
everything
from
single
application.
A
Yes,
thank
you
so
much
it's
for
that
presentation.
We
have
a
couple
of
questions
that
have
been
posted
on
the
questions
tab
and
the
few
of
them
sent
directly
on
the
chat
tab.
Some
users
chatted
with
us
directly.
So
the
first
question
is:
do
you
have
a
white
paper
stating
your
latency
between
endpoints
within
your
software,
to
edge
implementation.
C
We
don't
have
a
specific
white
paper
if
I
understand
your
question
correctly.
It
is
regarding
how
long
like
just
get
club.com,
for
example,
take
take
to
reach
the
Debian
package
managers.
All
our
infrastructure
is
on
GCP,
so
Google
cloud
platform
and
we
don't
have
any
specific
latency
numbers,
but
since
we're
on
the
Google
Network,
it's
fairly
low
and
it's
not
really
noticeable,
but
this
as
well
also
as
a
case-by-case
basis
of
your
running
Catlett
common
self-hosted.
That's
up
to
you.
Your
network,
set
up
on
your
network
stack.
C
If
you
are
talking
about
the
environments
that
it's
sick
showed
and
they
tap,
it
can
be
your
own
environment,
on
Prem,
in
the
data
center
or
and
like
I,
sure,
I,
sure
cloud
or
anything
like
that.
It's
just
to
three
lines
that
you
put
inside
of
your
code
lab
see.
I
am
a
file
where
you
specify
this
job
will
create
environment
and
it's
located
and
X
location,
and
then
you
can
do
to
place
on
that
environment
automatically.
A
C
We
do
have
support
for
artifacts,
we
do
have
support
for
JIRA
and
artifactory
bit
buckets
as
far
as
I
know.
We
do
not
have
support
for
CI,
but
at
the
end
of
the
day,
get
lab
does
provide
everything
that
that
bucket
artifact,
artifactory
and
JIRA
provides.
So
we
do
have
an
issue
tracker.
It's
a
show
that
artifactory
we
do
have
a
package
registry
right
inside
of
github
or
you
can
publish
maven
belts
and
things
like
that
and
of
course,
Caleb
has
the
source
code
all
there
as
well.
So
integration
wise.
C
That
really
depends
on
your
setup
if
it's
something
that
you're
handling
ten
thousand
to
users
on
Acathla
Princeton's,
maintaining
that
yourself,
but
it
does
involve
some
time
and
the
reason
for
that
as
there's
a
lot
of
moving
parts
on
github,
it's
a
ruby
application
and
then
there's
like
maybe
10-15
other
micro
services.
So
imagine
that
overall,
on
top
over
your
operational,
we
to
handle
all
the
upgrades
and
all
that
automatically
they're
all
scripted.
C
C
We
do
provide
all
of
that
and
we
are
working
work,
working
on
providing
Windows
shared
runners
and
micro
kernels
in
the
future
as
well,
but
your
own
calm
and
you
want
more
powerful
runners,
for
example,
like
let's
say
your
job
consumes
like
20
gigabytes
of
RAM
right.
You
can't
bring
your
own
runner
where
you
sell
it
on
your
own
data
center
or
your
own
cloud
provider,
and
you
will
contact
github.com
and
it
will
run
the
job
for
you.
A
C
So
we
do
releases
every
month,
so
every
22nd
of
the
month
we
do
early
release.
So
if
you
talking
about
the
last
six
months,
it
will
be
six
updates
overall
and
it's
continuous
realist
right.
It's
around
five
to
ten
features
of
it
every
month
or
fixing
some
bugs
and
performance
issues.
I
highly
suggest
you
look
at
our
blog
post
and
the
release
tag
and
that
will
has
will
have
all
the
change
look.
I
can
link
that
to
you
on
the
question.
A
C
So
does
yes,
for
example,
one
integration
we
have
with
slack
is
every
time
a
pipeline
fails.
It
can
leave
a
comment
and
into
a
slack
channel
and
other
things
are,
for
example,
if
you
push,
if
you
open
up
a
new
issue
or
create
a
new
merge
request,
you
get
a
notification
on
slack
or
you
can
even
create
issues
right
inside
of
slack.
So,
if
you're
having
a
discussion
on
slack-
and
you
say-
oh,
this
needs
to
be
an
issue,
so
we
can
track
it.
C
A
A
C
The
huge
locking
part
I
do
understand
that
concern,
but
at
the
end
of
the
day,
our
goal
at
get
lapis
to
be
two
single
DevOps
tool
for
the
single
tool
for
the
whole
difference
like
side,
so
I
do
understand
the
lock-in,
but
at
the
end
of
the
day,
right
now
you
don't
have
a
lock-in,
but
then
you
just
have
an
integration
mess
right.
What
hit
SiC
was
saying
earlier,
like
there's
1015
tools
you
have
to
integrate
together
and
if
want
want
to
change
is
something
your
whole.
C
A
C
Yes,
so
Caleb
does
provide
the
docker
registry
right
inside
right
us
out
of
github,
and
every
job
is
authenticated
to
that
docker
registry.
So
he
can
build
image
and
push
it
into
the
registry
or
pull
from
that
registry
and
a
secure
and
private
matter,
and
it
does
provide
like
all
as
a
normal
docker
like,
for
example,
hop
docker
calm,
it's
just
like
that,
but
on
the
trap
itself
and
it's
pear
project.
So
it's
even
like,
for
example,
a
private
registry.
So
if
you
have
a
private
project,
can
host
a
private
leader
as
well.
A
C
I'm
not
200%
familiar
with
potato
science,
but
we
do
have
some
customers
who
are
doing
like
simulations
and
like
doing
some.
So
we
have
our
own
data
team.
Who
is
doing
this.
I'll
have
to
give
you
a
link
on
how
they
are
using
github
CI
for
running
data
analytics
and
all
that
stuff
I
will
try
and
find
a
link
down.
A
C
Get
lap
runner
must
work
with
get
lab.
It
only
knows
how
to
talk
to
github
and
does
not
talk,
know
how
to
talk
to
any
other
sen
system,
but
we
do
have
github
integration.
So
you,
your
source
code,
can
stay
inside
of
github
and
we
will
run
your
CI
jobs,
but
then,
for
that
to
happen,
you
need
to
have
a
good
lab
installation
that
will
do
all
the
magic
there.
Undone
get
lab
boosts
and
two
jobs
to
get
LeBron
ur.
A
C
C
So
you
can
save
the
credentials
as
I
deliver
a
secret
inside
of
catalepsy
I
and
you
do
a
login
automatically
and
like
we
do
have
like
people,
customers
who
are
using,
for
example,
Cueto
tayo
that
are
music
way,
that
IO
and
using
the
club
CI
to
build
images,
pull
images
and
push
images
to
create
a
tie.
Oh.
C
Get
lab
to
offer
a
community
edition
and
it's
free
and
open
source
for
you
to
download.
Of
course,
we
do
have
a
page
here
and
some
features
are
behind
those
tiers,
but
the
basic
stuff
like
catalepsy
I
running
jobs
during
deployments
for
bernardi's
integrations
most
of
what
a
chick
showed
are
all
in
the
ante
free
version
of
the
community
edition.
A
C
So
we
do,
you
have
a
specific
document.
We
call
it
ticket
lab
flow
and
I
will
give
you
a
link
for
that
on
how
we
suggest
you
to
turn
base
development,
having
different
environments
and
having
different
releases
versions,
and
things
like
that
so
Sun
dot
and
we
I
will
send
also
another
link.
Other
examples,
for
example,
how
to
deploy
a
PHP
application,
how
to
deploy
to
Heroku
and
things
like
that.
A
Awesome
excellent
that
looks
like
all
of
the
questions
were
in
and
all
of
them
were
answered.
But
if
you
do
have
more,
questions
then
feel
free
to
write
back
too
we
connect
team,
so
we
could
pass
it
on
to
it.
Six
team
and
the
gate
lab
team
for
them
to
be
able
to
get
back
in
touch
with
you,
like
I
mentioned
before
the
webinar
session
is
entirely
recorded
and
the
recorded
piece
will
be
sent
to
you
each
one
of
the
registrants
by
an
email
by
the
gate
15.