►
From YouTube: 2023 01 10 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
Hello,
everyone
welcome
to
the
Jenkins
weekly
meeting
for
the
infrastructure
team,
Sig
team,
so
first
of
all
opinion
year.
That's
the
at
least
for
me.
I
know
that
some
of
you
already
saw
each
other
last
week,
but
that's
the
first
time
so
I'm
happy
to
start
a
new
year
and
I
wish
the
best
for
the
upcoming
month
to
everyone.
A
D
A
Nice
one
thanks
for
that
info
and
for
the
job,
the
hidden
job
behind
that
Mark,
who
you
have
other
announcements,
none
for
me
not
there,
just
a
big
thank
a
big
thanks
to
Stefan
and
Mark
for
running
the
weekly
meeting
last
week
by
the
week.
A
A
387
will
be
Tuesday
17th
of
January
important
note
to
everyone.
Tomorrow
is
LTS
release
day,
so
the
Jenkins
LTS
version
2.375.2
will
be
released
and
published
tomorrow.
I
understand
that
Christian
is
the
release,
lead
that
time
our
infrastructure
Uncle
Duty
persons
to
help
Chris.
During
the
the
release
we
will
be
available
on
Stefan
mail.
Both
of
them
will
be
there
to
be
to
support
creases.
C
Permissions
to
launch
the
build,
so
he
confirmed
in
governance
meeting
on
Monday
that
he's
willing
to
launch
the
build
as
well,
so
that
that
should
make
it
simple
for
the
infra
team.
If
Alex
launches
the
build,
he
tends
to
launch
them
relatively
early
in
the
day
and
but
by
all
means
check
with
him
to
see
if
he,
if
he
needs
help
or
if
by
nine
or
ten.
Your
time
you
have
not
seen
a
build
start,
it's
worth
asking
because
you're
right
Christian
is
in
Asia.
A
Good
to
know
so,
I
won't
be
really
available
on
my
sides
tomorrow,
except
asynchronously,
so
that
would
be
a
nice
test
for
both
for
everyone,
but
yeah
any
case
call
me
and
I
should
be
able
to
to
park
somewhere
and
open
the
computer.
A
And
next
security
release
and
known
announced
on
the
mailing
list,
I've
added
a
link
for
to
here's
our
browsing
in
the
future
and
to
next
major
events
that
I
know
are
will
be
the
first
demo,
four
and
five
February
in
Brazil
2013
and
14
April
of
2023
in
Paris
play
yes,
12
to
14.
thanks
I
know
that
at
least
one
eventually,
two
percent
on
that
room
will
submit
bird
of
feather,
which
are
kind
of
informal
discussion
on
the
topic.
That's
last
one
hour.
A
So
it's
a
kind
of
gathering
of
people
asking
person.
It's
not
let's
say
a
formal
presentation.
It's
more
Roundtable
one
will
be
around
mobile.
Is
that
correct,
Bruno.
D
Yeah
yeah,
mobile
and
Jenkins,
the
other
one
will
be
about
building
for
embedded
hardware
and
or
building
on
exotic
Hardware
with
Jenkins
nice.
A
And
everybody
is
working
on
the
Jenkins,
simple
Jenkins
spread
of
feeder,
so
that
will
be
a
discussion
for
any
Panera.
Any
people
interested
I
will
assist
survey
on
submitting
that
topic,
but
are
no
Richie
confirmed
that
we
can
submit
one.
A
No
okay:
let's
proceed
a
few
issues
done
during
the
past
week,
nice
job
on
this
one
because
especially,
we
were
still
in
holidays
or
coming
back.
First
of
all,
General
availability
of
Windows
Server
2022.
A
So
thanks
Stefan
for
the
work
involved
here.
So
that's
that's
allows
developers
and
cidenkins
IO
to
use
a
new
label
Windows
2022
if
they
seek
to
build
on
a
machine
or
using
specific
containers
tested
manually
by
Stefan.
So
we
have
ping
the
person
who
requested
such
an
image
on
I
think
it's
Jenkins
controller
Docker
image,
so
I've
pinged
them
if
they
want
to
continue
or
we
will
take
care
of
any
maintainer
but
on
the
infrastructure
side.
It's
closed.
A
A
A
Thanks
for
the
for
the
detail,
good
point,
duplicate
profile,
I,
don't
know
which
issue
it
was
so
okay.
So
thanks
survey
and
Mark
I
remember
so
someone
had
an
issue
with
their
accounts.
So
thanks
for
solving
the
that
issue,
is
there
anything
something
to
say
on
this
one
Mark
or
Airway.
C
E
C
Right
so
we
can't
combine
the
profiles,
but
as
far
as
I
can
tell,
the
user's
original
profile
had
two
issues,
one
or
two
issues
reported
in
issues.jenkins.io.
The
new
profile
seemed
to
have
no
action
activity
on
issues.jenkins.io,
so
I
didn't
don't
think
by
deleting
the
new
account,
we
would
lose
any
content
for
the
user
and
they
are
not
a
plug-in
maintainer.
So
they're
not
uploading
anything
to
repo.jenkinsci.org.
A
Okay,
are
you
at
ease
with
doing
that
operation,
Mark
or.
A
Okay,
so
I'm
adding
it
to
the
next
Milestone
and
we
will
close
then
if
you
do
it,
no
sorry,
let's
keep
it
on
current
Milestone.
It's
it
should
be
closed.
Can
I,
let
you
close
that
issue
once
it's
finished.
A
Yes,
cool
thanks!
Okay,
next
one
renew
digital
assistant,
personal
access,
token,
so
thanks
everyone
Stefan
for
managing
this
one.
So
to
summarize,
we
have
a
technical,
personal
access,
token,
a
technical
account
related
on
digital
Lucian
because
they
don't
have
the
concept
of
an
app
like
a
GitHub
app.
So
since
we
need
to
generate
this
token,
we
need
technical
account
which
doesn't
have
access
to
billing
or
administrative
areas,
and
that
token
is
renewed
every
19
days.
A
So
we
had
to
renew
it.
It
expired
last
Monday.
We
had
alerting
system
that
went
very
well,
so
we
were
able
to
renew
it.
It
was
documented
on
the
issue.
The
only
problem
we
are
having
here
is
that
I'm,
the
only
one
able
to
login
to
that
account
because
of
the
MFA,
because
it's
on
my
app
and
we
cannot
add
multiple
MFA
system
like
we
would
on
GitHub,
so
I'm,
not
really
sure
which
road
to
take
from
there,
removing
the
MFA
or
eventually
ask
digital
design.
A
If
we
could
use
email
based
token
a
bit
like
a
zoom,
what
Zoom
is
doing
so,
each
time
someone
logs
there
is
a
numeric
code
sent
to
the
email,
so
that
will
be
an
MFA
I,
wasn't
able.
So
if
it's
okay
for
you
I
will
ask
that
to
the
digital
Essence
support
explaining
our
use
case,
because
maybe
they
have
something
for
that
problem
to
solve
that
problem.
A
A
Yeah
good
to
see
if
we
don't
have
false
negative
there
good
point
thanks.
Okay,
so
welcome
to
shoe
as
usual,
okay
I'm
going
to
switch
to
the
work
in
progress
for
each
issue.
We
have
to
decide
if
we
are
able
to
work
on
it
on
the
next
iteration
or
if
we
should
move
back
to
backlog,
don't
forget
that
we
will
have
new
items.
A
A
So
I
will
take
care
of
this.
One
I
need
I
just
want
to
check.
How
can
we
administrate
both
key
cloak
and
accounting
kinsayu?
It
sounds
like
it's
not
the
same
mechanism
so
interesting
to
check,
in
any
case,
I
I'm,
UPS
I'm,
okay,
for
giving
you
these
accesses.
A
C
Yes,
I
I
think
it's
to
me.
At
least.
It
seems
obvious
that
if
you
can
access
click
key
cloak,
you
clearly
should
have
enough
permissions
to
also
be
an
account
administrator
on
accounts.jenkins.io
key
cloak
is
behind
the
firewall
right
if
I
remember
right
or
it's
inside
the
VPN
and
therefore
all
sorts
of
privileged.
A
A
E
Great
I've
took
a
look
at
the
Rainbow
Country
for
accounts
to
check
the
group,
and
I
saw
the
table
listing
all
of
them
and
some
notes
we
might
want
to
do
something
about
it,
since
a
lot
of
them
are
I'm,
not
sure
I,
don't
know
the
tourist,
so
yeah.
A
Okay,
so
I
will
look
at
the
Run
books
and
check
that
button
cool,
any
question:
okay,
Next
Issue,
all
the
inbound
agent
Publishers
latest
so
yeah.
We
still
have
that
recurring
issue
and
trusted
cig
and
kinsayo
where
some
of
the
jobs,
but
not
all,
are
not
behaving
as
expected.
That's
a
word
bug
that
we
can't
understand
the
jobs
are
configured
to
ignore
tags
that
are
ordered
and
three
or
six
days,
and
it
builds
tags
that
are
two
years
old
and
these
these
ones
builds.
This
tags
keeps
overriding.
A
The
latest
tag
on
the
images
on
the
docker
head.
I
took
the
time
earlier
today
to
explain
the
battery
plan.
I
got
in
mind
the
idea
right
now,
so
that
problem
was
fixed
by
the
new
release
we
did
yesterday
of
the
images
you
have,
a
new
release,
you
build
a
new
tag
and
latest
is
again
overrated.
A
I
will
say
most
of
the
time.
Someone
using
a
latest
tag
is
is
really
at
EDH.
So
you,
let's
say
friends,
don't
let
friend
you
latest.
However,
it
can
still
be
it's
still
a
problem.
So
my
proposal
is
to
First
archive
the
current
jobs
that
we
have
on
trusted.
Ci
backed
them
up
directly
on
the
file
system
of
the
virtual
machine
and
have
an
archive
somewhere
like
in
the
big
archive
bucket
encrypted
part
that
they
have
created
last
month,
thence
we
disable
meaning.
A
We
delete
the
job
once
backed
up
now
we
checked
the
back
the
backup
and
create
again
free
multibranch
jobs.
Instead
of
a
GitHub
organization
scanning,
with
a
list
of
free
jobs,
I
mean
free
configuration
is
acceptable,
even
manually
managed.
The
goal
is
to
be
sure
that
we
start
with
a
clean
State
and
to
demonstrate
that
we'll
we
should
see
during
the
initial
scan
that
only
the
tags
released
yesterday
will
be
rebuilt
and
overriding
on
the
docker
hub.
A
That
will
be
the
demonstration
that
the
issue
was
something
because
this
is
an
old
job
with
a
bunch
of
config
XML
that
were
upgraded
during
years.
I
think
it
has
been
created
in
2015.,
so
let's
say
gut
feeling
that
something
in
the
XML
might
be
wrong
or
an
in
a
word
bug
with
the
GitHub
organization
scanning.
So
the
goal
is
to
have
less
moving
pieces
and
we
control
each
of
these
three
jobs.
A
A
Finally,
on
long
term,
so
we
have
an
issue
that
I
will
talk
about
later,
but
we
should
move
this.
These
jobs
from
trusted
CI
to
release
CI
at
least
the
job
mentioned
on
2845,
which
build
Jenkins
official
Docker
controller
image
we
have
to
discuss
if
the
free
jobs
mentioned
on
that
issue.
For
the
docker
agent,
images
should
be
moved
on
release
CI
as
well.
Are
there
official
release
Jenkins
assets?
Are
there
something
else
we
we
have
that
discussion?
That
should
happen.
A
A
A
C
A
Because
security
advisory
process
requires
to
be
quick
and
right
now
we
are
stuck
with
the
latest.
There
is
an
issue
open
about
that
all
right.
Okay,
next
issue
is
cigo
move
ACI
remaining
workload
to
kubernetes.
A
A
E
A
A
A
Is
that,
okay
for
you
to
put
it
on
backlog?
Yes,
given
your
intent
was
to
not
lose
that
issue
somewhere
on
a
black
hole
yep,
but
somehow
this
is
a
new
black
hole,
but
thanks
survey
exclude
non-numeric
plugin
version
from
Update
Center.
A
E
I'm
wondering
if
this
I
found
3DS
or
old
one
thing
in
the
existing
list:
yeah.
B
C
I
know
that
Daniel
Beck
will
accept
pull
request
to
update
Center
to
the
repository,
and
that
seems
like
the
place
where
this
would
have
to
be
made.
I,
don't
know
that
we're
the
ones
who
have
to
make
it
I
think
that
was
what
you
were
asking
Damien
right,
because
this
seems
like
it's
a
a
change
in
a
in
a
pattern
that
Daniel
may
just
simply
reject
and
say
no
I'm.
Sorry,
we
are
allowed
to
have
whatever
version
string.
You
wish.
E
C
E
E
D
A
Okay,
both
of
you
are
making
good
points
are
way
or
Mark.
Can
one
of
you
take
the
lead
on
this
one
and
ping,
both
Danielle
and
Kevin,.
C
A
A
Yep,
as
stated
by
RV,
we
are
still
having
the
umbrella
of
the
Year
desk
and
multi-repository.
So
somehow
we
still
have
a
foot
on
that
area
and
a
voice
on
the
matter.
So
and
let's
keep
it
then
both
of
you
are
making
good
arguments,
and
that
meant
thanks,
Mark
and.
A
I've
assigned
to
to
you
Mark,
if
you
don't
have
the
time
we
will
take,
take
care
of
taking
this
one
next
week,
it's
still
a
bit
early
for
my
brain
being
back
from
holidays
to
fully
process
the
intent
of
this
one.
So
that's
why
I'm
asking
for
other
leads
so
I've
added
that
to
the
next
Milestone
thanks
blocked
from
creating
a
new
account
in
the
anti-spam
system.
I
think
this
one
is
waiting
for
an
answer
from
the
user.
A
E
A
I'm
not
sure
there
are
code
path
where
the
account
is
created
and
somewhere.
It
is
not
both
code
paths
lead
to
the
that
message,
so
we
have
to
check
the
logs
of
the
application.
A
It
was
last
week
so
I
guess
it
might
be
lost
already,
so
we
should
retry
creating
a
new
account
in
his
name
and
while
watching
the
accounts
to
drink
inside
your
logs
to
see
if
there
is
any
logs
that
could
help
I
don't
mind
taking
that
one.
Unless
someone
is
interested.
A
A
It's
the
next
milestone.
Sorry
next
issue.
C
Correct
there
was
never
a
response
to
my
email
and
so
without
a
response
to
the
email
that
there's
no
evidence
that
the
that
the
person
who
submitted
this
is,
in
fact
in
control
of
that
account
right.
So
I
think
it
was
very
dangerous
for
us
to
act
on
this
request.
When
we
we
haven't
confirmed
the
the
One
path,
we
know
they
must
have
control
of
the
email.
They
don't.
A
Yep
is
there
any
voice
again,
since
it
was
one
week
ago?
Is
there
any
voice
against
closing
has
not
planned
with
a
message
to
the
user?
We
keep
it
closed.
Unless
your
answer
to
the
email.
A
A
A
So
that
one
moved
to
close
does
not
blend,
am
I
am
I
understanding.
It
correctly.
Are
we
yeah
next
issue?
That's
listed
since,
before
Christmas
we
had
changes
on
terraform
AWS,
eks
module.
We
had
to
recreate
a
cluster
the
tissue
tracks,
all
the
changes
that
had
to
be
done
to
recreate
the
ACP
instance
at
repo
AWS
champion
last
step
is
that
let's
encrypt
certificate
is
not
generated,
because,
let's
encrypt
received
an
authentication
error
when
trying
to
retrieve
the
challenge.
A
The
HTTP
challenge
I'm,
not
sure
why
it
worked
before
when,
during
the
first
attempt
of
RV,
my
guess
is
that
there
is
something
weird
on
the
engine
EX,
so
first
solution
would
be
to
switch
to
DNS
challenge.
That
should
be
a
easier,
but
there
are
issues
on
that
area.
Security,
let's
say
concerns
not
issues,
but
yeah.
We
have
to
to
put
that
back.
I
propose
that
one
anyone
interested
can
work
on
it.
So
it's
not
the
priority
because,
right
now
we
have
to
finish
the
private
Network
and
migrate
everything
unless
someone
object.
A
A
A
Next
one
netify
site
for
Jenkins
IO
components:
the
tissue
was
open
by
giving
right
before
Christmas
sorry
gave
in
we
weren't
able
to
under
this
one
that's
a
requests
to
track
unit
device
sites.
There
are
some
additional
steps
to
be
done.
Is
there
anyone
interested
to
assist
giving
on
that
product
or
should
I
take
it.
E
A
Okay,
netplify.
A
And
GitHub
no
I
haven't
removed
3H,
and
it's
for
the
next
Milestone
cool
thanks
everybody,
some
Jenkins
mirror,
are
using
the
wrong
media
type.
I
didn't
have
time
to
to
use
this
one
to
make
this
one.
It's
a
puppet
Challenge
on
Apache
configuration
that
one
is
not
emergency.
Anyone
interested
can
help,
but
it's
not
the
priority.
A
I'm,
putting
is
that
there
might
be
a
conflict
with
the
pupet
Apache
module.
We
haven't
updated
since
at
least
one
trimester,
because
it's
breaking
tests
on
the
lemons.
So
we
should
be
careful
on
updating
this
one,
because
that
one
could
expose
sensitive
areas
on
the
virtual
machines,
especially
pkg.jenkins.io.
A
C
Actually,
I
don't
think
it's
I
I
had
assumed
it
was
more
than
documentation
because
the
status
page
itself
reports
correct
servers.
We
don't
expect,
but
on
the
other
side,
I
don't
know
that
this
is
valuable
enough
for
us
to
spend
any
time
on
it.
We've
got
other
things
that
are
much
higher
priority.
If
we
were
to
just
drop
it
and
say
we're
not
going
to
do
it
for
now,
I
don't
feel
any
any
guilt
at
that
at
all.
C
E
C
Or
not
yeah.
Well,
when
we
know
that
ftp.belnet.be
is
offline
and
we
know
that
serverion
is,
if
is
offline.
Those
two
we
know
are
offline,
aliyun.com
is
actually
online
and
they
had
wanted
to
engage
with
us,
but
we
we
didn't,
have
we
didn't
at
the
time
and
then
they
stopped
responding.
Okay,
so
I
mean
no
objections.
If
we
do
it
and
for
me
it
just
was
it's
not
as
urgent,
it's
not
as
pressing
as
some
of
the
other
things
on
our
list.
Okay,.
A
Yeah
the
survey
on
one
is
worrying.
Me
I,
don't
try
to
experiment
on
this
one,
because
the
four
last
time
we
tried
to
put
it
back
online.
We
ended
up
with
issues
from
users
and
quite
some
issues
where
the
people
were
trying
to
download
files
and
it
was
breaking
their
downloads,
especially
with
an
LTS
coming
tomorrow.
I
will
advise
against
playing
a
run
with
the
mirror
during
one
or
two
days
around
the
LTS.
A
But
are
they
no
problem
to
plan
it
for
next
iteration?
Then,
if
it's
okay
for
you
I've
gone
right,
okay
proposal
proposal,
we
contact
the
person
in
charge
of
the
four
mirrors.
So
first
we
dig
on
the
history
Associated
to
the
formula
that
we
can
get
on
the
mailing
list
and
the
issues
we
check
the
contacts.
If
we
have
some
from
the
wrong
books
and
we
contact
the
administrator
to
ask
them
if
they
are
still
willing
to
to
provide
these
mirrors,
especially
the
the
baronet
and
serverion
one.
C
D
C
A
Okay,
so
that
mean
we,
we
just
have
to
double
check
so
to
link
to
add
any
link
on
the
issue
that
that
points
to
the
story.
That
will
be
an
argument
to
remove
these
two
from
the
list.
A
Okay,
don't
forget
what
I
said
about
the
LTS,
because
if
you
remember
correctly
last
time
we
cleaned
up
and
removed
the
mirror.
There
was
a
few
minutes
of
unavailability
on
HTTP
500
errors,
so
removing
this
has
to
be
planned
and
announced.
It's
not
a
problem
that
there
is
a
row,
but
we
need
to
announce
it.
A
So
right
before
Christmas,
everybody
successfully
finished
this
spinning
a
private
Gates
deploying
an
empty
shell
for
future
infrastia.
If
I'm
correct.
A
E
E
You
Know
It
definitely
be
able
to
finish
this
study.
D
A
A
Last
news
where
the
repository
reporting
in
CI
was
merged
migrated
successfully
in
December,
it's
faster
than
it
was
before.
So
thanks
a
lot
for
g-frog,
we
need
to
do
a
post
migration
meeting
with
shifrag,
but
due
to
personal
scheduling
item
it
has
been
moved
to
next
week.
Sorry,
for
that,
I
was
able
to
confirm
that
the
issue
ayad
when
setting
up
repositories
on
the
UI
it
looked
like
it
was
gone.
A
I
have
to
confirm
that,
but
I
tried
to
change
repositories
and
it
was
instantly
taken
in
accounts,
so
that
would
ease
my
task
and
I
have
to
go
back
to
documented.
With
your
help
mark
I
think
we
need
to
set
up
a
few
a
few
pairing
sessions,
both
of
us
to
continue
the
Work
World.
We
left
it
middle
of
December.
Yes,.
C
Nope,
okay,
so
I
guess
one
one
point:
I
did
ask
for
the
report
of
bandwidth
utilization
and
support.
Jfrog
support
has
acknowledged
that
they
have
received
the
request
and
they
are
working
on
the
request.
They've
told
us.
They
can
only
give
us
data
since
December
18th
and
my
answer
back
was:
that's
perfectly
fine.
In
fact,
that's
preferred.
We
would
like
to
know
what
the
current
usage
is
and
see
if
we
can
identify
any
guilty
Parties
by
IP
address
or
by
domain
name,
that
we
could
ban
and
save
bandwidth
quickly.
A
Absolutely
the
plan
here
for
me
on
my
side
is
to
validate
some
assumption
around
how
the
plugins
are
built.
The
goal
will
be
to
enable
authentication
one
of
the
main
infrastructure
tasks
that
I
have
to
work
on
right
now,
along
with
planning
and
describing
test
is
to
find
if
there
is
a
technical
solution
to
have
ldap
replication.
A
So
anytime
we
restart
the
ldap
it's
available.
Otherwise
developer
will
be
impacted
with
our
monolithical
adapters
for
today.
Iphone
solution
that
are
working
in
the
context
of
using
virtual
machines
and
huge
setups
I
have
to
validate
that
on
kubernetes
kubernetes
could
help
as
a
framework
for
availability,
but
I
have
to
dig
more
on
that
topic.
Anyone
interesting
can
try
their
on
their
own.
I
will
run
experiment
on
local
kubernetes
cluster
before
and
I
will
then
do
a
duplicate
copy
to
test
during
sometimes
before
going
further.
A
Time
for
the
new
items,
we
had
a
bunch
of
issues
that
were
open
recently,
one
from
Eros
lab
from
the
security
team
due
to
hsts.
They
are
having
issues
with
chrome
and
not
on
Firefox.
So
since,
like
there
are
subtle
difference
on
the
way,
hsts
is
undulled
by
web
browsers
for
trusted
CI
and
cert
CI.
A
There
are
right
now
these
two
controllers
are
providing
self-signed
certificate.
Most
of
us
ignore
and
accept
the
exception
due
to
Ash
STS
on
Chrome,
it's
not
possible.
As
pointed
by
team.
There
is
already
an
eldesk
issue
open
for
that
that
was
about
have
a
valid
certificate
for
trusted.
Sea
agent
can
say
why?
A
The
good
news
is
that,
let's
encrypt
on
these
setups
with
the
set
Bots
process,
not
kubernetes
is
absolutely
able
to
under
DNS
validation,
which
means,
if
we
put
the
correct,
DNS
API
credentials.
That
said,
but
should
be
able
to
validate
worst
case.
We
can
also
do
it
manually,
but
that
will
be
to
be
re
renew
every
few
months,
so
quite
the
pain.
So
the
goal
would
be
to
find
a
way
to
configure
the
puppet.
Let's
encrypt
module,
to
have
the
correct
credentials
with
limited
accounts
as
per
team
and
F.
A
They
disclosed
it
a
few
months
ago.
We
should
be
able
to
create
Azure
account
technical
accounts
that
are
restricted
to
only
a
DNS
zone,
so
that
will
help
avoiding
issues
but
I
don't
mind
having
a
full
DNS
manipulation
from
these
machines,
because
I
mean
if
someone
access
this
machine,
if
an
unexpected
person
or
process
do
it.
A
Is
that
okay,
if
I,
try
to
to
set
Stefan
as
volunteer
on
that
one.
B
A
So
Maven
387
is
generally
available.
It
has
been
merged
on
the
main
branch
of
the
outbacker
images
so
now
and
on
the
Windows
container
templates.
A
So
we
have
to
now
release
the
packer
images
and
let
the
update
CLI
pull
request
open
and
do
their
jobs,
and
once
done,
we
have
to
communicate
to
developer
that
hey
everyone
now
Maven
387
is
the
default
version
just
in
case.
If
something
breaks
somewhere
developer
won't
waste
time
thinking.
Oh
my
pair
build
and
is
sending
where
the
raw
message.
C
A
I'm
looking
at
the
new
shoes
so
account
for
a
smell,
renewed.
Oh,
we
knew
designer
certificates
that
one
is
quite
important.
A
So
as
I
understand,
Stefan
and
Mark,
so
during
last
weekly,
the
following
message
that
say
in
March
the
code
signing
certificate
for
Jenkins
will
be
expired.
America
might
need
help
on
this.
One
is
that,
okay,
if
we
set
up
a
session.
D
A
C
A
Yep
I
think,
because
that
requires
specific
access
to
the
other
volts,
specific
access
to
a
group
certificates
and
specific
access
to
the
private
key,
which
is
on
a
private
repository
I.
Think
all
the
GitHub
organization,
admin
of
Jenkins
Safra
should
be
able
to
access
the
private
repo
and
all
the
Azure
admin
should
have
so
I
guess,
Stefan
and
elevatorically
could
have
access
to
the
information
but
better
to
check
first
and
follow
up
the
wrong
book.
A
Monitoring
Stefan
to
start
the
work
on
creating
the
new
public
Network
and
then
the
new
public
cluster
I.
Think
public
network
is
almost
already
done
and
then
create
the
new
kubernetes
cluster.
A
E
B
A
Okay,
I
propose,
we
don't
add
it
to
the
Milestone,
no
pressure.
There
are
enough
tasks
back
from
early
days
and
if
you
have
sometimes
both
of
you
I,
let
you
make
discus
and
start
planning,
and
so
then
we
can
start
for.
You
can
start
walking
if
you
feel
like
I,
don't
think
it
I
feel
like
it's
too
much
on
one
milestone.
A
So
let's
see
would
be
here
for
the
other
task.
I,
don't
want
to
put
pressure
that
something
really
sensitive,
so
I
prefer
we
take
time
for
planning
ever.
If
you
feel
like
you
have.
Sometimes
you
can
start
planning
and
writing
down
the
steps
you
feel
like
the
issue
is
that,
okay,
based
on
your
experience
on
the
previous
cluster.
A
Yep
now,
where
should
we
take
it
both
of
us
and
the
first
one.
C
A
It's
kept
without
Milestone,
because
it's
yes
of
of
the
usual
printing,
okay.
A
A
So
thanks
see
each
other
next
week
or
during
the
week
I'm
gonna
stop
recording
and
then
you
will
be
able
to
speak
freely
for
everyone.
Listening
to
us
see
you
next
week,
bye.