►
From YouTube: 2022 12 20 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
Let's
get
started
with
announcements,
so
the
new
weekly
2.383
has
been
released.
Change
log
approved
checklist
in
progress
thanks
for
Mark
for
confirming
we
haven't
deployed
it
yet
on
our
infrastructure.
Neither
checked
for
the
docker
image
we'll
do
after
the
meeting,
but
that's
that
should
be
good.
I,
don't
think
the
change
log
was
you
join
this
one
so.
B
A
C
There's
a
webinar
today
for
webinar
today
just
to
launch
the
Jenkins
project
in
Google
summer
of
code.
C
A
A
Just
a
note
about
the
first
week
of
January
I
will
be
off
and
I
think
everybody
will
be
as
well.
Yes,
so
Stephanie
Stefan
giving
I'm
not
sure.
If
you
will
be
off
this
week,
that
Mark
will
be
there.
C
I'll,
be
there
yeah,
okay
and
I.
Think
Kevin's,
Kevin
I
think
you're
planning
to
be
in
the
first
week
of
January
yep
I'll,
be
here
I'm
only
off
next
week.
So
there
is
one
more
announcement
to
get
plug-in
and
the
get
client
plug-in
are
preparing
for
a
major
version.
Change
and
there's
been
a
request
by
the
get
plug-in.
Maintainer
me
to
have
people
help
tested.
C
C
C
A
So
there
is
no
problem:
if
you
do
it
doing
the
the
two
incoming
weeks.
B
A
C
D
A
A
That's
so
next
weekly
next
week,
even
if
there
is
no
team
meeting,
xlts
will
be
11.
January,
2000
D3
I'm,
not
aware
of
any
security
release.
A
B
A
Okay,
so
let's
proceed:
what
did
we
do
last
week?
That
is
closed,
so,
first
of
all,
Mark
thanks
for
the
fix
and
for
about
the
javadoc
I
confirm
it.
It
works
as
well
on
the
agents
and
on
trusting
where
it's
deployed
so
Mark
pushed
the
fix
on
the
javadoc
Builder
that
under
the
caves
that
we
had
with
that
devops
plugin.
That
has
been
that
has
been
released
for
the
first
time
and
we
don't
know
why,
but
it
generated
an
empty
jar
file
for
the
javadoc
I
assume
everything
was
done
manually.
A
C
So
Damien
I
actually
had
a
question
about
that
one.
If
you're,
okay
with
me,
asking
any
questions
so
one
of
the
things
that
job
does
is
it
creates
a
600
megabyte
archive
and
saves
the
archive
with
an
archive
artifacts
I,
believe
that
means
it
writes
it
to
the
controller
and
over
half
the
total
execution.
Time
of
the
job
is
spent
doing
the
creation
of
that
of
that
archive
the
tar
process,
because
it's
using
a
bzip
correctly
to
compress
the
thing.
C
And
and
see
if,
if
you
look
at
the
next
step
down,
the
next
step
down
is
where
it
gets
shipped
off
to
the
blob
storage,
where
it's
actually
displayed.
Okay,
and
that,
for
me,
is
a
very
reasonable
thing
to
do.
Shipping
it
to
blob
storage
is
perfectly
sensible,
but
on
ci.jenkins.io
we
don't
want
to
do
that,
because
that
requires
credentials
right
and
and
correctly
it
should
require
credentials.
C
A
Okay
proposal,
we
have,
we
recently
walk
with
the
steps
generators
that
generate
also
a
website
based
on
the
source
and
we
Stefan
and
Adriana.
We
discussed
that
the
archive
part
should
be
kept
at
least
on
the
principal
Branch
only
on
cigo.
That
will
mean
we
would
have
the
infrastructed
else
if
infra
is
not
trusted,
meaning
if
it's
run
on
cigar
or
whoever
wants
to
build
it
and
the
Bro
the
it's
not
the
principle
and
it's
the
principal
Branch,
then
we
keep
that
step
only
on
Master,
but
not
on
pull
requests.
D
Makes
it
looks
the
high
interested?
D
C
A
That's
a
good
point
that
everybody's
underlying
there.
If
the
deployment
on
production
only
do
a
kind
of
ersync
like
Rubik's
Affairs
the
same
between
two
sources,
then
it
means
that
we
don't
need
to
First,
zip
without
bc2
and
then
zip
it
a
second
time
to
send
it
to
the
controller.
We
could
just
remove
that
part
and
change
the
RTA
archive
artifact
to
only
archive
the
data
sites.
C
All
right,
okay,
and
that
that
then
would
allow
archive
artifacts
to
do
the
well.
But
won't
that
then
create
a
lot
of
small
files
in
the
artifact.
C
C
A
B
C
A
Next
subjects
thanks
survey,
but
so
thanks
to
a
team,
Alex
and
and
the
both
of
them
for
working
on
updating
a
lot
of
the
Ruby
deponences
used
for
Jenkins
at
your
website,
which
includes
some
repositories
such
as
eskidoctors
and
games,
extensions
required
renovate,
which
is
a
kind
of
Dependable
or
update
CLI
alternative,
which
does
things
in
the
between.
So
it's
easier
for
them
to
use
renovate,
and
they
asked
the
infra
team
to
install
it
on
the
GitHub
organization,
which
we
did,
but
only
focused
on
the
repositories
that
require
renovate.
A
A
good
point,
so
the
thing
is
depend
about,
is
clearly
the
most
efficient,
but
its
scope
is
really
narrow
in
the
case
of
renovo,
but
it's
able
to
track
way
more
dependencies.
It
provide
a
nice
pull
request
way
more.
That's
the
most
useful
I.
Think
of
the
three
and
update
CLI
requires
more
maintenance,
but
is
way
more
powerful.
A
You
can
do
things
more
complicated,
so
it
depends
most
of
the
time
going
for
renovate
will
help
a
lot
but
I'm
I'm
mentioning
that,
because
marker
is
so
that
you
did
the
pull
requests
today
about
updating
pollution,
Maven
version
and
some
tutorials
on
Jenkins
IU.
That
would
be
worth
checking
if
renovo
update,
CLI
couldn't
help
you
on
that
part
by
opening
pull
request
automatically
when
there
is
a
new
Maven
version
or.
D
A
D
A
D
Okay,
because
it
was,
it
was
the
same
kind
of
seeing
you
secretly.
Yes,.
A
So
what
I'm
suggesting
is
that
it's
for
it
most
of
the
time?
It's
you
have
a
kind
of
scope
per
page
or
per
tutorial,
but
since
a
ski
doctor
is
able
to
have
variables,
if
you
are
able
to
at
least
move
the
variables
on
top
of
the
ASCII
doctor,
Source
page,
that
might
already
be
the
case
I'm
not
sure,
then
we
could
use
renovo
or
update
CLI
updates
here,
I'm
sure
it
will
be
able
to
using
a
search
and
replace
pattern.
A
C
D
D
D
A
I
moved
the
script
but
yeah
next
topic,
so
the
maintenance
migration
of
repo
jintensi
was
successful.
Past
Sunday
thanks
survey
for
the
help
Sunday,
so
we
did
not
have
any
issues,
so
that
was
perfect.
Nothing
to
do.
It
looks
like
based
on
what
you
saw
earlier
and
what
Daniel
saw
that
it's
clearly
faster
than
before,
like
at
least
twice
the
the
build
time
when
downloading
artifacts
are
clearly
better,
so
maybe
we
could
we
might.
A
We
might
use
way
more
bond
with
per
month
now,
thanks
to
that,
that
will
be
an
annoying
consequence,
but
no
it's
still
a
good
good
thing.
Yes,
so
no,
we
are
back
to
decrease
bandwidth.
We
will
have
a
meeting
with
you
frog
later
today,
mark
just
to
be
sure
I
assume
it.
It
will
be
to
just
to
summarize
before
and
of
here.
A
A
Support
account
and
see
if
we
have
access
to
the
portal,
so
there
I'm
sure
they
will
give
us
Direction
later
today,
forgot
username
password
account
not
found.
As
usual,
someone
opened
an
issue
for
an
account
that
doesn't
exist
and
then
never
answer
so
closed
has
not
done.
Even
though
we
ask
a
question
CD
failure
on
SM
API
plugin,
you.
A
That's
true
so
issues
on
GitHub
that
made
the
that
require
that
the
GSE
click
in
that
case
had
to
wait
for
five
hours,
but
repository
permission.
Letter
runs
should
run
every
three
hours
successfully
to
update
a
token
that
is
only
valid
for
four,
so
five
hours
means,
if
you
have
the
token
of
that,
is
age
of
five
hours
that
will
be
refused
by
artifactory,
but
that
was
fixed,
then.
So
thanks
to
Daniel
for
helping
on
that
part
and
finally
jenkins.io
components.
D
B
D
Issue
this
type
of
issue,
the
crowding
level,
because
it's
according
to
have
see
it's
for
the
integration
into
crowding.
It's
it
has
nothing
to
do.
We
created
an
blank
blank
issue,
he
didn't
use
any
template,
but
it
was
for
integrating
and
drinking
okay.
So
your
component
into
crowding,
okay.
A
Walk
in
progress
now,
a
word
about
eks
I
had
to
recreate
one
of
the
case
cluster
yesterday
and
spend
on
my
day
doing
that,
because
without
further
warning,
AWS
changed
some
default
parameters
of
eks
cluster
and
I
suffered
from
that,
while
trying
to
upgrade
the
major
version
of
the
terraform
module
that
broke
things
that
made
the
diff.
All
clusters
are
now
private
by
default,
so
you
have
to
explicitly
change
the
default.
A
Right
now,
everything
is
redeployed.
It's
integrated
I
just
did
that
the
certificate
on
repo.aws.10kins.io,
the
local
artifact
caching
proxy.
That's
the
only
application
on
that
cluster.
That's
why
I
want
to
add
that
application
is
now
working
running,
but
without
a
valid
certificate.
I
have
to
check
on
that
one
more.
We
are
trying
to
use
AWS
eks
for
something
else
than
ephemeral,
Play
Store.
Tomorrow
we
have
issue
and
waste
time.
So
at
the
moment
in
time.
A
Maybe
it
might
be
worth
it
to
use
a
a
local
machine
instead
of
that,
but
yeah
we'll
see
just
that's
why
the
air
base
you
just
turned
at
the
beginning.
We
chose
to
use
kubernetes
because
we
want
the
caching
proxy
to
be
the
same
on
every
cloud
where
we
have
a
kubernetes
cluster,
but
that
might
be
worth
it
having
a
virtual
machine.
A
Instead,
I've
opened
an
issue
and
I'm
gonna
update
the
issue
with
all
the
pull
requests
and
commits
I
did
and
changes,
so
it
will
be
auditable
afterwards,
but
I
didn't
have
time
to
do
it
in
real
time
yesterday.
So
work
for
today
and
tomorrow
for
me
consequence
on
cigen
Sayo.
That
was
only
working
with
digitalocean,
so
it
was.
It
had
a
huge
bill
queue
this
morning
due
to
that,
but
now
it's
back
to
normal
a
new
issue
so
that
one
I
keep
for
next
iteration.
A
D
I've
set
the
available
provider
or
global
settings
to
none
so
plugin
use
that
org
by
the
default
every
time
while
I
look
into
it.
A
So
is
there
anyone
against
keeping
it
disabled
for
now
and
moving
the
that
issue
back
to
back
to
the
backlog
until
we
we
have
finished
the
network
and
cluster
migration
stuff
yeah.
A
A
A
So
that
issue
is
not
close,
but
we'll
move
to
the
backlog.
As
soon
as
we
will
be
able
to
answer
to
the
contributor
on
the
Jenkins
CI
Docker
images,
a
pull
request
has
been
open.
I
need
to
try
one
time
that
that
request
bill
with
the
new
label.
It's
only
Windows
2022,
so
it's
an
explicit
label.
If
it
worked,
then
we
can
tell
the
user.
They
can
continue
working
on
their
pull
request
and
that
issue
will
go
back
to
the
backlog.
A
A
That's
a
nightmare
so
right
now,
2019
is
on
Azure
and
AWS.
For
us
and
2022
is
a
neon
azure,
so
Stefan
proposed,
let's
see
how
it
it's
going,
but
maybe
we
might
have
to
only
keep
Azure
as
a
provider
of
Windows
Server
virtual
machines,
at
least
for
the
upcoming
month,
because
we
are
wasting
too
much
time
on
this.
Build.
B
A
Java
netcash
is
no
longer
considered
by
the
update
Center
I've
reopened.
That
issue,
which
is
about
the
Java
Nets
2
repository
on
artifactory,
which
Upstream
is
gone.
There
are
at
least
two
local
repositories,
one
that
I
did
two
days
ago
and
one
which
is
more
ancient.
They
are
private,
not
visible
by
default,
but
both
of
these
have
all
the
artifacts
we
can.
We
should
check
exhaustively
but
I
checked
the
checksum
of
the
global
repository
and
it
looks
really
good.
A
So,
at
least
if
that
repository
is
gone
by
accident,
then
we
could
absolutely
add
it
on
our
tree.
So
we'll
wait
for
Danielle
to
give
us
history
when
he's
back
from
holidays,
so
January
but
yeah,
we
have
at
least
three
copies,
and
we
have
the
old
architecture
instance
migrated
Sunday,
as
a
backup
of
backup
I
wasn't
able
to
find
a
way
to
download
this
artifact
yet
because
all
of
these
repositories
are
private
and
marked
as
blacked
out.
A
D
I've
deployed
on
it
yesterday
or
services,
not
directly
Fortune
keys,
and
today,
I've
deployed
a
controller
on
it
with
Orleans
harder
created.
Thinking
that
your
confusion
except
search,
job
definition,
foreign,
it
seems
to
be
working
but
I,
can't
access
the
instance
I
can
access
I
can
ping
the
machine
from
the
and,
as
in
the
on
the
VPN
machine,
when
I'm
working
with
SSH,
but
going
from
my
brother
with
Aston
Tree
on
my
machine
that
doesn't
work,
we
are
working
on
it.
D
And
the
good
news
is
I
had
to
change
the
credential
name
in
my
factorization
or
having
two
of
us
I
understand
in
our
inside
config,
and
it
didn't
break
the
security.
D
A
A
So,
which
means,
as
soon
as
we're
able
to
fix
that
VPN
issue
and
that
we
can
reach
through
the
new
VPN,
we
will
communicate
about
migrating
the
current
infra
CI
to
that
new
instance.
So
then
we
can
Trash
the
temp
private
Gates
cluster.
A
A
We
also
plan
to
do
a
full
migration,
full
clean
migration,
meaning
we
will
back
up
the
Jenkins
home
and
migrate
it
to
the
empty
instance
that
are
we
created
because
last
time
we
migrated
in
Frasier.
We
didn't
care
about
the
bill
history
we
do
now
because
there
are
other
jobs
in
that
instance,
in
that
controller
that
are
not
infra
related
or
not
directly
to
our
tooling.
A
So
that
will
be
your
next
stepper
way:
nice
job,
because
yeah
that
was
a
lot
of
Shadow
walk,
especially
in
the
network
area,
terraform
area
Azure
and
the
ipv
for
voting
so
really
cool.
To
have
that
part
done
by
someone
else
than
me,
I'm
really
happy
for
that
outcome
of
it.
That's
really
nice
job
foreign.
A
A
So
the
that's
why
I
propose
a
new
issue,
because
the
network
part
for
me
is
finished,
even
though
we
haven't
validated
the
IPv6
part.
So
my
proposal
is
rename
the
issue
and
create
two
sub
issue,
one
to
four
validating
IPv6
later,
because
we
will
have
to
do
it
because
the
huge
work
there
is
is
has
been
done
and
the
VPN
VM
is
not
required
for
the
public
network
because
we
can
use
the
private
VPN
to
reach
through
the
pairing
to
the
public
backends.
A
A
So
if
it's
okay
for
you,
RV
I,
will
create
the
tuition.
I
will
consider
the
current
when
done,
because
you
did
the
scope
of
the
issue
that
was
creating
brand
new
networks
manager
scored
by
terraform
in
the
Azure
net
Repository
and
a
new
VPN,
so
same
set
of
features
we
have
today.
So
for
me,
work
is
done.
A
A
There
has
been
now
an
issue
open
by
giving
about
netley
5
for
Jenkins
your
components
I
need
to
check.
He
created
the
the
initial
handling.
We
will
have
to
look
at
it
for
the
next
iteration
I
assume.
We
need
a
website
deployment
somewhere
and
atlify.
What
is.
D
D
A
A
The
idea
is
to
switch
the
plugin
scoring
application
from
a
GitHub
token
to
a
GitHub
app
the
challenge
we
will
have
to
face
that
will
be
presented
so
for
Jean
Mark
when
collecting
metrics
and
other
scenarios
like
this
one
will
be
I'm,
not
sure
what
is
the
policy
for
the
administrator
of
the
Jenkins
CI
GitHub
organization?
We
are
not
admin
at
least
not
me
not
our
way.
What
is
the
policy
when
they
install
a
GitHub
app
for
managing
thousands
of
repositories
should
only
be
able
to
run
on
the
plugin
Dash
something
Repository.
D
We
are,
we
are
manager
for
obviously
application
on
thinking
CI.
That's
an
admin
has
to
validate
the
requests.
Okay,.
A
A
Person
the
person
in
charge,
who
will
say
yes
and
no
is
Vedic
the
security
officer
and
if
I
would
be
with
Vedic
I
will
say:
I,
don't
care,
you
have
to
partition
the
access
and
I
know
it's
a
pain,
but
that
I
mean
that's
too
risky.
If
there
is
any
private
repository
on
Jenkins
CI,
if
there
is
anything
that
should
not
be
done,
if
you
don't
have
to
you,
don't
have.
A
Exactly
we
will
need
a
process
that
say:
oh
there
is
a
new
plugin,
something
repository
permission.
Updater
could
be
one
of
the
areas
that
could
help,
because
the
goal
of
that
reposit
repository
and
the
build
Associated
is
to
list
all
the
plugins
and
do
stuff,
but
with
that
that
list,
so
that
could
be
a
way
to
automate
it
with
the
current
tooling,
because
we
are
not
alone
having
that
that
kind
of
challenge.
A
We
have
some
Jenkins
mirrors
using
wrong
media
type,
so
it
was
fixed
by
your
cusl
as
we
said
last
week,
and
we
need
to
update
the
Apache
configuration
on
archive
Jenkins
I
totally
forgot
about
this
one.
It
should
be
quite
quick.
A
Murals
within
that
time,
to
check
and
realigned
Jenkins
so
that
one
was
posed
until
the
Heathrow
migration,
so
I
need
again
to
check
if
my
setup
is
still
there
if
it's
still
buggy
or
if
it's
still
eventually
consistent
or
not
I
hope
it
should
not,
and
my
next
step
is
to
try
to
build
a
plugin
with
a
proxy
to
my
test
area.
That
is
completely
an
absolute,
a
different
set
than
what
he's
doing
done
right
now.
That's
the
worst
case
scenario,
but
I
have
to
test
to
start
testing
somewhere
and
I.
A
That
means
I
will
have
a
perfect
setup
to
force
using
everyone
on
the
same
Repository.