►
From YouTube: 2022 11 22 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
infrastructure
weekly
team
meeting.
Today
we
are
the
22
of
November
2022..
So
today
around
the
table,
we
have
your
services.
A
So
that
should
be
your
handle
in
this
course
yep.
Okay,
perfect,
I,
think
the
third
were
one
two,
three,
four,
five:
six
percent.
What
am
I
missing,
I,
don't
know
we
are
five
okay,
so
first
announcement
today
is
the
weekly
release.
So
I,
don't
remember
the
number
I
assume
it's
a
It's,
not
finished
it.
Has
it
had
an
issue
on
the
packaging
step,
so
it's
minor
issue
I'm,
not
sure
why
I'm
showing
the
issue
on
the
screen
right
now
at
the
step,
synchronize
mirror
so
which
is
really
Universal.
A
A
Before
the
we
were
able
to
push
them,
because
everything
initially
lists
the
files,
then
it
has
a
list
of
file
and
say:
okay,
I
will
copy
them
one
after
the
other,
so
one
of
the
files
on
that
list
has
vanished
when
everything
tried
to
copy
it.
Not
sure
why
that's
word,
is
it
the
agent
going
somewhere
else?
Did
the
controller
restarted
I'm,
not
sure
just
survey,
so
you
don't
feel
bad.
It's
not
the
pipeline
utility
step,
because
that
pipeline
is
still
present
on
the
controller.
Unless
you
manually
uninstall
it
and
restarted
the
controller
which.
A
Okay,
so
since
there
is
no
obvious
error
here,
but
the
script
return,
the
naroka
24,
so
I've
kicked
a
new
package
built
because
that
one
is
the
important
that
won't
trigger
a
new
release.
The
relay
has
been
done
by
the
car
build
now
it's
the
core
package.
We
can
retrigger
it
as
much
as
we
want
until
it
works,
so
that
one
is
easy.
A
That's
the
status
of
the
weekly
during
Packaging
pre-packaging
in
progress,
then
Docker
image
and
item
of
the
release.
Checklist.
A
B
A
A
D
Because
otherwise,
our
regular
four-week
clock
would
put
2.375.2
right
between
the
Christmas
holiday
and
the
New
Year's
holiday
for
many
of
us
in
the
western
world,
and
many
of
us
won't
be
available
during
that
time.
So
we
would,
we
will
follow.
I
will
propose
the
usual
pattern
we've
had
in
the
past,
which
was
delay
two
weeks.
A
If
you
need
bad
ideas,
I
have
plenty
thanks
for
the
info
mark:
okay,
cool,
any
other
upcoming
calendar
thing:
nope:
okay,
let's
proceed!
What
have
we
done
during
the
past
week?
Completely
done?
First
containerized
Java,
17,
Windows
agents
that
one
was
long
overdue.
A
We
were
able
to
use
Java
17
on
all
Linux
kind
of
agent
and
on
Windows
Virtual
machines.
However,
the
windows
container
agent
are
the
most
used
for
Windows
builds
and
tests
for
Jenkins,
car
and
plugins.
So
thanks
Stefan
for
taking
care
of
this
one.
The
initial
plan
was
having
all-in-one
image
from
backer
image
for
having
like
Linux
for
having
the
same
thing
between
content
of
a
virtual
machine.
Alas,
we
are
late
on
that
area.
It's
not
that
easy,
because
we
lack
High
skills
on
Windows.
We
have
enough
to
make
it
work,
but
it
takes
time.
A
We
keep
having
a
bunch
of
Jenkins
login
access,
but
the
pattern
change
the
past,
the
the
most
recent
one.
The
people
are
asking
us
to
give
them
the
access
to
the
admin
account
with
the
password
admin.
C
A
A
A
So
is
it
okay
for
everyone?
If
we
continue
seeing
such
as
soon
as
there
is
admin
on
the
username
or
that
the
URL
is
not
one
that
we
manage,
we
can
immediately
cause
the
issue
with
a
message
saying:
hey:
that's
not
the
that's,
not
the
issue
tracker!
You
are
looking
for
I.
A
A
A
So
we
had
to
clean
up
and
archive
this
element.
That
project
has
been
long
gone,
foreign
not
being
run
for
Jenkins
CI,
Bridge
method,
injector.
That
was
a
request
to
add
a
project
to
see
agent
kinsayu
thanks
survey,
more
component
to
Archive,
more
login,
login,
login
backload
of
of
already
built
item
on
CI
Jenkins.
C
We
were
testing
the
instrumental
build
of
work
for
the
task
step,
we've
fixed
from
JC
since
two
weeks
and
since
we
didn't
have
any
issue,
just
emerged,
his
request
and
live
deployed.
This
released
the
question
on
release
on
CIA.
A
A
We
had
a
request,
so
thanks
Stefan,
for
taking
care
of
this
one
GSC
asked
to
install
the
pipeline
GitHub
plugin,
so
the
bomb
project
was
able
to
get
some
additional
pipeline
keyword
from
that
plugin,
specifically
on
the
runman
variable
used
set
by
the
previous
on
GitHub
repositories.
So
thanks,
Stefan
and
finally
key
cloak.
That
was
only
the
cleanup
Stephanie.
Is
that
correct,
yes,
cool?
So
we
should
have
a
few
more
books
on
the
AWS.
Thanks
to
your
work
or.
C
A
C
So
to
see
to
see-
and
he
basically
United
function
we
had
in
the
pipeline
Library
and
you
got
rid
of
the
metadata.
B
C
And
so
easily
now.
C
C
A
No,
no,
no
so
I
think
Jenkins
5
Runner
benefited
from
that
service,
but
it
was
a
service
online
that
we
hosted
and
we
removed
a
few
months
or
years
ago,
where
a
user
at
the
web
UI
and
they
could
download
a
jenkinswa
prepackaged
with
a
set
of
plugins
or
pre-package
with
whatever
settings
you
want,
and
so
the
system
was
in
background
generating
the
zip
and
zip
and
downloading
the
correct
a
bit
like
a
Docker
Custom
Image
as
far
as
I
can
understand
it,
but
that
project
might
have
been
g-soc
I'm,
not
sure
about
that,
but
that
has
been
completely
gone
so
we
removed
it
from
the
infra
last
year.
A
D
Yeah,
it
was
a
Google
summer
of
code
project
and
it's
idle
right
now,
so
it
was
attempting
to
do
that.
I'm,
not
aware
of
anything
that
would
require
us
to
keep
it
running.
If
you
find
it
helpful
to
shut
it
down,
I'm,
not
aware
of
anyone
who's
actively
consuming
it.
C
A
C
A
Custom
wire,
packager,
okay,
thanks
survey
for
that
works,
so
just
a
reminder
for
Everyone
by
removing
that
pipeline
plugin,
which
is
providing
useful
but
dangerous
methods,
because
these
methods
are
pipelined,
so
they
were
run
on
the
controller.
Why?
Most
of
the
time
we
want
to
run
such
element
on
an
agent?
So
sh
should
do
that.
Do
that?
So
if
you
see
a
pipeline
on
the
infrastructure
failing
because
missing
a
keyword
and
that
keyword
happened
to
be
on
that
list,
then
that
means
that
the
pipeline
or
the
pipeline
Library
calling
that
keyword
should
be
changed.
A
A
Oh
okay,
so
let's
move
on
the
currently
being
worked.
Items
walk
in
progress,
I'm
taking
them
on
the
right
list,
separate
terraform,
backend
and
repository
as
your
net
and
azure.
A
That
issue
wasn't
prior
until
today,
or
at
least
until
we
discussed
yesterday
the
as
the
team,
because
we
discovered
that
our
Network
are
not
ipv
V6
compliance.
We
need
to
recreate
all
of
our
networks
and
migrate
or
recreate
resources
to
get
to
the
new
network.
So
we
can
support
at
least
people
from
the
outside
being
able
to
request
infrastructure
in
IPv6.
A
So
that
means
it's
the
correct
opportunity,
since
we
are
working
on
private
cavities
and
then
we
will
have
to
recreate
all
the
all
the
kubernetes
cluster.
We
decided
that
okay,
that
will
delay
a
bit
our
work
on
ACP
on
the
new
cluster,
but
since
we
have
to
migrate
everything
creating
from
scratch
on
new
network
that
are
clean
without
the
mapping
issues
with
IPv6
compatibility,
that
should
be
the
right
moment
to
do
it.
A
So
are
they
what's
the
status
of
that
because
I
gave
the
Y
now
it's
the
what
and
the
how,
where
you're,
able
to
start
working
on
it
or
do?
Are
you.
C
Going
to
I
have
created
a
repository.
I
want
okay,
I'd
like
to.
B
A
A
A
So,
yes,
we
have
to
create
these
resources
and
we
have
to
work
it
out
more
details
on
that
part.
We
already
shared
knowledge
with
the
recording
the
free
Frenchies
from
on
the
room.
Now
we
have
to
translate
that
knowledge
publicly
with
links
on
an
issue.
A
Okay,
next
issue
we
have
on
the
list
on
the
left
is
a
migrate,
alkai,
gen
kinsayo
component
to
Jenkins
Central.
A
C
So,
given
transferred
the
his
concept
of
a
web
component
for
rankings,
are
you
in
drinking
stuff
organization,
I,
haven't
closed
issue
as
I
want
to
put
in
place
the
service
accounts
for
npm?
So
we
you
wouldn't
have
to
put
the
a
personal
token
on
in
the
repository
to
access
the
democrine
type
I.
A
A
For
adding
npm
service
account,
okay,
thanks
for
the
status,
any
question,
clarification
on
that
topic:
nope,
okay,
next
one
publish
pipeline
step,
dog
generator
and
back-end
extension,
indexer
artifact
to
some
kind
of
storage,
so
the
name
is
misleading,
because
the
core
of
the
tissue
has
already
been
done
since
two
weeks.
Now
we
don't
need
CI,
Jenkins
IO
to
be
up
in
order
to
generate
the
jenkins.io
website,
which
is
a
nice
thing
for
the
security
team.
A
Whatever
information
to
generate
these
pages,
however,
we
migrated,
so
we
fixed
that
by
migrating
the
pipeline
in
infrasti,
because
we
need
a
private
credential.
That
must
not
be
on
cigar
publicly
and
that
credential
required
us
to
move
the
pipeline
to
infrastia
at
first
step,
but
we
forgot
and
that
we
have
been
reminded
by
Danielle
and
Tim
thanks
for
that,
that
end
user
still
wants
or
should
be
able
to
contribute
to
these
two
projects,
so
they
need
a
publicly
available
CI,
which
means
at
least
build
and
test
on
this
project.
A
B
B
Am
I
started
by
the
first
one
pipeline,
step,
dog
generator
and
and
in
order
to
add
them
to
have
it
to
work
fluently
on
cin
infra
I
had
to
do
two
distinct
PR
to
have
the
same
label
for
the
agent
on
CI
and
the
other
one
on
Alpha
and
like
that,
we
can
switch
back
and
forth
between
the
two
of
them.
That's
compatible.
A
B
A
A
Let
me
clean
up
so
that
one
okay,
so
the
next.
The
next
item
on
my
left
list
is
stories
is
not
only
pull
requests
so
I've
already
I
finished
the
work.
So
that's
the
same
idea.
We
need
both
public
and
private.
In
fascia,
it
deploys
previews
websites
on
pull
request,
but
also
deploy
the
main
website
on
netlify.
So
it
has
specific
credential.
It
must
be
private,
still
cig
and
Kim,
so
you
need
to
at
least
build
linked
and
test
the
projects
publicly.
A
So
the
the
unifying
work
has
been
done
by
Stefan
and
I
in
per
so
that
Stefan
is
now
autonomous
to
do
the
two
others,
as
we
just
did
I've
eat
I
was
about
I
was
almost
closing
the
issue,
but
I
would
eat
an
issue.
An
infra
CI,
the
size
of
our
virtual
machine
on
the
kubernetes
cluster
is
a
bit
too
small
compared
to
the
amount
of
resource
that
we
require
in
the
case
of
cigen
Kim
Sayo.
We
have
big
machines
where
we
pack
a
lot
of
PODS.
A
A
A
So
I'm
adding
it
to
the
next
iteration
that
should
be
okay.
Unless
there
is
a
question,
okay,
you
need
clarification
on
that
one
nope,
let's
continue
next
issue-
is
remove
windows
slave
plugin
from
cigion
related
server,
so
Mark
I.
Remember
that
you
you
remove
the
Plugin
or
you
checked
at
least
it
wasn't
installed
on
our
Docker
image.
Is
that
correct,
I.
D
A
Yeah,
since
we
had,
we
had
the
warning
issue,
while
I
was
upgrading
plugins
on
cig
and
Sayo.
That
was
the
opportunity
during
a
restart
to
test.
So
I
took
the
opportunity.
D
Infra
I'm
not
aware
of
anything
if
we
discover
some
reason,
but
that
we
can't
remove
it
one
of
the
problems
of
can't
remove.
It
is
because
it
has
such
an
ancient
Jenkins
Baseline.
It
can
create
an
implied
dependency
on
other
ancient
plugins
or
other
engine
plugins
create
an
implied
dependency
on
it.
So
if
we
have
any
ancient
plugins,
my
first
preference
would
be
get
rid
of
them
too.
A
Do
you
think
you
will
be
able
to
continue
the
last
check
of
the
controller?
Do
you
want
to
delegate
it
to
the
team
for
that
specific
issue.
A
Thanks
a
lot
so
one
last
check
of
all
controllers
before
closing,
if
in
please
see
dependency
from
another
plugin
ping
mark
or
a
plug-in
release
to
help
any
question,
any
clarification.
A
C
So
reasons
because
we
so
I
I
wanted
to
make
a
review
of
series
to
scorpion
as
you,
and
so
we
created
this
issue,
so
we
can
do
for
our
cleanup,
depending
on
what
we
reviewed
and
the
first
review
we
made
we've
made
was
about
the
product
conference
process
group.
There
was
two
database.
C
C
C
C
A
Done,
okay,
cool
and
so
I'm
giving
the
statues
about
the
proud
Community
function.
A
We
so
it's
in
the
list
to
be
cleaned
up,
because
we
decided,
after
confirming
with
at
least
team
I,
think
Morrow
can
give
in
that.
The
repository
could
be
archived
because
it
was
used
only
for
Evergreen.
So
in
Azure
we
have
a
resource
Group
with
Azure
function,
including
this
one,
but
also
some
infra
function.
A
So
I
have
to
send
an
email
on
the
mailing
list,
but
the
developer
mailing
list
just
to
be
sure
that
no
one
is
using
this
function,
because
we
saw
some
a
few
goals
like
one
to
four
on
the
past
months,
but
just
a
few.
So
we
just
to
be
sure
that
it's
not
used
for
statistic
generation
or
something
we
don't.
We
are
not
aware
of,
because
once
we
have
deleted
this
Resource
Group,
we
cannot
go
back
because
there
are
data
on
some
repositories.
So
the
goal
is
to
ask
before
delete
the
cost
of
this.
A
C
A
A
D
A
Okay
cool,
so
moral
issues,
I'm
adding
this
issue
to
the
next
milestone
and
as
explained
by
RV,
we
will
try
right
now,
weekly
and
then
monthly
in
the
future,
just
to
review
the
resource
Group
under
role
in
Azure,
just
to
be
sure
that
we
don't
have
some
dormant
resources
consuming
US
money
thanks
everybody
for
leading
that
any
question
clarification,
nope,
okay,
Windows
agent
on
ciao
disconnect
prematurely
I
looked.
We
were
done
with
this
one.
It's
the
9.2
yeah,
because
the
last
step
for
Stefan
was
to
remove
the
Windows
label
on
the
agent.
A
Stefan,
it's
allocated
to
use
it
okay
to
work
on
it.
Next.
A
A
Next
is
the
private,
the
new
private
AWS
cluster
so
before
asking
RV
for
status
because
you
worked
on
it
until
the
the
discussion
around
the
networks,
so
that
one
won't
be
moved
to
the
next
iteration
because
it
it's
obviously
now
we
know
that
it's
blocked
by
the
creation
of
the
new
network,
so
I've
already
did
the
EV
lifting
of
that.
So
we
have
a
cluster
already
on
our
current
private
Network
it
it's
almost
working.
A
A
lot
of
work
was
done,
it's
terraform
manage,
which
is
the
value
of
the
task,
so
we
should
be
able
to
recreate
it
easily
one
who
will
have
the
new
Networks
so
Airway.
First
of
all,
can
you
give
us
a
status
assuming
that
if
we
don't
have
the
network
issue
and
we
were
able
to
migrate,
did
you
have
blockers
next
step
to
be
done
so
delayed,
but
to
be
done.
A
Proposal
since
that
issue
is
the
prioritized
in
favor
of
the
private
Network.
Is
it
okay
for
you?
If,
first,
we
move
back
the
that's
associated
the
pull
request
on
kubernetes
management
back
to
draft
this.
C
A
C
With
the
what
would
be
nice,
it's
not
so
beautiful
nothing
but
merging
this
one.
I
can't
repair
the
next
one
with
use
the
version
of
half
between
the
Tom
private
and
the
public
and
private
star.
Even
if
it's
not
yet
I
I
would
have
my
pull
request
for
the
next
step,
ready
I'm.
Still,
it's
still
an
extract
from
my
first
pull
request,
which
was
recruiting
everything.
A
Hence
my
proposal
to
move
it
back
to
draft,
not
closing
it.
So
it's
still
there.
We
don't
close
your
work,
but
since
we
are
going
to
trash
the
cluster
for
not
paying
it,
that
will
not
make
sense
to
merge.
It
is
that
I
don't
want
to
merge
it,
but
I
want
to
keep
it.
Is
it.
C
A
So
okay
I
understand,
but
then,
if
we
merge
it,
then
you
will
have
to
open
one
pull
request
on
terraform
to
this
to
remove
the
cluster
and
second,
you
will
open
a
second
pull
request
on
that
repo
to
remove
private
gates
from
tentative
of
being
deployed.
Otherwise,
if
we
destroy
the
cluster,
we
will
fail
the
kubernetes
management
job.
That's
why
yeah.
C
A
A
A
So,
just
sorry,
moving
to
infrasync
next
and
I
will
add
a
command
explaining
why
the
last
item
is
realign
repo,
Jenkins,
CI,
org
Mission,
so
Mark
and
I
have
spent
some
time
yesterday.
We
will
right
after
that
meeting
first
thing
is
that
artifactory
is
eventually
consistent.
Sounds
like
Daniel
confirmed
that
when
you
create
a
new
virtual
Repository,
sometimes
it
works.
Sometimes
it
doesn't.
At
least
the
system
says
it's
created
successfully,
but
then
you
have
random,
depending
on
the
distributed
instance
that
you
eat.
A
A
So
we
are
doing
technical
POC
work,
we're
not
touching
the
existing
things.
We
are
only
creating
virtual
repositories
on
the
site
to
confirm
what
are
the
scenarios
once
we
have
confirmed
one
way
or
the
other
Mark
is
currently
finishing
and
should
let
me
write
The
Proposal
with
the
aggression
path
and
the
next
step
for
me
will
be
to
work
on
ldap
replication.
So
at
least
we
could
have
a
randomly
replicate,
ideally
active
active.
So
then
the
additional
request
flow
shouldn't
break
the
end
up.
A
A
B
A
A
C
C
A
C
C
Mentioned
something
I
I'd
like
to
is
it's
to
have
a
Link
Road
director,
from
which
we
will
be
able
to
have
some
statistic
like
a
number
of
freak,
because
we
for
now
when
we
are
publishing
something
on
Twitter
or
on
nicotine
or
anything
there
isn't
any
stats
on
this
click,
and
we
don't
see
said
then.
Yes,
Daniel
said
we
don't.
Even
we
don't
know
if
people
are
clicking
on
this
tweet
or
not,
we
don't
know
if
there's
a
near
patterns
or
not
to
have
some
visibility.
C
You
know
media
application,
not
only
major
publication,
but
that.
C
Nothing
relative
to
something
really
simple:
yeah.
B
Just
I
I
don't
want
to
record.
A
Yeah,
so
that's
why
a
simple
thing
could
help
yeah.
So
do
you
mind
so
do
you
think
it
should
be.
C
I
I
think
I'll
open
an
issue
proposing
a
Quinter
or
something
a.
A
A
A
I,
don't
know,
but
that's
really
a
good
idea
and
thanks
for
mentioning
the
topic
during
the
meeting
I
think
the
outcome
will
be
writing
an
issue
with
that
idea
and
sharing
it
with
the
advocate
csig
asynchronously,
asynchronously,
opic
I
assume
it
has
been
discussed
so
I'm,
just
just
a
beginner
here,
but
yeah
looks
really
good
idea
on
a
lot
of
media
and
yeah.
If
you
are
able
to
write
it,
that
could
be
a
service
or
student
infrastructure
with
Anonymous
data
that
you
cool.
A
A
B
We
had
a
warning,
but
something
let
me
let
me
find
that
there
was
something
that
I
mentioned,
that
we
need
to
be
careful
of,
but
I
forgot
to
say.
A
A
Subject:
area
networks
because
there
is
a
host
name
directly
inside
g-frog
namespace,
and
we
also
have
repo
Jenkins
CI,
so
the
certificate
should
cover
both
us
name.
At
least
we
should
we
can
get
this
the
Suns
from
the
Quran
certificate,
so
the
issue
will
require
me
or
anyone
writing
it
to
Deep
dive
on
the
description
that
happened
last
year
took
some
time
to
KK,
so
I
proposed
this
year.
We
will
do
the
certificate
Renewal
by
ourselves.
A
We
should
be
able
to
do
it
either
manually
or
from
kubernetes,
with
DNS
records
with
let's
encrypt
should
be
hazier
and
Mark
and
I
have
a
meeting
with
g
frog
next
week,
if
I'm
correct,
so
we
will
take
care
of
mentioning
it.
We
will
have
to
not
forget
it
Mark
to
tell
them
hey.
A
D
D
D
2023.,
okay,
and
as
far
as
I
know,
both
both
are
automated.
If
we
get
under
28
days
and
those
have
not
been
renewed,
I
will
start
knocking
on
Tyler's
door
to
to
under
to
see
hey.
What's
up
with
the
automation,
do
we
need
to
shift
it?
The
last
time
I
asked
him.
His
answer
is
I.
Don't
want
to
bother
Shifting
the
automation
Etc.
It
lets
you
sort
of
keep
running.
A
Okay,
so
I
will
take
care
of
adding
Team
calendar
event
for
20
day
before
each.
So
the
word
team
will
have
reminder.
Oh.
A
So
you
don't
know
Tyler,
that's
that's
why
you're
joking
yeah
trust
me,
you
don't
like
to
try
bother
him
he's
clearly
better
a
nastier
than
the
four
of
us.
Okay.
He
has
been
my
my
manager
for
some
time,
Olivia's
manager,
yeah
and
Mark
manager
as
well.
A
He
has
quite
the
sense
of
remark
thanks
Taylor,
if
one
day
by
by
any
means
you
listen
to
this
world.
Thanks
for
the
work
you
are
doing,
for
the
Champions
project.