►
From YouTube: 2021 04 27 Jenkins Infra Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting
before
we
start
just
two
announcements.
The
first
one
is
damian
and
I
will
work
on
updating
the
increased
controller
that
we
use
on
the
activation
cluster.
This
is
a
task
that
we
delayed
for
too
long.
Basically,
so
it
involves
deploying
a
new
controller,
redirecting
the
traffic,
the
dns
traffic,
the
network
traffic,
sorry
to
the
new
controller.
While
we
put
down
the
old
one,
so
nothing
I
mean
normally,
we
should
have
should
not
have
any
downtime
but
yeah
the
risk.
A
B
A
Yes,
so
every
website,
so
that's
why
we
deploy
a
second
one.
So
the
idea
is
we
deploy
a
second
one
and
redirect
our
traffic
to
the
second
one.
We
upgrade
the
first
one
and
then
we
go,
but
we
redirect
the
traffic
to
the
first
controller.
So
that's
that's
the
idea
so
because
those
are
just
stateless
application,
it
shouldn't
be
an
issue.
A
We
did
that
several
times
in
the
past.
So
it's
not
the
first
time
that
we
do
this
operation.
It's
just
that
because
you
have
to
deploy
a
new
controller,
redirect
the
traffic
and
then
redirect
it
back.
It
can
take
some
time,
but
otherwise
it
should
be
fine.
The
second
announcement
is
next
week.
We
will
have
an
lts
release
or
net
test
release,
so
this
is
something
that
we
have
to
pay
attention.
So
if
we
plan
any
work
on
the
release
environment,
we
should
not.
A
I
mean
we
should
be
careful
so
that
that's
it
basically,
so
don't
don't
be
too
don't
change
too
many
things
before
the
next
test
release.
That's
all
for
the
announcements
regarding
the
notes.
As
again,
those
notes
are
prepared
several
days
in
events
so
feel
free
to
just
add
any
topic
that
we
that
you
want
to
discuss
in
the
notes.
So
we
can
come
prepare
for
the
meeting,
so
the
first
one
that
I
want
to
discuss
briefly.
A
Is
I've
been
thinking
in
the
past
about
how
to
split
the
role
of
the
infrastructure
officer
to
delegate
the
rule,
so
the
community
could
take
more
responsibility
here,
and
so,
if
you
have
any
suggestions
there,
I
mean
I
would
be
really
happy
if
you
could
think
about
that.
The
way
I
would
think
is
would
have
to
to
have
a
shadow
infrastructure
officer
responsible
for
specific
area,
and
those
are
I
mean.
A
The
same
person
does
not
necessarily
have
to
work
on
everything,
so
we
could
have
let's
say
someone
more
interested
by
communities,
someone
more
interested
by
puppets
monitoring,
adapting
ci
shot,
libraries,
whatever
the
topic
is,
so
the
idea
is,
if
you
find
a
kit
repositories
or
an
area
that
interests
you
feel
free
to
yeah
feel
free
to
start
reviewing.
Pr's,
maybe
put
you
in
the
code
owner
I
mean
those
are.
A
I
would
be
really
glad
to
to
find
ways
to
to
to
delegate
a
little
bit
of
responsibilities
here
so
yeah
any
question.
A
A
So
if
something
is
not
clear,
feel
free
to
ask
and
I'll
try
to
find
the
right
person
who
can
put
the
documentation
on
git
repositories,
but
I'm
yeah
I'm
coming
I'm
coming
to
that
point
in
one
moment,
so
I'm
going
to
just
switch
to
continue
on
the
documentation
topic
and
then
we
will
continue
with
the.
A
So
I'm
just
switching
the
documentation,
so
we
stay
here
so
with
damien.
Last
week
we
started
discussing
about
how
we
can
improve
the
documentation
and
the
challenge
that
we
have
is.
We
have
different
kind
of
information
that
we
store
on
the
jenkins
e4
organization
and
we
have
different
ways
to
work
with
that.
So
the
first
is
you
have
we
have
like
this
meeting.
We
have
synchronous
communication
where
we
want
to
have
different
people
working
in
the
same
document
at
the
same
time.
A
So
that's
why
we
introduce
acme,
so
everybody
should
be
able
to
to
participate
to
take
notes,
basically
add
content
reorder
whatever,
so
everybody
is
invited
to
participate,
but
otherwise
for
specific
documentation,
it's
better
to
just
open
a
pull
request
on
the
repository
and
for
slash
documentation.
So
let
me
okay,
I'm
sharing
here.
So
this
is
the
git
repository
that
I'm
sharing.
So,
as
you
can
see,
we
we
have
a
directory
containing
kubernetes
maintenance.
A
A
We
are
taking
notes
for
the
meetings
and
we
want
to
add
more
the
services
documentation,
so
we
are
still
building
that
gauge
repository,
but
yeah
feel
free
to
feel
free
to
request
specific
information
and
then
another
element
that
was
asked
last
week
is:
what
do
we
do
with
information
that
we
don't
want
to
be
public
like,
for
instance,
run
books?
A
The
idea
here
is
just
to
to
to
document
a
specific
service,
and
inside
that
specific
page,
we
just
put
links
to
the
runebooks.
There
are
different
reasons
why
we
don't
want
to
have,
let's
say
our
rainbooks
public,
because
it
involves
either
personal
information
like
call
that
person
if
something
goes
wrong
or
do
specific
operations
that
we
want
to
keep
private
so
yeah.
That's
that's
why
we
we
we
still
have
different
kind
of
documentation
on
the
jenkins
software
organization,
again
feel
free
to
participate
to
that
project.
A
The
question
before
I
continue
no
awesome.
The
next
topic
is
instabilities,
I'm
infra.ci.
So
on
the
past
few
weeks
we
had
quite
a
lot
of
issues
with
websockets
damien.
Do
you
want
to
continue
on
that
specific
topic?
Yes,
so
I've.
C
Monitored
since
last
week
on
the
website
issue,
I
haven't
seen
on
any
on
the
logs,
so
I
might
have
missed
some.
It's
not
completely
rocket
science,
but
yeah
no
didn't
see
it
happen
again.
I've
monitored
the
throttle
status
of
the
aks
api,
the
kubernetes
api
we
use
for
the
underlying
humanities,
and
it
was
not
throttled
anymore
since
the
incident
last
plastic,
not
sure
if
it's
correlated
or
not
so
right
now,
the
relatives
that
we
don't
know,
but
it
looks
like
that-
has
been
a
bit
more
stable.
C
C
There
were
errors
that
were
taking
a
lot
of
times
to
load.
There
were
a
bunch
of
tiny
elements
that
took
a
lot
of
time
to
restart
and
it
was
restarting
the
jobs
in
loop,
sometimes
fading,
and
there
were
also
some
jobs
that
were
running
since
five
six
seven
days.
Even
so,
we
are
iterating
on
infra
ci
configuration
little
step
by
little
step.
To
be
sure,
it
should
be
better,
but
right
now
we
did
not
face
the
web
circuit
issue
anymore,
which
seems
to
go
on
the
direction
of
our
guts.
A
There
is
the
reason
thanks
damian.
There
is
another
point
that
we
change.
Last
week
we
faced
our
issues
with
the
traffic
with
get
the
jenkins
ally,
which
is
a
service
running
on
the
communities
cluster.
So
I'm
just
wondering
if
yeah,
if
the
fact
that
we
now
stop
reiterating
part
of
the
traffic
there
and
reduce
the
pressure
on
that
cluster.
C
Might
be,
the
pressure
was
not
on
the
crystal
itself,
but
then
the
request
made
to
the
kubernetes
api.
So
the
amount
of
requests
done
by
your
cattle,
client,
native
or
commonly.
A
Thanks
thanks
for
this
next
topic,
which
is
also
something
that
damien
has
been
working
on,
is
about
cleaning
the
datadog
configuration.
So
just
a
bit
of
context
here,
the
jenkins
project
is
sponsored
by
datadog
to
monitoring
a
big
part
of
the
infrastructure,
and
a
while
ago
we
started
using
terraform
to
configure
the
monitoring
checks.
A
Those
terraform
those
the
terraform
code
was
applied
from
ci
dodge
entities
and
what
damon
did
recently
was
to
first
update
the
terraform
dependency
so
that
it
was
supposed
to
move
to
version
0.13
and
also
clean
up
a
bit
of
yeah
legacy
around
that
that
project.
So
if
you
want
to
look
at
the
specific
repository,
it's
located
on
jenkins,
surfer,
slash,
datadog
and
now
the
the
that
repository
is
built.
A
Is
executed
from
infrared
ci,
we
used
to
have
a
staging
environment,
but
we
stopped
using
that
staging
environment.
The
reason
for
that
is
because,
for
some
of
the
synthetic
checks
that
we
have
on
the
prediction
account
we
had
to
request
to
increase
the
limits
so
yeah.
A
We
we
send
a
request
to
datadog
support,
to
increase
the
limits
of
the
number
of
synthetic
checks
that
we
can
have,
and
so
because
of
that,
we
cannot
use
the
traffic
code
to
deploy
the
staging
environment
anymore,
because
we
are
limited
to
three
synthetic
checks
or
something
like
that.
So
yeah,
the
work
done
by
that
by
daniel
here
was
ready
to
to
simplify
and
if
you
are
interested
by
a
specific
dashboard,
whatever
that's
the
right
place
to
go.
A
If
you
want
to
improve
the
monitoring
of
a
specific
service,
that's
also
the
right
place
to
go
still
on
the
data
dock
topic.
We
have
multiple
components,
so
we
build
our
own
data
docker
image,
so
we
have
some
custom
checks.
That's
how,
for
instance,
with
monitor
if
we
can
still
download
the
latest
changing
packages
from
the
service
kit
that
jenkins.io.
A
We
also
use
that
monitoring
to
know
if
the
release
process
is
not
is
not
stuck
so
typically.
What
happened
in
the
past
was
the
release
process,
released,
use,
maven,
release,
plugin,
to
publish
the
jenkins
war
and
for
some
reason
we
were
not
able
to
package
the
new
version,
and
so
we
had
to
manually
trigger
the
packaging
job,
and
so
when
the
same
situation
happened.
Now
again
we
just
detect.
That's
that
specific
issue.
A
Mark
I
see
you
that
you're
wondering
do
you
have
any
question
on
that
too.
Big,
no
okay
sounds
perfect,
so
yeah
custom
checks
for
the
dog,
and
otherwise
everything
is
maintained
through
terraform.
C
C
It's
our
ability
to
update
and
do
whatever
actions,
but
the
near
goal
for
end
users
and
us
is
that
we
want
to
improve
the
monitoring
to
be
sure
that
if
we
are
triggered
on
pagerduty
it's
because
something
is
really
broken,
because
currently
right
now,
it's
quite
verbal,
so
we
risk
the
risk
is
that
we
can
ignore
a
real
positive
issue
and
the
goal
is
try
also
to
automate
most
of
these
things
to
provide
automated
status
for
the
end
users.
At
any
moment,.
A
There
is
one
specific
topic
that
I
found
that
happened
multiple
time
in
the
past
was
we
update
the
terraform
code,
it's
working
and
then,
after
several
months
he
stopped
working
and
we
have
to
look
at
it
again
and
I
saw
the
same
behavior
for
some
of
the
docker
images,
and
so
we
should
have
probably
put
in
place
some
monitoring.
Let's
say
if
some
builds
are
not
passing
on
the
master
branch,
someone
should
fix
it.
I
mean
I'm
guilty
in
some
of
them.
A
I
was
just
surprised
this
afternoon
to
look
at
a
bunch
of
funny
failing
job,
even
if
we
work
on
those
previously.
That's
a
good
point.
C
A
Yeah,
but
this
is
something
to
keep
in
mind
thanks
thanks,
everybody,
the
so
the
next
topic,
which
is
cydia
jenkins,
I
mean
for
putting
that
as
well.
So
sounds
like
you
finish,
working
on
it.
Do
you
want
to
share
the
state
here.
C
The
underlying
cluster
has
a
static
capability
right
now:
three
nodes
that
are
medium
sized
nodes,
so
for
tiny
steps,
it's
okay,
so
the
next
step
will
be
to
start
moving
some
workload
hitting
the
limits
and
then
improving
the
automatic
scaling
of
the
underlying
cluster.
C
That
would
be
the
next
step,
but
it
has
been
successfully
applied
and
there
are
some
minor
configuration
changes
that
we
will
have
to
do
in
order
to
improve
switching
to
work
circuit,
et
cetera,
but
overall,
it's
working
very
well
and
really
efficiently.
So
I'm
quite
happy
with
this
all
the
jobs
I
worked
on
took
twice
or
three
less
times
they
were
building
on
virtual
machines
on
vc2
before
so.
The
performances
from
these
use
cases
were
quite
better
by
moving
to
kubernetes.
A
And
I
would
be
really
interested
to
to
work
on
that
with
you
as
soon
as
possible,
because
we
are
investigating
ways
to
reduce
the
cost
of
sea
idea,
jenkins
that
I
o.
So
if
we
can
be
more
efficient
with
that
service,
that
would
be
really
nice.
B
Sorry,
yes
before
so
I'm
assuming
for
now
that
the
experiment
is
explicitly
only
for
linux,
based
agents,
no
windows-based
agents
right.
So
we're
not
attempting
the
the
wild
card
of
windows-based
agents
and
kubernetes.
B
A
Great
thanks
the
last.
The
last
topic
that
I
want
to
highlight
is
we
transfer
a
few
teach
repositories
from
carrots,
get
it
back
on
to
the
jenkins
project,
so
feel
free
to
look
at
them.
The
first
one
is
the
uc,
it's
a
small,
but
it's
a
small
tool
that
you
can
use
to
bump
a
plug-in
version.
You
just
provide
a
plugin.txt
and
then
uc
will
automatically
updates
for
a
specific
jenkins
version.
A
We
are
using
it
at
the
moment
to
build
the
jenkins
now
the
jenkins
infra
jenkins,
docker
images,
and
it
has
been
working
very
well.
The
second
tool
that
I
mean
that
you
should
definitely
look
at
is
the
jenkins
version.
So
it's
also
a
small
binary
and
it
can.
You
can
use
it
to
know.
What's
the
latest
version,
either
the
latest
table
or
the
latest
wiki
a
weekly.
A
A
A
So
if
you
want
to
look
at
how
it's
used
jenkins,
I'm
going
to
go
here,
so
you
can
see
my
screen
jenkins
and
fra
and
it
should
be
docker,
let's
say
jenkins
lts,
so
we
have
a
specific
git
repository
for
the
lts
for
stable
and
for
the
we
need
for
the
weekly.
So
we
provide
the
plugins
that
we
want
to
that.
We
want
to
install.
A
The
way
you
remove
the
in-ear
right
so
is
the
ssh
agent
has
been
fixed.
No
yes,
so
we
can
also
specify
to
not
update
a
specific
plugin.
So
this
is
something
that
we
still
have
to
work
on
for
the
release
environments,
so
you
can
specify
to
not
update
a
specific
file
and
then,
when
you
look
at
the
jenkins
now
it's
not
here,
so
I
guess
it's
a
git
of
action.
Workflow
update.
A
Where
is
that?
Oh,
yes,
it's
using
github
action,
so
it
won't,
it
won't
be
easy
to
show.
But
basically,
if
you
go
to
the
uc
or
jenkins
version,
let's
take
jenkins
version.
You
go
for
the
latest
release.
A
We
go
for
the
latest
release
and
then
you
can
directly
download
the
binary
that
you
want
to
use
if
you're
running
on
yeah,
whatever
the
distribution.
You
are
the
architecture
and
you
are
sorry
and
and
yeah
that
that's
that's
pretty
useful.
A
And
finally,
the
third
project
is
captain
hook.
Captain
hook
is
a
web
book
proxy,
but
the
specificity
here
is
to
collect
every
web
hook.
That
should
be
sent
to
the
jenkins,
but
if,
for
some
reason
the
jenkins
is
down
captain
hook
cashed,
those
requests
to
when
champions
is
back
on
track.
Captain
hook
sent
those
requests
to
the
jenkins.
A
The
idea
is
no.
We
have
some
configuration
to
apply
to
use
it
on
a
jenkins
infrared
project,
but
because
we
restart
multiple
time
per
day.
The
jenkins
instance.
We
want
to
be
sure
that
we
connect
that
we
keep
that
we
that
window
everywhere
we
book
request
so
yeah.
That's
also
another
project
that
we
are
currently
testing.
A
We
cover
old
topic,
so
any
topic
you
want
to
briefly
talk
here
before
we
stop
the
meeting,
so
one
call
to
call
so
yeah
I
already
put
so
then
this
week.
I
already
put
the
link
to
the
next
notes.
Weekly
for
the
next
weekly
meeting
feel
free
to
add
any
topic.
You
want
to
discuss
there
and
yeah
thanks
for
your
time
and
goodbye,
see
you
on
rc.