►
From YouTube: 2023 09 12 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
B
A
Let's
get
started
with
the
usual
announcements.
First
of
all,
the
Jenkins
weekly
2.4.
No,
it's
free
one
is
released,
so
the
packages
Docker
image
or
out
so
last
release
elements
as
usual
will
be
done
by
a
third
documentation,
Sig,
mostly
Kevin
and
Mark,
a
bit
later
to
be
done
later
today.
A
That
means
the
Jenkins
is
ready
to
deliver
that
new
version
to
infra
CI
and
Wiki
CA,
mainly
Stefan
mer.
You
are
ready
to
go.
Usually
it's
Wednesday
morning
on
the
European
Time
Zone,
but
yeah
you
have
to
go.
You
can
proceed.
A
That's
all
for
the
weekly
release.
That's
the
first
release
without
a
smearing,
the
Apache
Central
Maven
repository.
So
that
means
that's
really
going
on
the
right
direction.
Since
we
remove
them,
we
didn't
have
any
major
thing.
We
only
released
plugins.
So
next
step
will
be
your
LTS
release.
That
should
go
fine
and
security.
Plugin
release.
A
A
C
A
Yep
and
I'm
calendar
so
upcoming
calendar.
We
should
expect
the
version
2.4
32
of
Jenkins
next
week.
It
will
be
in
September,
19th.
A
D
26
426,
maybe
no
not
27,.
A
A
A
A
Nope?
Okay,
so
we
had
Jenkins
plugin
security
advisory
last
week
last
Wednesday
during
our
past
Milestone,
which
went
very
well.
There
wasn't
any
plugin
that
we
are
using
except
job
configuration
history
on
one
of
our
private
controllers,
but
that's
not
a
concern
that
has
been
updated,
so
nothing
to
say
about
the
release.
The
security
releases
last
elements.
Next
major
events,
devops
world
devops
world,
happened
in
New
York
this
week.
A
A
D
To
interrupt,
there
will
be
a
session
after
each
day
of
conference,
which
is
called.
Let's
talk
about
Jenkins,
so
it's
not
ask
me
anything.
It's
just
just
talk
about
Jenkins
and
one
Community
member
will
be
there
to
discuss
Jenkins
with
all
the
participants.
A
I
believe
the
first
time
has
been
confirmed
to
happen.
Yes,.
A
Okay,
that's
all
for
the
coming
major
events
so
before
we
jump
on
the
task,
the
infrastructure
task.
It's
for
you,
it's
your
turn.
So
can
you
explain
us
your
requirements
under
this
recording
I
will
take
notes.
If
you
need
me,
I
can
lead
you
and
let
you
share
your
screen
or
you
can
guide
me
on
that
screenshot.
A
C
B
C
B
Right
now
we
are
using
GitHub
actions
for
uploading,
Docker
images
and
my
personal
account
for
hosting
the
images
which
which
is
not,
which
should
not
not
be
tested
by
users.
So
we
need
official
Jenkins
called
in
Docker
hub
for
images
and
for
testing
the
images
and,
if
they're,
working
or
not
we'll
need
a
two
shift
from
GitHub
actions
to
Jenkins
CA
foreign.
A
Because
so
today
you
are,
you
are
already
using
GitHub
registry
to
store
the
docker
image.
Is
my
understanding,
correct.
A
I
was
speaking
about
G
ashcr.io,
which
is
a
container
image
registry
like
the
docker
Hub.
Can
that
can
be
used
publicly
or
privately
like
Docker
Hub,
but
it's
inside
GitHub,
which
has
the
advantage
to
if
you
use
GitHub
action,
you
immediately
can
start
working
on
building
the
GitHub,
the
the
image
on
GitHub
action
and
then
immediately
store
it
and
distribute
it
through
that
registry,
as
a
first
step,
of
course,.
B
A
B
A
I
I
believe
it
will
be
safer
for
you
and
for
the
the
projects
to
start
with
jiachier.io.
The
reason
is
that
anyone
was
the
maintainer
permission
on
your
GitHub
repository
can
also
deploy
an
image
based
on
the
build
from
GitHub
action,
so
not
only
it
will
be
safer
as
a
first
step
again,
it's
a
first
step,
I'm,
not
saying
we
don't
have
to
move
to
Jenkins
something
but
right
now
it's
the
first
step
for
you,
because
that
will
allow
you
to
use
a
Docker
image
that
can
be
shared
with
others.
A
B
A
So
now
about
the
official
Docker
hub
organization
that
are
storing
images
for
the
Jenkins
project,
we
have
two
main
organizations.
Today
we
have
Jenkins.
For
instance,
you
have
the
official
Jenkins
controller
image,
which
is,
for
instance,
that's
tag,
that's
the
Jenkins
organization
and
Jenkins
infra,
but
Jenkins.
Sorry,
yes,
so
that
organization
asked
some
images,
such
as
say
this
one
for
instance.
These
are
two
examples.
Each
organization
or
map
are
mapped
to
a
corresponding
GitHub
organization.
A
Mapped
one
GitHub
organization
we
have
Jenkins
CI
for
the
first
and
Jenkins
Dash
infra
I
will
add
the
link
on
the
Note
4
richer
notes
later.
So
what
is
the
difference
between
those
two
images?
And
how
do
we
decides
when
the
artifacts
that
we
produce
are
consumed
directly
by
Jenkins
users
such
as
the
official
Jenkins
image
official
for
agents,
controller,
a
plug-in
HPI
file?
A
A
That
image
doesn't
exist
on
search
for
it.
It's
only
who
hears
something
else,
but
that's
the
idea
that
website
is
consumed
by
Jenkins
and
user,
but
that
the
service
and
itself
and
not
the
artifact,
we
don't
have
the
need
to
produce
a
to
share
or
to
provide
to
the
community
the
official
image.
We
are
an
open
project,
so
the
source
and
image
are
available
to
everyone
if
they
want
to
contribute
if
the
community
need
to
take
take
it
over.
A
A
Thanks
so
that
mean
now,
we
have
to
decide
what
will
be
the
destination
of
the
images
from
the
gsoc
project
for
ashutosh.
A
A
Okay,
so
that
means
that
anyone
going
on
Jenkins
IO
will
have
a
tutorial,
and
so
they
will
follow
the
tutorial
and
we
expect
images
in
the
name
Jenkins
something
column,
something
to
be
present
there
is
that
is
my
understanding,
correct
and
is
that
our
session
looks
good
for
you.
B
A
Okay,
so
that
means
we
want.
So
that's
the
first
step
for
you,
you
you,
we
will
need
an
exhaustive
list
of
the
images
you
want.
So
the
tags
we
don't
care
about.
The
tags
I
mean
that
whether
we
have
a
1.0
latest,
whatever
it's
a
trap,
we
don't
want
the
latest
tag
you
should.
We
should
not
produce
any
later
stack.
We
should
only
produce
version
artifacts,
but
we
need
an
exhaustive
list.
A
So
I
guess
we
will
have
something
like
Jenkins
I,
don't
know
tutorial
controller,
whatever
the
that's
the
kind
of
information
that
we
need
an
exhaustive
list,
because
we
will
need
to
then
check
with
the
person,
the
administrator
where
we
are
administrating
that
part
to
to
create
the
repositories,
a
low
permission
and
start
the
process
for
deploying
these
artifacts.
A
B
A
B
A
D
A
A
We
cannot
just
have
the
question
here
so
here
it's
more
brainstorming
with
me
giving
tips,
but
here
you
need
to
specify
the
life
cycle
of
releases,
which
means
you
need
to
say:
when
do
we
need
to
trigger
a
new,
build
and
deploy
a
new
version
of
one
image,
whether
it's
a
mono,
Ripple
or
multiple
repository?
What
are
the
conditions
leading
to
a
new
version
with
a
new
tag
and
then,
once
that
image
is
deployed
to
the
docker
Hub,
what
will
be?
What
would
be
the
conditions
triggering
the
whole?
Let's
update
jenkins.io
website?
D
Yeah,
the
thing
is,
for
the
time
being,
we
are
overwriting
the
image
whenever
A
Change
Is
made
so
I
know,
that's
not
good
practice
at
all.
You
know
it's
like
using
laters,
but
even
worth
we
have
depend
about
working.
We
may
install
update
CLI
one
of
these
days
and
I
think
we
may
have
released
drafter,
but
I.
A
Don't
know
you
are
defining
the
how
I'm
asking
a
higher
level
question
folks,
what
will
be
the
condition
to
trigger
a
new
release?
Is
it
a
new
dependency
that
we
track
is
available,
or
is
it
once
a
week
or
is
it
when
a
human
decide
to
make
a
release,
or
is
it
something
else?
It's
more
that
kind
of
question,
because
the
rest
is
only
technical
details
that
I
have
no
doubt
that
Bruno,
ashutosh
and
other
will
serve.
D
Yeah,
so
whenever
a
human
being
decides
it's
time
to
make
a
new
version,
because
we
made
some
modifications
to
the
docker
files,
for
example,
but
also
when
dependency
is
a
deity
like,
for
example,
a
new
LTS.
Then
we
have
to
update.
A
Okay
and
then
same
question,
but
we
don't
need
an
answer
now,
because
it
doesn't
it's
a
separated
process.
So
it's
I
don't
want
to
block
a
footer
from
that
part,
but
you
have
to
think
about
that.
I
should
ask
your
producing
images.
What
is
the
value
of
these
images?
It's
only
if
someone
consume
them,
so
you
have
the
g-soc
board
and
I
am
a
voice
of
the
Jenkins
project.
That
say:
hey,
that's
cool!
You
already
have
the
value
as
the
G-Shock
Park
I
hope,
but
that's
a
discussion
that
I
don't
have
any
voice
on.
A
So
it's
a
new
constraint,
it's
not
something
that
you
had
to
to
reserve
until
now,
so
that
the
context
changed.
So
it's
not
that
you
did
bad
or
did
wrong.
That's
absolutely
not!
It's
just
a
context,
change
to
think
about
a
different
context
to
make
the
Handover
from
a
gsac
project
to
something
widely
used:
I
I!
A
Let
Bruno
guide
you
on
the
steps,
what
what
would
be
required
and
what
is
not
a
requirement
but
more
nice
to
a
thing
because
I
don't
have
I,
don't
have
the
scope
of
the
gsoc
fully
on
my
mind,
so
I
delegate
to
Bruno
and
John
Mark
on
that
part.
But
if
we
want
that
work
to
be
pushed
on
the
Jenkins
project,
these
are
requirements.
B
A
I
think
we
have
all
elements
to
answer.
You
must
probably
the
destination
will
be
asking
the
GitHub
Jenkins
CI
organization
administrator
to
create
a
mono
repository
that
you
bring
us.
Your
Market
list
will
be
admin
off,
and
then
we
will
have
to
ask
the
Jenkins
Docker
image
administrator
to
create
the
repositories
and
had
the
proper
token,
if
needed,
to
allow
building
these
images,
which
leads
us
to
the
infrastructure
parts.
Now.
A
So
as
an
administrator
of
the
Jenkins
infrastructure
boards,
but
I
don't
have
administrative
permission
on
Jenkins.
I
can
only
work
on
the
docker
Hub
part
for
you.
So
my
proposal
is
that
now
we
we
are
going
to
open
a
Jenkins,
Dash
infra,
slash
L
desk
issue,
so
with
Jenkins
is
a
GitHub
repository
owned
by
the
Jenkins
infrastructure
team
used
for
everything
that
has
a
foot
on
the
infrastructure
or
Docker
Hub
or
GitHub
permissions.
A
So
we
have
a
centralized
location
where
to
track
this
kind
of
requests,
so
that
mean
I
should
ask
you
will
have
to
summarize
with
the
help
of
Bruno
and
John
Mark
everything
we
say
today
and
you
will
have
to
open
a
nail
desk
issue.
That
will
be
the
actionable
because
then,
from
there
we,
the
Jenkins
infrastructure
team
will
be
able
to
contact
and
ping
the
different
actors
and
have
a
centralized
photo
oops.
Is
that
clear?
Yes,
okay.
A
You
will
have
a
CI
that
can
be
available
on
ci.jenkins.io
the
public
channels.
This
one
will
be
easy:
a
Jenkins
file,
we
action
from
Jenkins
in
Fatima
to
track
the
job
for
builds,
so
we
will
create
a
job
somewhere
on
CIA
Jenkins.
So
you
will
give
you
the
link
on
the
ldesk
issue.
You
are
the
Jenkins
file
on
a
pull
request
and
automatically
see
I
drink
inside
your
controller
will
track
and
give
you
checks
on
each
pull
request
and
each
commit
on
the
principle
Branch,
but
at
only
CI
the
CD
ports.
A
A
We
have
trusted
CI,
Jenkins
IO,
which
surely
is
to
manage
the
update
Center
and
the
official
Jenkins
images,
and
we
have
infrared
CI,
Jenkins
IO
the
controller
for
the
Jenkins
infrastructure
test
with
which
pushes
all
the
Jenkins
here
in
for
images,
but
a
few
Jenkins
image
just
such
as
the
acceptance
test
harness
at
first
sight.
I
believe
that
we
should
use
infrastia.
A
A
Yeah
your
proposal
is
here
to
operate.
Unless
security
concerns
about
the
image
content,
we
can
revisit
the
choice
of
the
city.
Of
course,
the
main
takeaway
for
you
is
here
is
that
you
will
have
separated
CI
and
City
that's
way
different
than
what
you
are
building
with
GitHub
action
today.
Today
you
can
control
when
I
have
tag
then
deploy
to
the
curb
or
when
the
bill
depend
on
the
master,
Branch
then
deploy
to
the
curve.
You
have
control
over
this
one.
You
will
list.
A
A
A
Is
that
okay,
for
everyone,
be
aware
that
we
might
have
other
feedbacks?
That
could
absolutely
say
the
opposite
of
what
we
just
said
now
asynchronously
on
that
written
issue?
That's
why
we
need
written
communication,
because
overall
communication
is
for
brainstorming
and
asking
and
answering
questions,
but
that
one
will
serve
as
an
official
specification
that
we
can
persist
and
come
back
to
overtime.
B
A
No
problem,
if
anything,
if
you
forget
anything
and
you
want
to
come
back
or
have
any
question
further,
please
ask
the
question
start
a
Roth
issue
with
just
a
bit
of
context
and
ask
your
question
there
on
the
threads.
No
problem,
we
can
answer
them,
that's
not
a
problem.
This
can
leave
you
you
don't
you
are
not
expected
to
produce
something
written
once
and
never
touch
them.
A
Stefan
can
confirm
that
we
quite
often
edit
our
issues.
Contents.
The
important
part
is
that
we
have
the
question
and
the
discussion
persisted
so
the
future
ashutosh
in
eight
months,
when
you
will
have
to
come
back
saying
why
did
I
made
that
Docker
file?
You
will
have
a
written
answer
that
you
can
think
about,
and
the
community
will
benefit
from
that.
That's
my
goodness.
A
Thanks
ashutosh
for
the
work
you
did
on
this,
that
that's
a
great
project,
I
hope
you
learned
a
lot
and
have
a
bit
of
fun
at
least
and
don't
hesitate
you
off
free
to
stay
here.
If
you
want
to
continue
the
meeting,
but
no
one
will
be
mad
at
you.
If
you
stop
now
and
do
something
else,
productive,
no
problem!
You
choose.
C
E
Am
I
Audible,
yes,
okay,
just
in
case
so
I
just
wanted
to
to
hop
on
the
call
of
the
the
meeting
we
had
with
the
CDF
a
bit
to
get
you
up
to
speed
about
what
we
discussed
when.
E
A
Okay,
so
welcome
welcome.
So
let's
start
on
the
tasks
we
were
able
to
finish
during
the
last
milestone:
I'm
gonna,
take
them
on
the
order
of
my
screen
and
I
will
take
notes.
At
the
same
time,
Bruno
Stefan
I
see
that
you
have
closed
the
issue.
Gdka
21
changed
from
nightly
bills
to
weekly
AA
builds.
Can
you
give
us
a
summary
of
what
you
did
and
and
the
outcome.
C
You're
such
a
liar,
we
we
did
the
upgrade.
It
was
not
as
easy
as
we
thought,
but
it's
done
in
packery,
beige
and
Jenkins
Central
and
kubernetes
management,
and
we
did
also
the
dead
CLI
that
matched
all
of
those
changes.
So
right
now
we're
using
the
nightly
builds
of
the
early
available
of
GDK
21.
D
Yeah,
so
it's
early
access,
I
think
it's
from
the
second
week
of
August,
something
like
that.
We
haven't
seen
any
newer
version
of
Early
Access
at
GDK
21
build
from
Tamarind,
but
frankly
we'll
get
that
first
official
version
next
week,
I
think
seven
days
from
now.
So
that's
pretty
normal,
but
Stefan
made
all
of
this
work.
So
we
will
be
able
to
update
to
a
non-early
access
version
pretty
easily
we'll
see
yeah,
I'm,
confident.
D
We'll
see
that's
okay,
nothing
search
everywhere
and
replace
all
count.
Mess
up.
A
C
Did
I
didn't
forget
about
the
the
event
in
the
calendar,
so
we
have
no
some
trigger
that
some
warning
that
will
trigger
two
and
three
weeks
before.
A
Cool
so
renewed
for
six
months
as
usual.
Why
is
this
six
months
and
not
one
year
or
unlimited?
It's
a
certificate
revocation
list,
so
we
need
this
one.
We
need
to
control.
Finally,
this
one
yeah
I
know,
ideally
that
should
be
renewed
every
month,
but
that
start
to
be
quite
the
walk.
So
six
months
is
an
intermediate
that
has
been
discussed
years
ago
with
the
security
team.
We
can
always
challenge
that
more
than
six
months
is
out
of
question.
C
Oh
yes,
I
had
it,
it
did.
A
A
And
we
renewed
the
gpg
keys
or
Stefan
and
RV,
because
you
changed
machine
and
created
new
GPD
keys,
so
we
encoded
and
we
also
removed
the
outdated
key
removed,
Olivier
Verner
or
black.
We
remove
the
outdating
so
Olivia.
If
you
hear
us,
you
are
not
able
to
renew
the
VPN
serial
anymore,
it's
been
two
years
but
yeah.
Now,
because
your
gpg
key
is
outdated.
So
that
was
the
only
solution
we
had
to
be
able
to
re-encode.
If
Olivier
won't
access
again,
he
can
ask
us
no
problem.
We
can
reoccode
with
a
new
gpg
key.
A
That's
all
thanks:
Stefan!
Is
there
any
question,
clarification
on
the
topic?
Edition,
okay,
so
next
topic
expiration
of
the
digital
lesson,
personal
access
token,
so
that
one
is
on
me
La.
So
these
tokens
are
updated
every
three
months.
These
are
the
tokens
that
allow
to
create
and
delete
every
pieces
of
resources
on
the
digital,
usern
Cloud
architecture,
which
is
mostly
30
percent
of
the
cloud
agent
of
cig
and
say
you
and
their
caching
proxy,
and
soon
that
will
be
the
home
of
the
new
updates
Jenkins
IU
Update
Center
by
default.
A
A
So
of
course
that
broke
the
builds
for
a
few
days
last
weekend,
so
I
opened
that
issue
I
did
on
the
Milestone
and
changed
them,
but
that
time
I've
created
the
calendar
event,
so
yeah
so
bears
and
me
folks
next
time
outside
is
it's
like
the
crl,
nothing
too
hard.
It's
a
process.
We
run
every
three
months.
Nothing
changes
work
as
usual.
So
unless
you
have
a
question
or
need
clarification,
nope,
okay
by
the
way,
I've
closed
it.
After
checking
that
every
digital
7
related
jobs
were
working
as
usual
and
were
fixed.
A
Thanks
everyone
to
helping
contributor
to
make
their
plugin
builds
work
on
Windows.
That
was
a
Gradle
thing
about
deletion,
so
the
the
go.
The
fix
was
really
simple,
but
it
had
to
be
done,
and
so
many
thanks
for
that
you
contribute
or
confirm
they
were
able
to
proceed.
D
So
now,
just
a
slight
remark:
building
something
related
to
Jenkins
on
Windows
is
a
struggle
in
itself,
so
yeah.
Thank
you.
Everybody
for
helping
a
very
brave
contributor.
D
A
Now,
walk
in
progress:
what
are
the
tasks
that
we
weren't
able
to
finish?
Some
are
cross
Milestones.
Some
we
didn't
at
that
time.
Some
are
new,
so
let's
cover
them
one
after
the
other
run.
Let's
continue.
First,
one.
No
action
required
I
think
that
I
removed
it
from
the
Milestone,
so
I
might
have
added
to
the
Milestone
here.
A
So
let
me
remove
it
immediately.
So
there
is
a
plugin
that
is,
that
will
be
removed
from
the
plugin
Jenkins
IO,
because
it
embeds
the
appropriate
dependencies.
And
then
there
is
a
long
discussion
about
what
will
be
the
solution.
There
is
no
action
expected
for
the
Jenkins
infra
team.
That's
why
I'm
removing
it
from
any
Milestone.
We
don't
have
to
track
this
one.
It's
more
for
information.
A
I'm
gonna
take
them
in
my
order
of
priority.
The
most
prior
today
is
artifactory
bond
with
reduction
projects.
We
are
officially
nuts
Apache
Central
Maven,
since
last
Friday
yay
Mark
asked
for
gifrogen
received
the
logs
until
Thursday
or
Friday.
So
now
we
are
tracking
loads.
The
idea
is
that
in
two
weeks
we
will
start
to
see
a
positive
impacts.
A
Why
two
weeks
because
we
have
cleared
the
wall
cache
system.
So
now
we
have
to
refill
that
cache,
which
involves
downloading
a
lot
of
dependencies
only
once,
but
we
have
to
download
them
by
the
way.
There
is
an
issue
on
the
maven.
A
HPI
test,
plugin
and
I
need
help.
I
think
that
I
understood
the
problem
so
I
partially
understand
it
and
I
need
help
to
drive
this
to
completion.
The
integration
test
of
that
plugin
are
broken
since
we
started
to
fine-tune
settings.
A
Xml
I
need
help
because
it
involves
a
lot
of
old
Jenkins
decisions
that
were
made
in
2015
with
Maven,
whatever
version
the
initial
idea
that
Brazil
also
pushed
on
was
to
remove
the
old
plugin
in
charge
of
trying
to
to
proxy
every
dependency
so
that
each
integration,
the
scenario,
doesn't
download
the
dependency
each
time.
However,
that
plugin
does
not
result
properly
the
mirrors
and
everything,
so
it
was
fitting
on
cigar,
but
not
on
contributor
individual
laptops.
A
My
problem
is
whatever
I
tried
when
playing
with
settings.
Xml
use
for
this
test.
I
cannot
reproduce
on
my
machine
The
Horizon
cig,
even
with
the
same
Maven
setup.
So
there
is
something
I'm
missing,
maybe
obvious,
but
I
need
help
from
let's
say
a
specialist
to
give
this
to
completion.
If
I
can't
find
anything
on,
my
own
I
will
ask
directly
basil
Danielle
the
usual
yeah
everyone,
every
Jenkins
contributor
I
could
find
from
the
past
seven
years.
Basically
that
was
just
the
notes.
Anyone
interested
you
can
look
on
the
issue.
A
A
Okay,
I'm
putting
now
rm64
so
Stefan
control
can
describe
his
work
while
I
take
notes.
C
That
you
want
to
pause
in
fact,
I
try
to
create
an
exhaustive
list
and
in
fact,
I
missed
a
lot.
So
I
have
to
work
again
on
that
exhaustive
list
which
is
not
exhaustive,
but
the
system,
the
shared
pipeline
library
that
built
our
images
is
now
fully
functional
and
even
with
the
Legacy
part
for
Windows
and
the
new
one.
Even
when
we
specify
path
and
and
specific
arguments,
so
I
switched
to
migrate
a
few
more
to
am
64
for
the
public
k8s
cluster
and
we
oh
and
then
it's
another
issue.
C
We
I
merged
two
issue
in
my
brain
because
we
also
work
on
avoiding
irm
on
the
same
node.
I
I
did
prepare
everything
for
Wiki
and
for
Account
app,
so
I
couldn't
help
should
soon
migrate
to
Aram
64.
A
Thank
you,
okay,
cool
thanks,
so
that
means
that
mean
we
have
the
list.
C
A
C
C
A
I
did
in
the
issue
not
absolutely
exhaustive,
but
a
good
start,
yeah
warning
about
update
CLA.
A
That
must
be
aware
of
the
am
64
images
and
check
both
in
there
and
I
rhyme,
and
do
you
agree
Stefan
that
it's
an
opportunity
for
us
for
each
of
the
images
to
push
them
on?
No?
No,
no
for
each
of
these
images
to
properly
check
and
fix
the
life
cycle,
meaning
we
we
should
not
use
latest
anymore
on
any
of
the
images
and
instead
use
our
automatic
tagging
deployment
system.
Yes,.
A
So
on
use
latest,
so
we
were
using
kind
of
latest
that's
something
we
checked
with
Stefan,
because
we
had
to
update
some
images
with
packages
regularly
because
you
don't
want
a
CV.
So
first
problem
is
that
some
of
our
images
end
up
for
not
naming.
It
hasn't
been
changed
since
two
years,
which
is
catastrophic
from
my
point
of
view
and
the
process
should
have
been
update,
CLI
or
whatever
tool
say.
Oh
this
week.
What
is
the
the
Sha
of
the
latest
version?
A
So
you
can
Surface
to
The
Operators
to
the
prediction
operators
that
oh
there
is
a
new
sha.
There
is
a
change,
so
you
have
to
find
this
change.
In
that
case,
it
was
a
set
share
for
numerous
reasons,
including
no
solution
were
able
to
to
get
the
source
of
reference
for
these
images
because
we
don't
have
tags.
A
So
the
pattern
for
building
this
Docker
images
is
the
same
as
what
ashutosh
did
for
the
gsoc.
We
were
building
a
main
branch
and
we
were
overriding
the
latest
tag,
and
then
we
had
that
detection
system
that
say:
oh
there
is
a
new
that
that's
not
bad
or
wrong.
That's
just
how
it
used
to
be,
which
now
is
the
rm64
problem.
We
need
to
switch
to
tags
because
when
we
deploy
a
tax
version,
We
differ
to
the
kubernetes
cluster.
The
choice
of
how
I'm
running
on
Iram
64.
A
I
want
to
manifest
for
the
irm
64
for
that
tagged
image,
the
otherwise,
if
we
don't
use
shh
checksum,
if
you
want
to
stay
strict,
that
means
we
need
to
update
all
of
our
M
chart
to
say:
oh,
the
N
chart
must
know
based
on
the
Node
selector.
Oh
I'm,
gonna
run
an
FM
64
here
is
the
checksum
for
the
rm64
or
Intel
or
then
my
checksum
is
there,
which
means
a
dead
seal.
I
need
to
keep
track
of
both
sha,
not
a
problem.
It's
just.
C
I
think
we
also
need
to
spend
a
few
minutes
few
few
hours
to
improve
the
child
pipeline
library
to
to
tag
and
push
in
one
pass
and
not
having
Main
and
tag
that
we
need
to
to
speak
about.
That.
A
So
Stefano
can
I
ask
you
for
the
upcoming
Milestone
to
open
an
issue
describing
the
expectation
here.
You
don't
have
to
find
a
solution
on
the
code
user
step
to
describe
the
eye
level.
Workflow
and
I
propose
on
the
following
reason
that
that
will
decrease
by
half
the
number
of
builds.
We
do
on
infra
CI
for
Docker
images.
Is
that
or
at
least
25
percent,
but
any
case
that
will
be
less
credit,
spend
on
azure.
C
Nope,
can
we
can
we
speak
about
the
ntf
in
here
right
after
this
one,
because
it's
matching.
C
Not
much
I
just
prepared
a
pull
request
to
make
sure
that
any
kind
of
of
application
that
have
more
than
one
replica
account
got.
This
replica
count
on
multiple
different,
node
and
and,
of
course,
I
started
with
the
m64,
because
they
are
the
one
that
are
more
more
visible
probability
to
get
that,
because
there
is
a
few
nodes
and
that
mean
that
kubernetes
tend
to
spoon
all
the
old
replica
on
the
same
node.
A
Cool
and
I
was
able
to
review
your
pull
request
and
validate
on
the
local
cluster
that
it
works.
So
the
next
step
is
to
deploy
and
see
how
it
behave
on
real
life
with
aka's
autoscaler,
because
that
one
cannot
be
tested
except
in
production,
so
yeah
we
might
bring
down
the
wiki
for
a
few
minutes,
but
better
doing
it
on
the
control
way.
So
that
means
you
need
to
this
to
decide
an
operation
time
open
a
status
chain
kinsayu,
and
then
we
can
merge
and
see
that
one
that
shouldn't.
B
C
A
A
list
of
tasks
to
apply
this
because
then
we
can
create
issues
and
mark
them
as
a
newbie,
and
then
that
means
you
will
be
able
to
drive
the
newbies.
If
you
have
new
contributor
that
want
to
try
opening
pull
request
and
contributing
you
can
drive
them,
give
them
feedbacks.
We
have
Octoberfest
coming
well,
you
can
spend
your
your
brain
on
something
else
more
valuable
than.
A
Is
that
clear,
perfect?
No,
more,
no
more
question:
okay,
Next
Step
blah
blah
blah
I'm
gonna
report
for
LV
about
updates,
Jenkins
Sayo
migrated
to
another
cloud,
so
problem
statement,
updating
your
run
on
AWS
on
whole
virtual
machine,
which
is
not
even
highly
available.
That's
a
really
important
service.
That's
the
the
most
important
service
of
the
world
infrastructure,
as
I
as
I
will
say.
A
The
goal
is
to
use
a
mirror
director
system,
so
Airway
was
able
to
build
an
HTTP
director
which
is
running
on
Azure,
and
now
it
started
to
two
parallel
tracks,
starting
a
mirror
on
digitalocean
using
the
same
L
chart
as
we
have
on
Azure
cluster.
So
we
use
the
same
bricks
that
will
be
the
default
mirror
that
will
be
hosted
in
Frankfurt.
A
Then
in
parallel
is
working
with
cloudflare
to
start
a
sponsorship,
so
they
will
ask
mirrors
of
this
one
in
the
form
of
S3
buckets.
The
goal
is
to
have
one
on
U.S,
east
and
one
in
Asia
eventually,
so
the
the
proposed
timeline
will
be
having
a
brown
out
before
end
of
September
to
try
last
last
week
of
September.
A
Unless
we
discover
something
complicated
to
move
the
updates
tank
inside
your
domain
name
for
one
hour
to
the
new
one
another
and
see
the
results,
of
course,
we
will
test
with
controller
B
for
that
and
we
will
ask
from
security
and
usual
contributors,
but
the
the
whole
idea
is
that
we
have
redirects,
so
we
can
continue
using
redirects
that
will
remove
from
five
to
seven
K
of
bond
with
billing
from
AWS
worst
case.
If
everything
migrate
to
only
digital
ocean,
so
digitalocean
primary
mirror
is
being
built
worst
case
billing
scenario.
A
So
even
the
worst
case
that
would
be
easier
for
us
if
we
cannot
sustain
both
cig
and
inside
your
builds
and
update
on
updating,
we
will
remove
CI
Jenkins
I,
go
somewhere
else
or
find
new
new
sponsors,
and
so
everybody
has
started.
Contacted
digital
listener
is
going
to
to
increase
or
move
the
the
sponsorship
here.
The
goal
is
to
leverage
the
impact
of
moving
that
service
towards
your
own
Azure
itself,
cloudflare
answered
and
is
evaluating
sponsorship
for
us
and
Azure
appearance
worst
case
we
have,
or
we
have
a
box
for.
A
A
One
two:
three
okay,
so
now
now
now
I
get
a
few
SSL
certificate
expires
in
25
days,
so
Mark
thanks
Mark.
Our
best
monitoring
system
ever
detect
that
the
5
of
October
the
certificate
for
this
free
domain
will
expire.
So
after
a
quick
research,
when
we
moved
a
migrated,
AKs
clusters,
a
change
was
propagated.
That
means
these
domains
are
the
three
of
them
are
pointing
to
our
cluster,
which
redirect
them
to
firstly
for
WWE,
Jenkins
Sayo
cdnis,
the
version
of
the
website.
A
The
thing
is,
we
still
need
to
have
TLS
connection
before
the
redirection
open
and
the
culprits
is.
There
is
a
problem
with
the
certificate
renewal
inside
our
AKs
cluster
I.
Try
to
give
a
summary
here,
but
we
need
to
remove
one
certificate,
let's
encrypt
setup,
from
vastly
and
remove
one
English
domain
from
our
arcade's
cluster
and
then
renew
the
certificate
that
should
solve
the
problem
once
for
all.
The
main
reason
is
because
we
have
one
Ingress
with
four
or
five
hostname,
which
means
one
certificates
which
suggests
alternative
names
and
one
of
the
domain
names.
A
Is
failing
which
make
the
world
certificate
renewable
to
fail,
and
why
is
it
failing?
Because
ww
Jenkins
IO
is
manage
by
festi
themselves,
let's
encrypt
included
and
I
think
everyone
I
missed
that
close
domains
due
to
how
fast
it
works.
So
that
should
be
the
corporate.
So
we
are
working
on
this
one
for
the
upcoming
milestone,
I'm
taking
it
by
default.
A
But
when
you
have
300
or
400
parallelized
steps,
which
is
our
case
for
the
bump
steps,
the
some
sh
steps
are
now
as
Mark
discovers
some
stations
and
stash
steps
as
well
takes
minutes
when
they
should
take
seconds
so,
for
instance,
seven
minutes
to
run
a
curl
head
on
one
of
the
ACP.
The
sh
process
takes
less
than
one
second,
but
then
it
takes
seven
minutes
for
Jenkins
to
retrieve
the
state
close
the
connection
and
do
whatever
they
do
internally.
A
So
due
to
that,
Jesse
helped
us
and
we
enabled,
on
our
some
of
our
controllers,
mainly
see
I
drinking
a
new
startup
flag
which
changed
the
way.
The
pipeline
CPS
system,
the
durable
task,
when
you
restart
controller
pipelines,
can
resume
after
the
restarts
the
way
that
mechanism
works.
You
change
its
Behavior
I.
Don't
know
the
lower
level
details
and
I,
don't
oh
I
don't
want
to
share
them
now
it's
public,
but
we
are
trying
that
new
mode.
Now
that
should
have
a
great
impact.
A
C
C
As
for
the
rest,
the
the
image
I
have
done.
Nothing
yet
on
it.
A
Okay,
we
so
new
subnets
draft
for
the
terraform
manage
MySQL
instance.
So
we
need
need
to
discuss.
Is
that
correct?
Yes,
validates
some
specs,
no
more
work
yet
on
the
docker
image?
No,
no!
You!
No!
You
clean!
You
already
started
to
clean
right.
A
A
C
A
C
A
C
A
Just
a
word
about
Jenkins
image
from
our
new
contributor
who
is
not
able
to
visit
us
this
week.
He
started
to
work
on
playwright
artifacts
because
we
discover
on
the
cig
and
kinsai
your
agent,
where
the
container
or
virtual
machines,
but
over
Linux
we
had
unwanted
artifacts,
mainly
packaged
season
and
odd
modules.
That's
not
a
problem
that
wasn't
a
blocker.
A
He
found
that
it's
because
of
the
sanity
check,
because
we
check
that,
given
the
dependencies
we
installed
during
the
provisioning,
then
we
should
be
able
to
install
prey
white
playwright
test
and
run
a
command
in
studying
that
test
framework
and
the
associated
command.
If
we
embed
the
tools
and
its
dependencies
creating
these
leftovers,
so
we
started
the
discussion.
Do
we
want
to
add
that
tool
as
a
tool?
A
A
A
A
We
shouldn't
have
an
impact
but
yeah
at
least
less
work
done,
but
I
trust
Stefan
will
do
a
lot.
You
already
did
and
we'll
see
if
her
ways
is
going
better.