►
From YouTube: 2022 02 08 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
This
week
there
isn't
any
weekly
expected
at
least
not
today
and
not
tomorrow.
As
far
as
I
understand,
because
there
will
be
a
security
release
on
weekly
and
lts,
I
don't
know
if
we
should
trigger
a
weekly,
tuesday
or
friday
and
on
team.
What
do
you
think
about
that?.
B
I
know
so
there
will
be
a
weekly
tomorrow
will
be
2.334,
but
it
will
be
a
security
release,
so
it's
2.33,
plus
just
the
security
upgrades
or
security
changes.
B
C
B
A
About
the
next
week
release
also,
there
will
be
a
set
of
security
release
for
plugins.
That
should
happen
15
of
february.
So
I
took
the
responsibility
to
to
say
we
will
delay
the
weekly
to
the
6th
16th
of
february
to
wednesday.
A
Great
okay,
thanks
just
to
say
not:
it's
systemd,
not
system,
v
system
v
is
the
old
in
it
or
it's
referred
to
something.
A
Okay,
so
let's
proceed
on
the
tasks
and
not
first
a
priority
about
the
two
security
releases,
so
this
week
tomorrow,
we
will
have
calls
only
remember,
don't
merge
anything
this
afternoon
or
tomorrow
until
the
security
release
is
done
at
least
nothing
that
could
have
any
impact
on
release.ca
or
ci
jenkinsairo.
Please.
A
This
morning
we
took
the
opportunity
to
update
relucia
infrasi
ci
untrusted
kernel,
plugins
everything
that
was
available
this
morning.
So
tomorrow
the
security
team
will
have
a
clean
state
to
work
with.
That
would
avoid
them
having
a
zillion
of
plugins
to
update
and
they
have
to
manually
select
most
of
the
time
they
don't
need
to,
but
yeah
at
least
we
have
a
clean
state
for
them.
A
Once
again,
the
weekly
automatic
releases
triggered
automatically
at
this
time.
It's
no
one's
fault
compared
to
last
time.
It's
because
we
had
a
short
notice
from
the
security
team
that
they
were
willing
to
have
a
core
release
tomorrow,
and
they
were
going
to
stage
it
monday.
At
least,
I
received
the
notification
really
really
early,
really
late,
so
yeah,
but
just
to
be
sure.
Thanks
survey
for
the
review,
we
disabled
the
management
of
freely
ci
on
kubernetes.
A
So
the
proposal
is
that
we
don't
put
it
back
on
automatically
managed
until
until
the
security
release
is
finished,
and
we
will
have
to
do
the
same
thing
next
week,
just
to
be
sure
there
isn't
any
unplanned
reload
of
the
configuration
on
kubernetes
that
will
enable
again
the
job.
A
A
C
We
don't
want
anyone,
updating,
plugins
or
the
image
or
anything
while
we're
writing
anything
that
could
take
it
down.
While
we're.
A
About
to
do,
however,
I've
also
had
a
smart
idea
that
could
be
complementary
to
that
which
will
be
changing
the
pipeline
for
the
releases
to
check
for
a
lock
file
or
not.
So
that
will
mean
if
anyone
from
infra
team
or
security
team
commits
the
log
file
on
the
repository
when
the
automatic
weekly
trigger
starts.
If
it
see
the
log
file,
it
will
stop
immediately
with
a
message
saying
I
got
a
log
file.
B
A
Will
be
full
as
code
only
restricted
to
the
release
pipeline,
so
releases
dot,
ci
jenkins,
dot
io
could
still
continue,
working
and
being
updated
without
any
risk
right.
So
that
will
be
a
complementary
process,
but
we
still
need
job
dsl
contribution,
because
disabling
jobs
is
something
we
need
on
numerous
places.
A
I've
put
all
the
links
and
danielle
yesterday
did
the
part
of
the
staged
the
release
part,
not
the
packaging
part.
Only
there
is
generating
the
war
and
signing
it
for
the
weekly.
It
worked
perfectly.
I
mean
last
week,
last
weekly
last
week
worked
perfectly.
That
was
the
same
code,
so
that's
fine
about
lts
still
the
same
issue.
Each
time.
A
A
C
A
B
B
A
Who
is
going
to
do
that
part
that
staging
release?
Is
it
us
or
security
team.
B
C
B
A
B
A
A
A
Okay,
just
a
word
for
next
week.
That
will
happen
before
our
team
meeting.
That's
why
you
wanted
to
mention
it.
Trusted
will
be
needed
at
all
costs,
because
it's
only
plugins
release
dot,
ci
shouldn't.
However,
let's
keep
it
safe
and
ci
jenkins
io,
of
course,
because
they
will
need
to
update
the
plugins.
If
we
have
some,
I
haven't
seen
the
list
of
plugin
impacted
by
the
cvs
stuff.
So
let's
assume
cie
the
jenkins
that
I
will
be,
especially
since
vadek
asked
for
the
status
jenkins.
I.
A
B
B
No,
no,
no,
just
for
it's
it's
a
usually
it's
a
our
history
says
it's
about
a.
It
can
be
anywhere
from
a
15
minute
to
a
45
minute,
downtime
except
stefan.
If,
since
steph
and
I
are
going
to
be
cherry
picking
on
on
a
branch,
why
don't
we
also
take
that
one?
Because
that
way,
he
and
I
can
do
a.
How
do
you
do
a
submission
to
status.
A
A
A
It
seems
that
the
readme
that
I
originally
created
for
aws
terraform
management
needs
some
a
bit
of
revamp
or
update,
at
least
on
the
file
structure.
We
add
good
exchanges
about
how
to
build
a
stronger
shard
pipeline
library
for
terraform
management
and
testing
and
stuff,
based
on
the
issue
that
they
had
locally.
Due
to
let's
say
it's
a
the
oath
of
that
terraform
stuff,
I
understand
irving.
Can
you
confirm
that
you
are
the
ci
steps,
meaning
making
the
ci
jobs
working
it's
created,
but
you
have
to
make
it
work,
so
it
managed
digital
ocean
cluster.
C
C
C
It
should
work
in
jks,
but
I
mean
it's
easier
if
you
just
avoid
this
and
just
just
just
use
like
string
variables,
I'm
not
sure
if
I'm
not
sure
exactly
what's
in
this
file,
but
normally,
if
you
just
do
something
like
a
like
in
aws
or
azure,
you
just
do
tf
arm
id
equals
and
then
and
then
have
the
key
as
like
an
environment
variable
so
like
with
the
as
your
azure
terror
from
provider.
You
can
provide
files
or
you
can
just
provide
environment
variables,
and
it's
awesome.
C
Is
this
for
the
like
the
s3
bucket
or
something
else
because
from
looking
at
the
digitization
dock,
so
it's
very
s3.
D
E
Yeah
I
can.
I
think
I
can.
C
C
A
Yep,
okay,
also,
another
clue
is
that
since
the
content
of
the
backend
config
for
the
actual
terraform
and
the
are
almost
the
same,
there
is
only
one
change
one
key.
The
idea
would
have
been
to
reuse
the
existing
credential
and
then
only
define
the
key
on
the
backend.tf
of
digitalocean,
because
it's
not
a
sensitive
data
yeah
only.
C
A
C
D
A
D
Yeah,
it
got
it's,
it's
the
content
of
backend
config
in
the
purposes.
C
A
A
It
can
use,
read
the
content
of
a
file
and
base60
for
it
or
a
string,
or
it
will
unreference
a
variable.
So
there
is
something
weird
yeah.
Sorry
we
backed
we
sidetracked
just
in
case
it
was
a
well-known
behavior.
I
don't
know
so
we
have
something
weird
and
we
need
to
change
to
fix
that,
because
it's
slowing
down.
A
A
For
sure
but
yeah
we
can
find
it,
but
outside
that
credential
issue,
almost
there
so.
C
A
Job
rv
next
topic:
unless
you
have
a
question
or
something
else,.
A
So
update
cli
so
great
work,
stefan
on
adding
more
update,
cli
tracking
on
more
dependencies.
We
have
ashikop
tools
which
has
a
bigger
which
has
been
updated
recently
and
the
most
interesting
part
is
kubernetes.
Management
is
now
tracking
the
mei
for
the
ec2
agents
that
we
recently
added
on
release.ci
and
infra.ca.
A
That
should
allow
us
to
build
using
docker
engine
on
virtual
machines
and
that
will
allow
us
to
use
the
same
labels
for
both
ci
jenkins
io
and
our
kubernetes
jenkins
controller.
So
in
the
future
we
should
be
able
to
shrink
the
pipelines
to
use
only
jenkins
file
and
migrate
trusted
to
release
that
will
open
this
road.
So
thanks
a
lot
for
that
worker,
stefan
you're
welcome
private
access
cluster.
A
I
haven't
done
anything
I
was
in
day
off,
but
that's
my
top
priority
for
this
week,
focusing
on
the
groovy
pipeline
library
for
terraform
management
and
then
reinitialize
the
azure
repository
like
the
digital
ocean
data
is
working
on,
so
we
can
create
a
private
cluster
and
move
at
least
in
frasier
and
really
cia
with
them
behind
the
vpn.
A
A
There
is
an
issue
to
be
created.
Thanks
tim,
that's
a
good
point
that
you
underline
that's
worth
it
to
communication,
at
least
the
blog
post
and
the
twitter
before
really
starting
to
decommission
and
otherwise
underlined.
Also,
we
might
want
to
search
for
the
references
of
mirrors
that
jenkins
dot
io
inside
our
own
code
base
in
jenkins,
afro,
at
least
test
rns
and
the
pipeline
libraries
and
change
them
to
get
jenkins
sayo.
So
at
least
they
will
use
the
correct
service.
D
A
A
Another
word
on
rating
the
jenkins.you:
we
have
jeremy
playout
from
cloudbees
that
started
to
work
on
to
take
again
the
work
that
gave
in
and
maybe
others
started.
One
year
ago
at
least
the
goal
is
to
migrate
the
service
rating
jenkins
io
from
the
tiny
virtual
machine
on
amazon,
while
it's
running
today
into
kubernetes,
so
it
took
the
work
that
gavin
pointed
at
us
to
have
a
helm
chart
that
he
was
able
to
run
locally.
There
is
a
pull
request
that
opened
that
we
have
to
review.
A
The
next
step
will
be
to
prepare
the
installation
of
the
term
chart
on
our
pod
public
cluster
attention
point
for
the
infra
people
rating
need
a
database.
It's
a
postgresql
database.
I
don't
remember
where
it
hosted.
I
assume
it's
on
aws,
as
for
today,
yes
need
to
be
checked.
Okay,
yes,
so
we
might
want
to
create
a
new
postgresql
database
inside
azure
at
least
manually,
and
I
will
import
it
on
terraform
later
when
it
will
work,
but
we
need
a
postgresql
and
there
will
be
a
migration
phase.
A
A
So
thank
jeremy.
Jeremy
is
out
so
he
will
continue.
It's
not
a
priority
topic,
but
on
background,
that's
interesting,
an
external
contributor
doing
that
for
us,
that's
really
nice.
A
It's
four,
so
I
propose,
unless
you
want
to
bring
another
topic,
that
we
delay
the
other
topics
to
next
week.
Is
there
any
prior
topic
that
we
forgot
about,
or
do
you
want
to
speak
about
right
now
today,.