►
From YouTube: 2021 11 23 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
A
The
reason
is
because,
during
the
we
did
a
an
update
of
a
bunch
of
our
docker
images,
including
docker
packaging
and
the
release,
the
release
agent
environment
is
using
always
the
latest
version,
so
using
the
latest.
One
of
the
side
effects
of
our
changes
was
to
follow
good
practices
on
the
docker
file,
just
to
define
that
image,
and
some
dependencies
like
gpg
were
not
explicit.
A
They
are
not
defined
explicitly
on
the
dockerfile,
they
are
present
on
the
image
or
they
used
to
be
because
they
were
implicit
dependencies
of
other
packages.
So
we
have
to
release
a
new
version.
With
this
element
we
are
currently
checking.
It
sounds
like
we
need
to
add
git
and
open
ssl,
at
least
as
explicit
dependencies.
Just
to
be
sure.
The
reason
is
because
the
release
shell
script
is
using
explicitly
these
commands
there
might
be
other,
but
that
we
are.
We
have
almost
covered
all
the
script.
A
B
A
Just
one
thing
it
sounds
like
we
have
a
tag
from
the
7th
of
october
on
the
github
repository,
but
I
propose
we
don't
spend
much
time
and
we
fix
the
issue
this.
This
is
a
weekly
release.
It
would
have
been
lts.
I
would
have
proposed
to
find
a
version
for
last
week,
but
I
propose
we
go
ahead.
Is
it
okay
for
everyone.
A
Okay,
so
let's
wait
after
that
meeting
and
continue
the
effort
next
point
jenkins,
io
outage
so
last
week
we
had
an
outage
on
jenkins,
io
and
all
the
documentation
blog
posts,
so
everything
under
that
website,
so
we
still
have
a
postmortem
to
write
down
the
root
cause.
Was
the
engine
exam
charts
that
we
that
we
upgraded
in
production
and
even
though
it
was
a
patch
version,
it
has
a
side
effect
due
to
security
cv
fixed
in
engine,
and
we
add
to
the
consequence,
was
once
upgraded.
A
The
cv
fixed
on
the
term
chart
is
some
code
block
on
nginx
are
forbidden
on
that
version
when
you
are
using
some
characters
that
correspond
to
configuration
item
in
nginx
that
could
be
used
to
extract
secret
or
do
a
wrong
thing
like
calling
a
lua
script
or
a
simple.
If
block
and
alas,
we
had
a
hiv
block
on
the
annotation,
so
thanks
server
for
the
work
on
that
part,
you
were
able
to
remove
or
move
away
at
the
image
level
for
jenkins.
A
B
A
A
We
have
two
weeks
where
people
could
comment
propose
edits,
ask
questions
and
in
two
weeks,
without
any
comments
or
if
everything
is
solved,
we
will
froze
that
document
into
the
jenkinson
foreign
documentation,
repository
in
the
markdown
format
and
updating
status
jenkins
sayo.
There
is
an
incident
in
the
history
of
incidents,
so
we
will
have
the
link
to
the
postmortem
and
an
incident
for
later
is:
does
it
seem
good
to
you?
That
means
collaboration
during
two
weeks,
question
comments
and
then,
if
everything
is
okay,
then
we
can
move
our
move
away.
A
That
should
be
upgraded.
We
mentioned
that
last
week.
So
since
last
meeting
we
have
done
everything
required
to
help
kk,
so
he
is
able
to
take
over
the
name,
and
now
he
should
have
generated
a
new
certificate
or
he
should
be
able
to.
We
haven't
heard
from
kk
yet,
and
I
was
planning
to
send
a
reminder
today
and
it
sounds
like
g
frog
rostidus
and
ask
kk
what's
the
status,
my
proposal
is
to
wait
at
least
tomorrow.
A
If
kk
doesn't
answer
to
g
frog,
who
will
send
in
send
him
an
email
hey
there
if
you
still
want
to
do
it
or
we
can
take
over
again
and
do
it
by
yourself
and
exchange
with
you
from
if
it's
too
much
for
him.
C
C
Previously
it
was
already
at
one
second,
as
I
could
find
in
some
articles
from
20
2018,
but
see
this
requirement
wasn't
respected.
It
was
a
bug
in
kubernetes
in
community.
So
now
this
one
second
default
timeout
is
unfortunate,
so
we'll
have
to
meet
our
application
to
see
if
some
of
them
will
need
this
parameter
specified
with
an
increased
timeout,
especially
jenkins,
but
we
don't
know
yet
we'll
have
to
test.
C
But
apart
from
that,
I've,
I've
not
seen
anything
specific
or
problematic
for
the
upgrade.
So
I
think
we
could
maybe
set
a
date
for
this
upgrade
this
week
or
next
week.
If
it's
okay
for
you.
B
So,
and
if
if
thursday
or
friday
are
viable
for
you,
they
are
certainly
low
activity
days
in
the
in
the
us,
because
those
are
bank
holidays.
So.
A
So
if
it's
okay,
then
you
will
have
to
send
an
email
on
both
mailing
lists
to
let
people
now
and
open
a
pull
request
to
prepare
the
operation
on
status
chain
kim
scio
and
additionally,
a
fourth
point
will
be
telling
telling
that
on
the
irc
and
every
instant
messaging
channel,
that
we
could
use
for
infrastructure
or
communicating.
B
Those
are
great
choices.
Oh
community.jenkins.io
might
also
be
a
good
place
to
to
note
it.
If
you
didn't
mention
that
already
it's
it's,
it
doesn't
do
any
harm
to
say
it
there
and
it's
another
another
forum
where
someone
might
see
it
every
are
you
expecting?
Are
you
expecting
downtime,
or
is
this
one
that
I
I
don't
recall
kubernetes
upgrades?
Do
they
typically
take
a
downtime
or
is
it
rather
it's
a
rolling
thing
where
a
piecewise
upgrade
usually
works?
B
A
A
So
we
we
should
expect
a
cut.
Most
of
the
ldap
usage
is
like
jira
or
ci.
Gentin
sayo
have
some
caching.
However,
we
should
say
by
default,
it
will
be.
We
will
have
an
outage
of
unexpected.
Let's
say
the
service
will
be
done
for
a
few
minutes
during
the
restart
time.
Great
okay,
thank
you.
B
B
D
A
A
So
then
the
goal
will
be
to
use
that
pipeline
library
for
our
current
terraform,
automated
job,
meaning
aws
and
datadog.
Both
of
them
will
need
some
slight
changes.
Datadog
is
something
created
by
olivier
and
tyler
with
terraform
three
years
ago,
and
it's
still
working
which,
by
the
way
is
really
cool
and
aws,
is
the
new
one
that
garrett
and
I
created
this
year.
So
the
goal
will
be
to
to
have
the
same
way
of
manipulating
both
because
they
have
slight
differences.
B
So
there
is,
there
is
interest
in
the
open
source
community
around
the
us
federal
government
in
terraform
automation
in
pipeline.
So
what
you're
doing
I
may
come
begging
you
a
month
or
two
from
now
to
help
and
coach
on
hey.
Could
this
be
may
used
a
little
more
broadly,
even
certainly
you'll
do
it
for
our
needs,
but
we
may
come
beg
for
your
skills
or
your
knowledge
to
how
could
we
help
the
the
open
source
piece
of
the
us
federal
government
if
they
want
to
use
it.
A
C
A
There
is
a
free
plan
that
should
suffice
in
our
case,
and
that
could
be
interesting
also
for
open
source
code.
They
have
programs
for
open
source.
If
we
need
more,
I
am
herve.
You
told
me
that
one
of
the
limit
of
the
feature
is
the
amount
of
users
available
to
access
that
so
meaning
the
admin
of
the
infrastructure
that
should
suffice
for
us
but
yeah.
A
Maybe
we
need
a
bit
more,
so
that
could
also
be
interested
to
have
in
mind
if
it's,
okay,
I
propose
that
we
start
keeping
our
items,
so
we
manage
everything
from
scratch,
with
the
risk
of
losing
our
state,
and
then
we
can
think
about
checking
on
ashikorp
services,
because
that
will
help
maybe
less
code
everything.
But
since
we
already
have
some
code
running,
the
goal
is
to
go
step
by
step.
A
A
Next
topic,
ci
jenkins,
io,
so
maven,
3.8.4
and
gitwood.34
are
generally
available.
They
are
almost
available
on
ci
jenkins
io.
We
are
having
issues
on
building
the
the
virtual
machine
template
only
the
azure
with
windows.
A
A
A
I
I
guess
there
is
something
to
be
checked
there.
We
might
have
been
too
quick
on
using
that
way
of
installing
it,
but
I
mean
it's
not
breaking
the
use
cases
on
cigo
because
we
have
a
vm
template
but
yeah
that
was
to
mention.
So
in
that
case
the
idea
is
to
provide
this
version
as
soon
as
possible
to
see
how
jenkins
is
and
send
an
email
to
the
jenkins
developer
list.
Once
it's
been
done,
does
it
sound
good
for
you.
A
Cool
one
note:
the
docker,
the
campaign
that
harvey-
and
I
did
on,
trying
to
check
all
the
docker
images
built
inside
infrastructure
for
our
own
usages
and
taking
care
of
the
tracking
dependencies
of
these
images,
depending
on
parent
image
or
binary
like
the
black
maven,
the
gates
that
we
don't
know
it.
The
goal
of
that
campaign
was
to
check
that
we
were
able
to
use
the
latest
update,
cli
manifest
version,
and
we
have
the
five
repositories
that
have
been
listed
in
the
meeting
notes
that
are
still
to
be
checked
or
updated.
A
A
One
last
thing:
just
about
the
costs,
so
it
sounds
like
we
will
be
able
to
eat
to
not
eat
the
10k
limit
on
aws
right
now,
the
we
have
used
6k
and
we
should
be
around
9.2
k
this
month,
the
goal
as
you
remember,
we
still
need
to
be
under
the
bar
of
8k
per
month,
so
there
are
still
some
work
to
do
on
that
part
just
to
mention,
because
everything
was
on
previous
meeting
there
and
we
are
working
on
on
this
element,
then,
as
we
for
remember,
the
goal
is
to
move
pkg
jenkins
io
to
another
cloud,
because
it's
3k
of
bandwidth,
so
we
have
to
check
the
cost
on
oracle
cloud
and
azure
just
to
have
a
comparison
or
a
backup.
B
So,
unfortunately,
the
they
had
a
hardware
crash
on
the
system
that
we
use
to
run
our
voting
system
or
that
we
we
rely
on
to
do
the
voting.
We
don't
actually
run
it.
They
do
cornell
university
in
upstate,
new
york,
hosts
that
service
and
has
hosted
it
for
years
for
us.
Unfortunately,
they
had
a
hardware
failure.
B
So
my
hope
is
that
it
will
come
online.
I
don't
see
any
way
for
us
to
replace
the
service,
because
it's
got
the
40
plus
votes
that
have
already
been
recorded,
so
we're
hoping
that
they've
got
good
backups,
like
professor
myers
indicated
they
have
backups
and
that
they're
able
to
restore
the
hardware
and
that
the
holiday
weekend
in
the
u.s
doesn't
and
it
being
a
university
holidays,
tend
to
be
a
little
longer
in
the
u.s
than
typical
business
holidays.
B
B
Well,
if
I'll
check
with
professor
myers
I'll
tweet
the
professor
myers,
to
see
what,
if
there's
any
progress
today,
I
doubt
that
that
would
help
because
we'd
have
to
have
access
to
their
backups
we'd
have
to
have
access.
You
know
it's.
The
data
is
much
much
more
valuable
to
us
than
the
service
itself
right.
The
voting
data
for
this
running
election
is
intentionally
secret
and
is
intentionally
you
know
private,
and
we
don't
really
want
it
to
not
be
private.
We
like
that,
it's
private,
that's
intentional
good
point.