►
From YouTube: 2022 04 05 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
A
A
B
Docker
image
is
built
and
confirmed.
That's
part
of
the
checklist.
A
B
A
I
accented,
I
accidentally
deployed
a
change
to
release
ei
that
happened
during
the
during
the
release,
so
I
had
to
trigger
it
manually
on
myself.
Sorry
for
that
this
week
it
happened,
so
we
still
have
some
tasks
that
will
allow
such
issue
issue
to
happen
in
the
future.
A
A
A
A
First,
we
had
an
incident
yesterday
about
artifactory
being
slow
for
a
few
hours.
So
that's
the
same
incident
regularly.
We
start
seeing
alerts
on
datadog
and
pedja
duty
and
right.
At
the
same
time,
our
human
monitoring
eg,
our
users
start
complaining
about
builds
being
slow
on
the
machine
or
on
cigarencia.
A
A
We
also
opened
an
incident.
I
followed
up
except
the
usual
automatic
message.
We
never
heard
from
them
each
time
we
never
heard
from
them,
except
we
don't
accept
hello
and
okay.
Is
it
closed,
not
sure
what
to
do
about
that?
We
don't
have
anything
right
now,
but
it
starts
to
be
more
and
more
frequent.
A
A
There
is
an
issue
for
that
that
has
been
added
to
the
nodes
in
the
help
desk
issue:
1136,
no
sorry
monitor,
artifactory
or
all
right.
No,
so.
A
Also,
okay,
so
I've
added
on
the
the
list
at
the
bottom
of
the
notes.
You
have
a
new
section
that
will
be
the
set
of
issues
that
we
will
set
to
the
next
milestone
and
artifactory
proxy
caching
will
be
one
of
these,
so
artifactory
proxy
caching
is
about
spawning
an
nginx
server
that
will
serve
as
a
proxy
as
explicit
proxy.
A
So
any
subsequent
build
will
be,
will
have
its
file
served
from
the
local
nginx.
That's
something
that
used
to
be
present
on
the
platform,
so
we
should
be
able
to
build
from
the
existing
tooling.
It
was
already
caching
only
the
release,
artifacts
and
only
maven
url,
which
should
be
a
good
target
to
get
started
on.
There
has
been
discussion
about
using
snapshots,
etc.
A
Let's
start
with
the
release
and
let's
see
how
it
behave
and
then
let's
iterate,
the
main
challenge
we
will
have
to
face
compared
to
three
years
ago
is
that
we
have
the
builds
of
sea.
Ige
and
quincy
can
happen
on
aws,
azure
or
digital
ocean,
and
they
can
happen
on
virtual
machines
or
kubernetes
agents.
So
we
will
have
to
find
a
way
to
correctly
balance
the
caching
should
we
start
with
the
first
instance
that
might
add
network
latency.
A
A
A
The
two
things
we
can
do,
though,
are
first
ensuring
that
the
data
dog
monitor
is
published,
so
it
should
be
available
for
everyone
on
status,
jenkins,
sayo
by
default,
and,
secondly,
ensuring
that
everyone
on
the
team
will
will
be
on
page
duty.
That
will
be
a
topic
for
middle
of
may
not
for
now,
unless
you
want
to
get
started
on
that,
but
I
propose
we
delayed
that
second
point
to
may.
If
that's
okay
for
everyone.
A
Okay,
next
topic,
we
fix
the
digital
ocean,
terraform
build
that
was
failing
since
a
few
days,
thanks
rv
for
that
and
already
discovered
that
kubernetes
1.20
is
not
available
anymore.
On
digital
ocean,
the
older
version
is
1.21,
so
that's
erased
the
topic
of.
Maybe
we
should
start
planning
upgrading
our
clusters
on
1.21.
A
A
A
A
Okay,
there
were
so
the
disk
space
on
the
virtual
machine
hosting
the
service
sensors
census.jenkins,
dot
io,
which
retrieve
metrics
and
send
them
to
the
jenkins
report
system
was
triggering
alert.
It
was
almost
full,
so
we,
the
team,
increased
disk
space
on
both
the
system
volume
and
the
data
volume
is
the.
I
am
understanding
that
correctly
stefano
nrv,
yes,.
D
A
A
A
A
nuancer
jenkins
job
has
been
introduced
to
allow
us
to
define
using
configuration
as
code,
so
we
to
define
credential
and
jobs.
So
we
write
a
bunch
of
yaml
and
we
use
environment
variables
that
are
passed
like
the
usual
kubernetes
and
jenkins
configures
code,
and
that
generates
job
structures.
So
that's
the
first
step
and
that
chart
is
only
let's
say
sized
for
our
usages.
A
A
A
So
thanks
for
everyone
for
taking
all
of
this
work
in
progress,
so
we
had.
We
currently
have
10
issues
that
are
currently
being
worked
on,
or
that
should
have
been
the
two
major
one,
so
I'm
taking
them
on
the
order.
We
have
rating
migrating
rating
jenkins
io
to
azure
so
status.
A
A
There
is
a
name
chart
which
is
installed
in
the
prod
publicates
that
hosts
deployment
and
service,
and
that
is
able
to
connect
to
that
database.
So
the
next
two
tasks
are
now
defining
an
ingress
that
might
not
be
enabled
now,
because
the
current
dns
points
at
the
old
virtual
machine
but
defining
the
ingress,
is
required
and
importing
the
first
time
the
data
from
the
actual
database
on
aws.
So
you
can
see
the
application
working
on
real
life,
and
once
these
two
tasks
are
finished,
then
we
can
plan
the
migration.
A
Yes,
okay,
so
is
it
okay
to
continue
working
on
that
issue
for
the
next
for
the
next
iteration?
A
A
A
I'm
currently,
I
started
a
run
books
that
should
be
published
tomorrow.
I
expect
that
explain
the
fact
that
we
have
docker
herb
organization
where
we
publish
images
and
this
organization
has
associated
users
and
owners
of
members,
and
we
are
limited
because
we
are
not
part
of
the
open
source
program
to
free
users
per
organization,
which
means
most
of
the
time
we
should.
We
are
not
able
to
correctly
let
everyone
access
and
manage
it
as
for
today.
So
the
pattern
I
propose
is
for
each
of
these
organizations.
A
This
account
will
have
an
api
token
to
connect
that
we
can
rotate
and
it's
only
member,
so
it
can
only
read
and
write
the
images.
It
cannot
delete
images
and
it
cannot
change
the
ownerships
and
the
settings
of
the
organization
to
damage
control
ifs.
If
one
of
our
instances
is
is
cooked,
everyone
on
the
team
will
have
access
to
that
technical
access
through
the
subs
encrypted
passwords.
A
Then
the
two
others
user
are
owner,
so
they
should
be
humans
with
a
2fa
password
authentication
on
the
docker,
either
on
their
personal
account
or
the
account
specified.
Since
it's
only
two.
The
proposal
is
that
one
is
the
current
jenkins
infra
officer.
So
for
now
it's
me
that
will
be
the
next
office
and
I
will
change
the
seat
in
the
future
and
we
define
a
fallback
if
the
jenkins
officer
is
in
holiday.
He's
gone
is
whatever
we
need
to
have
someone
else
able
to
to
get
it
so
for
now
on
jenkins
forever.
A
A
So
to
do
on
that
area,
I
need
to
write
down
the
run
book,
so
I
propose
that
we
delay
that
issue.
A
D
And
and
you
you
maintain
that
spreading
access,
even
if
you
got
the
open
source
program
from
docker.
A
C
A
A
A
A
So
the
reality
is
that
we
have
to
proceed.
We
could
try
to
contact
mail
gun
at
the
same
time,
but
we
still
need
to
ask
in
parallel
linux
foundation
to
start
the
web
server
for
us
yeah.
So.
A
C
A
A
B
A
A
A
A
Git
for
windows
long
path,
so
I
understand
that
the
in
short
term,
the
issue
from
our
user
is
closed.
So
the
issue
should
be
closed
because
the
next
step
are
long
term
that
will
be
building
our
own
windows
docker
image
and
setting
up
the
the
parameter.
Is
that
correct
or
there
or
did
I
miss
something?
A
A
What
are
the
other
topics?
Infra
costs,
so
you
were
successful.
A
D
A
A
Yes,
yes,
okay!
So
let's
move
it
to
the
next
milestone,
monitor
builds
on
our
private
instances,
so
I
think
there
was
okay
items,
so
the
mark
you
propose
to
use
rss
like
you
are
doing
on
your
own
and
danielle
answered.
I
missed
that
answer.
B
Right
and
daniel's
answer
guides
guides
what
we
should
do
he's
right.
I
thought
of
replicating
rss.
He
said
hey,
we
really
don't
need
anything
that
complicated
a
single
job
running
on
that
trusted.ci.
That
then
reports
outward
to
some
other
location,
whether
that's
the
status.jenkins.I
or
wherever
is
enough,
and
so
so
I
think
it's
he's
right.
B
B
C
A
Okay,
so
that
means
thinking
about
whatever
language
scripts
that
will
run
as
a
jenkins
job
that
will
generate
whatever
reason
yaml
takes
the
report
published
on
azure
buckets
and
then
the
next
step
is
adding
the
datadog
monitoring,
eventually
link
to
pagerduty.
That
will
looked
at
the
freshness
of
this
one.
A
A
A
A
Yes,
if
you're
okay,
are
they
both
you,
and
I
will
monitor
that
issue
and
answer
to
tim.
So
so
we
shared
the
workload
on
that
one,
but
that
should
be
a
must
there,
thanks
for
taking
care.
B
C
A
A
A
C
D
C
A
A
C
A
The
later
one,
it's
just
that
when
we
reach
the
la
the
later
state,
it
means
it.
We
won't
have
time
or
it's
not
as
important
as
the
current
one.
Well,
the
next
or
the
upcoming
for
next
week
or
the
one
we
need
to
delay.
I
propose
we
start,
but
we
can
meet
my
new
ideas,
your
idea,
because
that
might
be
needed.
Let's
try
it
with
the
next
this
week
and
see
you
with
bf,
if
it's
okay
for
you,
yes,
okay,
upgrade
to
kubernetes
1.21,
who
is
motivated
to
start
working
on
that.
A
A
Okay,
so
we
can
think
on
the
next
step.
I
think
the
first
step
can
be
done
totally
by
stefan
and
there
they
can
just
ping
you,
but
that
one
is
quite
easy
and
then
the
rest.
I
will
let
you
both
of
you
work
on
that.