►
From YouTube: 2022 12 13 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
B
A
Oh
yeah
wow
flash
thanks
hello
Kevin,
so
that
Weekly
is
currently
okay
in
term
of
package
where
file
Docker
image.
I
assume
that
the
change
log
is
being
reviewed,
if
not
already
done
so.
Everything.
A
Next
announcement
just
a
reminder
that
between
Christmas
and
New
Year's
Eve,
no
one
will
be
in
the
area,
at
least
on
the
European
and
Western
countries
in
the
world.
So
let's
assume
that
we
won't
run
the
meeting
the
26th
of
December.
C
A
I'm,
adding
an
announcements,
this
Sunday
19th
of
December,
.jenkins,
ca.org
artifact,
or
instance,
sponsored
by
g-frog
for
us,
we'll
be
down
which
means
old
buildings
here
in
Kentucky
will
be
cute
and
no
one
will
be
able
to
build
Jenkins
plugin
in
the
world
or
a
Jenkins
release
or
any
of
the
components
during
the
downtime.
B
A
A
Trusted
will
be
failing
and
as
soon
as
the
everything
will
be
back
down,
trusted
will
be
back
again.
Maybe
it
could
be
smart
to
put
trusted
CI
in
maintenance
mode
as
well
or
even
shut
it
down.
Just
to
be
sure
that
if
we
start
to
have
weird
artifacts
that
we
don't
generate
Update
Center,
where
it
builds
work.
C
C
So
that's
I
think
that's
a
question
worth
asking
to
Daniel,
because
there
were
some
timing:
timing
related
things
around
Update
Center
that
caused
us
to
make
sure
that
it
ran
very
very
frequently-
and
in
this
case
it
could
be
down
for
six
hours
and
and
the
question
to
Daniel
is
what's
the
impact.
If
it
is
down
for
six
hours,
do
we
have
impact
on
Jenkins
controllers
worldwide,
Etc.
A
A
Last
time
we
had
a
general
issue
with
the
update
Center
requested
for
20
hours,
so
the
only
people
annoyed
are
us
and
plugin
maintainer.
We
want
their
release
to
be
released
so
for
the
second
group
of
people
they
should
be
reading
the
mailing
list.
A
We
have
a
blog
post,
so
I'm
not
sure
how
we
can
contact
them
eventually
may
eventually
Community
but
yeah,
and
for
us
it
will
be
pager
Duty.
That
is
monitoring
the
age
of
the
latest,
build
of
the
update
center.json
file,
which
will
be
clearly
far
more
than
six
hours.
But
yes,
you're,
you're,
correct
gotta
check
with
Daniel.
B
Remember
correctly,
there
is
even
a
process
to
follow
to
get
back
for
the
if
it's,
if
it's
too
late
on
automatic,
is
it's
a
few
hours
and
and
if
it's
more
than
that,
you
have
a
manual
process
to
to
follow
that
we
got
somewhere
absolutely.
D
A
D
E
Had
I
just
had
one
note
real
quickly:
Damian
I
just
remembered
that
I
have
not
submitted
a
tree
proposal
for
the
jfrog
blog
post,
so
I'm
actually
gonna
submit
that
to
the
advocacy
and
Outreach
Gator
channel
so
that
we
can
get
a
tweet
out
for
the
blog
post
as
well.
C
Well-
and
we
should
we
should
probably
tweet
that
again
or
we
should
we
should
send
another
announcement
Friday
and
then
anybody
who's
awake
at
the
time
they
started
could
do,
could
ask
for
the
similar
thing
on
Sunday
I'm,
not
sure
I'll
be
awake
at
the
time
they
start
do.
We
do
we
have
a
state
of
time
yet
Damian
or
is
that.
A
No,
no
any
answer
so
I
will
try
to
send
them
a
ping.
Today
we
don't
know
what
will
be
the
time
window,
so
I
assume
all
day
long.
So
yes,
that
might
be
a
surprise,
we'll
see.
A
Thanks
folks,
what
about
calendar
so
next
weekly
release
as
usual
next
Tuesday,
so
that
will
be
20
December
2022.
A
next
LTS
really
easiest
plan
for
the
11th
of
January
I'm,
not
aware
of
any
security
release
and
next
major
event
or
the
Box
first
them.
As
far.
D
D
A
A
Okay,
a
word
about
the
work
that
has
been
done,
so
we
close
the
one
issue
that
looks
for
me
an
obvious
fishing
attempt,
because
the
person
created
their
account
like
a
few
days
ago,
one
or
two
days
ago
before
never
did
anything
on
GitHub,
but
the
email
is
absolutely
not
the
correct
one.
A
A
It
might
be
a
mistake
if
I
did
I
apologize
in
advance,
but
right
now
it's
yeah.
It
feels
weird
Java
19
support
thanks
Stefan,
so
Java
19
is
generally
available
for
everyday
bloopers
on
cig
and
kinsayu,
and
also
on
every
virtual
machine
of
the
infrastructure
that
are
used
as
build
agents.
A
So
reminder
that
this
chidiga
is
not
LTS,
so
it
will
be
the
prosecuted
in
I.
Think
it's
three
or
six
weeks
a
bit
we'll
talk
about
that
a
bit
later.
There
is
a
new
subject
on
that
topic,
but
right
now
it's
available.
So
thanks
Stefan
for
for
that
work,
Christmas
gift
in
advance,
a
remote
movement
rename
of
Jenkins
Central
government's
meeting.
So
that's
the
website
meetings.jenkinsi.org
there.
There
has
been
some
misunderstanding.
So
now
it's
backed
with
original
state.
A
Just
a
note
for
everyone.
When
GitHub
page
refused
to
use
a
custom
domain,
you
have
to
validate
the
custom
domain
by
putting
a
DNS
record
generated
by
GitHub,
but
please
be
aware
that
when
you
validate
a
domain
in
GitHub,
there
are
free
location
where
you
can
validate
one
and
it's
easy
to
do
the
mistake.
So
thanks
the
guitar,
the
GitHub
support
for
helping
me
on
this
one.
You
can
go
to
your
account
and
there
is
a
security
area
with
verified
domain,
but
only
for
your
accounts
and
the
repository
of
your
accounts
and
your
folks.
A
You
can
go
to
your
organization,
security
settings
and
verify
domain,
but
that
one
doesn't
work
for
GitHub
Pages.
You
need
to
go
to
your
organization,
settings
Pages,
section,
subsection
validate
domain,
and
here
you
have
to
have
verified
the
domain
with
DNS
took
me
some
time
to
understand
that
and
the
tickets
to
the
GitHub
support,
but
now
it's
back
online,
so
the
repository
has
been
renamed
thanks
for
the
proposal,
Fairway.
A
Based
on
the
misunderstanding
of
the
discussion
that
we
propose
to
make
it
explicit
that
it's
an
archive
and
now
for
the
there
is
another
issue
opened
we'll
talk
about
that.
The
board
is
in
the
board
members
area,
so
they
decide
if
they
want
a
new
repository.
This
one,
but
yeah
discussion
need
to
happen
before
we
Act.
C
It
was
discussed
in
board
meeting
on
yesterday
Monday
and
decided
that
we
would
continue
the
discussion
in
the
GitHub
issue.
To
be
sure,
we
understand
we
have
all
the
right
context.
I
didn't
bring
enough
context
to
the
board
meeting
to
have
a
good
discussion
there,
but
the
board
members
that
were
in
attendance
me
Uli
Alex
yeah,
the
three
of
us
agreed.
We
would
continue
the
discussion
there.
C
A
That
that's
not
the
meaning
it's
more!
If
it
can
avoid
good
taking
too
much
time
and
I.
D
A
A
To
be
sure
that
no
one
acts
too
fast
right,
not
not
a
problem,
but
this
I
I
think
we
are
a
few
who
did
not
evaluate
correctly
to
some
Civic
DVD
of
that
topic.
I
wouldn't
have
guessed
so
I
prefer
having
a
long
discussion,
even
if
it
takes
time
and
then
it
will
be
okay
for
everyone.
Consensus
is
key
for
that
specific
topic.
A
A
Account
Jenkins
does
not
have
HTTP
500
errors,
thanks
Tim.
For
that
part,
that
was
also
the
opportunity
to
Archive
another
repository
and
the
component
inside
our
system.
The
error
was
due
to
a
former
component
in
charge
of
synchronizing
ldap
with
jira,
but
since
Shira
is
on
the
CDF,
it's
at
least
two
years,
it's
automatically
done
on
jira's
sites,
so
it
wasn't
used
anymore.
So,
thanks
Tim
for
the
helper
on
the
cleanup
there.
A
We
had
an
issue
with
Windows
Virtual
Machine
for
cig
and
kids
IU
agent,
failing
that
has
been
fixed
thanks
Stefan,
for
for
the
the
help
on
that
one,
we
had
a
short
term
and
long-term
fix.
It
was
due
to
templating-
and
here
just
a
note
for
the
person
following
on
the
platform
Sig
meeting
the
windows.
Container
agents
for
inbound
or
for
inbound
agents
have
a
different
slightly
different
Behavior
than
the
rest
because
of
the
way
Powershell
and
the
entry
point
script
are
parsing
the
arguments.
A
It
sounds
like
it's
a
tricky
topic
because
the
shellan
interpolating
parameters,
but
what
bother
me
as
a
administrator
and
users
is
that
the
behavior
is
different
between
virtual
machines
and
under
container,
so
I'm,
not
sure
how
the
virtual
machine
or
handling
that
part
could
be,
could
be
interesting
to
mention
that
I'm
also
maintainer
of
the
inbound
agent,
so
I
can
take
part
but
important
to
share
the
topic.
A
Various
plugin
downloads
fail
with
HTTP
response.
So
when
we
have
found
an
issue
on
mirror
bits,
it's
not
really
an
issue
because
there
is
no
documentation,
but
it
seems
like
to
be
a
normal
behavior
based
on
the
reading.
The
code,
when
you
remove
a
mirror
there
is.
There
is
a
short
outage
of
a
few
seconds
that
can
extend
to
one
minute
the
time.
That's
the
reduce
system
propagates
to
all
replicas
inside
the
cluster.
A
That's
what
happened
when
RV
cleaned
up
former
murals
we
didn't
know,
and
so
it
generated
HTTP
500
for
some
people,
downloading
plugins.
A
That
mean
we
might
need
to
have
to
write
the
Run
books
next
time.
We
have
to
delete
it's
not
the
case
when
you
update
or
create,
but
when
you
have
to
remove
a
mirror
from
the
list.
First,
the
first
thing
would
be
to
scale
down
to
only
one
replica.
The
cluster
apply
the
change
and
scale
up
again,
just
to
be
sure
that
everything
that,
even
if
there
is
an
issue,
it
doesn't
take
so
much
time,
it's
eventually
consistent.
A
A
We
have
renewed
the
certificate
for
repojenkinsi.org
prior
to
the
migration,
thanks
kosuke,
who
immediately
provided
a
certificate
for
one
year,
so
that
one
is
okay
and
G4
is
aware
not
able
to
Fork
Jenkins
repository.
So
we
were
just
waiting
for
confirmation
by
the
contributor
which
they
did
HPI
file
in
artifactory.
So
it's
a
brand
new
plugin
and
the
brand
new
plugin
are
the
issues,
multiple
issues,
so
some
part
of
the
documentation
were
weren't.
A
There
were
some
holes
in
the
plug-in
developer,
documentation
as
I
understand
in
the
area
of
Gradle
because
they
use
Gradle
for
building.
So
we
raise
the
topic.
Their
initial
release
has
been
is
out,
they
need
to-
or
at
least
they
should
move
to
Maven
in
order
to
benefit
from
automatic
documentation
on
plugin
Jenkins
IO,
and
there
has
been
an
issue
on
the
javadoc
due
to
that
plugin
I
will
I
have
an
open
issue
on
a
few
minutes.
A
Cleaner
process
of
product
conference,
that
was,
that
was
a
bit
of
money.
So
thanks
survey
for
that
work,
so
the
we
have
set
up
a
dump
of
the
database,
which
is
inside
the
Azure
bucket.
That
dump
is
encrypted
with
the
gpg
key
of
a
few
percent
here
and
it's
inside
an
encrypted
bucket,
which
is
private.
We
have
different
layer
of
security.
The
reason
is
because
conference
had
the
security
section.
A
A
C
Checking
to
be
sure,
I
remember
which
ones
it
is
that
are
yes,
so
Jenkins
Dash,
no
jenkins-ci.org
has
been
renewed.
Jenkins.Io
will
be
renewed,
probably
within
the
next
16
or
17
days.
E
C
F
A
Problem
new
items
we
had
a
short
outage
on
the
agent
in
say
earlier
today
showed
that
and
Pedro
Duty
and
a
few
persons
like
Stefan
and
high
are
the
proxy
heroes
from
the
Apache
in
front
of
cig
and
games
IO.
A
So
we
statues
was
updated
and
updated
back
once
was
back.
We
have
an
issue
to
open
to
put
what
we
did.
No
abuse
error.
We
saw
a
peak
in
network
traffic,
a
lot
of
incoming
connection
and
outbound
traffic
as
well
a
lot
of
system,
CPU
usage,
so
not
I.
Oh,
nor
are
you.
Nor
are
you
big
at
all,
so
it
was
definitively
CPU
waiting
for
network
resources.
So
we
checked
the
logs
of
Jenkins.
Nothing.
We
check
thoughtfully
the
Apache
error
logs.
A
Nothing
word
no
word
request
on
the
access
log
as
well,
so
we
are
not
really
sure
what
happened.
That's
that
spawn
for
four
four
or
five
minutes.
We
can
see
that
clearly
on
data
dog,
so
we
will
open
an
issue.
Put
everything
there
and
I
think
I'm
we
need.
We
will
need
a
to
ask
the
security
team
just
for
double
check,
just
to
be
sure
to
see
what
happened,
but
in
terms
of
infrastructure.
Nothing
obvious.
C
Yeah
I'm
I've
been
helping
with
the
bomb
maintenance
and
I've
been
thoroughly
impressed
with
how
well
Ciara
jenkins.io
there
have
been
times
I.
Think
I've,
seen
cues
of
over
800
and
I
may
have
seen
cues
of
over
a
thousand,
and
it
still
survived.
So
yes,.
A
A
Network
connection,
so
something
we
have
in
mind
here
for
sea
agent,
Kim
Sayo,
is
that
the
tuning
of
the
Apache
server
is
not
not
always
the
best.
It
doesn't
have
caching
of
static
assets,
for
instance,
but
one
of
the
element
here,
we
are
not
sure
that
it
was
Apache
that
a
dog
does
not
show
something
abuse.
A
A
So
I've
I've
checked
because
of
an
issue
with
the
mirror.
So
there
is
a
so
first
of
all,
I've
introduced
everyone
from
the
team,
Atlas
Mark
Stefan
Irvin
High,
because
they
were
still
linked
to
Taylor
for
them.
So
even
Olivier
was
an
unknown
person
as
I
understand
the
email,
but
I
might
be
wrong.
First
of
all,
checked
in
with
them
I'm
gonna
run
book
to
write.
A
A
B
A
C
Right
they
they
have
facilities,
they
have
power,
PC
for
sure
available,
I'm,
not
sure
about
Mainframe,
but
they
have
power,
PC
available
for
sure
and
and
IBM
pointed
us
to
power
to
osus
OSU
OSL.
If
we
needed
them,
but
I
don't
see
enough
interest
in
supporting
that
architecture.
So
we're
we're
not
going
to
bother.
A
D
A
Interest
for
Jenkins
project,
so
the
reason
I'm
mentioning
that
I
shared
with
Bruno.
That
could
be
interesting
to
contact
them
for
other
architectures
because
they
also
have
irm,
CPUs
and
I
assume
they
could
be
interested
if
they
are
not
already
providing
a
risk.
Five
machines
as
well.
That
could
be
something
to
check
with
them.
D
We'll
do
yeah.
A
So
that
could
be
interesting
if
we
want
to
provide,
let's
say
on
the
age
agents
for
CI
Jenkins
IU.
If
you
want
to
validate
regularly
plugins
search
engines
Quran.
So
that's
relative
to
infrastructure,
USL.
A
Okay,
so
we
have
the
issue
there,
I
won't
repeat
so:
Sunday
we
are
going
to
migrate.
Repo
Jenkins
g
frog
is
going
to
migrate.
For
us
the
instance.
A
Everything
is
on
the
issue,
a
word
about
gdka
depreciations,
so
we
have
two
GDK
depreciations
to
discuss,
or
at
least
to
mention
first
gdka
8..
So
we
are
inside
the
critical
area,
which
is
how
to
make
the
life
of
plugin
developers
easier.
A
It's
been
sometimes
that
we
don't
that
there
were
some
I
forgot.
The
word
differences,
let's
say,
between
what
the
documentation
and
tutorial
for
plug-in
developer
says
what
the
maven
archetypes
used
to
generate
new
plugin
project
from
Maven
and
what
the
documentation
of
the
shared
Library
maintained
by
the
infrastructure
are
saying.
We
have
free.
We
had
three
different
ways:
one
of
the
main
issues
that
for
sometimes
quite
some
times
we
try
to
go
on
just
call
the
function
and
let
the
default
value
take
place,
which
was
fine
until
we
reached
the
gdka
depreciation.
A
A
There
is
no
easy
consensus
there,
but
one
of
the
direction
that
everyone
agrees
on
will
be
having
a
walk
to
be
sure
that
build
plugin
function,
starting
from
this
week,
should
not
be
called
with
the
default
value
to
avoid
byte
surprises,
because
if
everything
is
explicit
at
least
the
list
of
platform,
you
want
to
build
your
plugin
and
test
it
against.
Then
you
should
avoid
surprise
in
the
future
and
we
could
change
so
maybe
removing
a
default
value
could
be
something.
G
I,
don't
think
that's
our
job,
but
would
it
be
possible
to
have
something
automatically
send
a
PR
yeah.
D
A
Go
a
great
I've,
explained
I
plan
to.
F
To
create
a
pro
request
on
every
plugin
which
have
an
empty
build
plugin
to
put
a
complete
one
from
the
archetype,
so
two
main
advantage
doing
that.
First,
we
will
be
able
to
Define
this
to
eliminate
sticker
8.
Then
we
will
be
able
also
to
to
determine
which
plugins
are
using
the
care
in
a
way
which
isn't
compatible
with
use
container
plugin.
F
Will
you
and
then
identifying
this
plugin?
We
can
then
put
false
for
this
value,
for
this
plugin
only
and
then
make
these
values
the
default
when
the
build
plugin.
So
you
won't
have
to
put
use
container
in
every
ranking
file
if
you
don't
need
to
to
not
use
it
actually.
Currently,
we
can't
put
this
value
as
a
default,
as
we
don't
know
which
plugin
will
break,
but
putting
is
a
default,
build
plugin
template
without
asked.
We
don't
face
and
fix
them.
F
A
Why
it's
on
the
area
of
the
infrastructure-
because
we
already
did
that
because
the
infrastructure
team
is
partially
responsible
of
the
shared
Library
Bill
Brigade,
because
that
plugin
is
at
the
interface
between
people
who
provide
abstraction
for
building
plugin
in
a
reproducible
way,
interface
of
plugin
developers
and
contributors
and
infrastructure,
because
when
you
call
build
plugin
that
has
an
impact
on
the
infrastructure.
You
need
to
spawn
the
correct
agent
there.
A
It
wasn't,
for
instance,
Bill
begin
can
be
called
with
use,
container,
Agents
Set
to
false
or
true
it's
true
by
default,
as
far
as
I
can
tell.
But
if
you
have
a
plugin
with
a
maven
process
that
runs
Docker
for
its
tests
during
the
maven
verify
phase,
you
need
to
change
the
default
value
to
run
your
test
on
the
virtual
machine
instead
of
a
container,
because
you
cannot
run
Docker
inside
the
container.
A
It's
not
a
safe.
Technically
it
work,
but
it's
not
safe
at
all.
So
that's
why
we
forbid
that,
on
the
platform
also
build
plugin
defines
the
labels
that
we
prove
that
we
use
to
spawn
machines,
so
Stefan
started
to
work
on
gdka
19..
So
this
is
an
area
where
we
have
to
work
on.
We
have
to
change
the
label
and
clean
them
up,
based
on
what
we
provide
on
cig
and
Kim
Sayo.
A
So
that's
why
the
topic
is
sensitive
and
why
we,
it
took
us
as
a
community
so
much
time,
because
there
are
different
areas
of
responsibilities
and
we
have
to
all
agree
before
moving
on
to
that
area.
That's
why
here,
since
we
already
did
the
batch
of
pull
request,
exercises
infrastructure
team
with
the
help
of
RV
and
Alex
as
far
as
I
can
remember,
we
should
be
able
to
easily
do
that
to
avoid
the
pain
for
the
others.
That's
somehow
part
of
the
services
that
we
provide
as
infrastructure
team.
A
That
will
be
a
good
exercise
for
us
if
we
need
to
check
which
plugin
is
using
virtual
machines,
I
need
Docker
and
which
isn't
or
any
kind
any
kind
of
metrics
collection
or
behavior
collection
from
the
old
plugin,
the
1000
plugin.
So
it's
still
useful
for
us
to
have
a
procedure
that
can
be
run
out
of
the
box.
B
A
Finally,
something
where
we
could
help
or
not,
but
that's
more
for
Kevin,
so
there's
been
a
walk
pushed
initially
by
Jean
Mark,
then
Brazil,
then
Kevin
I
contributed
a
bit
and
timel
as
well.
Right
now,
basil
made
a
good
point.
That
is
the
Jenkins.
Are
you
website?
Tutorials
should
always
show
the
content
of
what
the
archetypes
is
generating.
So
it's
always
synchronized,
so
an
improvement
to
avoid
the
multiple
pull
request.
A
Each
time
we
update
the
archetype,
we'll
be
finding
a
way
to
automate
when
jenkins.io
is
generated,
having
something
that
gets
the
template
and
put
it
in
the
documentation
instead
of
having
to
cherry
pick
manually.
That
way,
jenkins.io
will
always
be
in
line
with
the
archetype
and
eventually
put
a
date
or
a
link
to
the
original
file.
C
No
I,
like
I,
like
the
ideas,
certainly
we're.
We've
already
got
some
automation
that
feels
sort
of
like
that.
That
knows
how
to
automatically
update
the
recommended
Jenkins
version
based
on
the
current
LTS
and
the
the
preceding
major
LTS,
so
so
I
think
that
kind
of
automation
is
much
appreciated.
Great.
A
And
also,
we
should
update
the
date,
the
test
of
the
Python
Library
to
do
the
same
okay,
because
that's
another
location
where
the
method
build
plugin
is
documented.
So
we
should
ensure
at
least
that
the
readme
is
able
to
point
to
the
archetype.
So
that
will
be
the
source
of
truth,
because
the
archetype
is
an
automated
system
and
then
we
should
have
always
a
test
that
use
the
latest
archetype
and
try
that
method,
and
it
should
it
will
work
as
expected,
even
in
a
unit
test.
A
A
And
same
a
question
was
triggered
when
Stefan
pushed
to
the
gdka
19
about.
Oh,
the
infrastructure
team
is
planning
to
support
the
non-lts
TDK,
because
gdka
19
is
the
first
time
as
far
as
can
Daniel
Beck
remember,
which
means
a
good
indicator
that
we
are
able
to
provide
Edge
version
clearly
in
advance.
But
that
raised
the
question.
What
will
happen
when
jedica
19,
which
has
a
short
time,
leaving
it's
not
LTS
when
it
will
be
replaced
by
gdka
20
Etc
until
the
next
clinical
LTS?
A
So
the
proposal
here
we
have
an
issue,
help
desk
open
by
Stefan
to
work
on
proposing
enough
life
support
by
the
infrastructure
for
the
tools
we
provide
the
proposal
in
simple
because
same
same
issue:
do
we
make
chideka
19
explicits
and
we
have
to
ask
developer
to
change
it
over
time
and
they
have
to
change
your
phone?
Do
we
provide
Jenkins
chidika
age,
the
change
automatically
creating
surprise
breaking
no
consensus,
so
my
proposal
as
infrastructure
officer
there
after
discussing
with
Stefan,
that's
the
proposal
from
Stefan?
A
Is
we
write
down
that
we
stick
to
the
official
gdka
depreciation?
There
is
another
Life
program
and
we
stick
to
it,
and
then
we
say
when
ajitica
is
deprecated,
we
remove
it
like
two
or
three
weeks
after
the
end
of
life
time
for
us
to
move
it,
and
since
we
should
be
able
to
work
on
a
batch
of
pull
requests.
A
C
That
that
makes
sense-
and
that
aligns
perfectly
with
the
way
we
describe
our
support
of
Linux
platforms,
where
we
say
the
Jenkins
project
says
we
do
not
support
any
platform
that
the
Upstream
provider
does
not
support
yeah,
and
we
we
drop
support
immediately
so
the
day
that
they
stopped
supporting
Red
Hat
Linux
7.
As
an
example,
we
will
gratefully
stop
supporting
that.
A
Exactly
there
has
been
a
nice
this
nice
proposal
as
well
around
the
gedica
age.
That
would
be
always
the
latest
age,
so
we
only
maintain
one
at
a
time
which
is
not
LTS
that
if
it's
that
GDK
The
Proposal
will
come
from
initially
from
Alex
error
by
default.
Failure
with
that
GDK
does
not
fail.
The
world
build,
it's
just
an
indicator
and
developer
could
opt
in
on
failing
their
bills.
If
they
want,
they
say
no
I
really
want
to
fail.
If
it
fell
on
that
GDK.
A
However,
if
if
the
age
did,
they
can
name
19
discussion
is
a
topic.
We
could
still
keep
that
behavior
saying
we
have
a
list
of
identified
GDK
that
we
know
is
LTS
11,
17
and
21
in
the
future,
so
any
gdknot
on
the
LTS
list
could
benefit
from
that
optional,
behavior
on
the
build
plugin
function.
F
I
think
we
should
it's
an
optional
nice
to
have,
but
yeah.
A
I
think
it's
nice
to
have,
but
still
useful
and
cooler
developers
to
help
them,
because
the
GDK
is
going
to
change
more
and
more
often
and
Jenkins
is
just
starting
to
take
the
path
it's
brand
new
for
the
community.
We
are
late
on
the
GDK
ecosystem
on
that
and
it's
not
an
easy
Cliff
to
have.
So.
If
we
provide
that
kind
of
behavior
for
developer,
it's
really
a
service
we
can
provide
to
them.
A
Nothing
else
on
this
is
everything
clear:
okay,
just
award
the
Ubuntu
20.0
for
a
great
campaign,
so
thanks
everybody
for
taking
care
of
digging
everywhere.
On
that
part,
it
sounds
like
all
the
obstacle
to
start
are
removed,
as
you
provide
the
correct
free
version,
and
so
in
order
to
be
sure
that
everything
works,
I
always
started
to
work
with
the
new
VPN
for
the
new
private
network.
If
I'm
not
mistaken
or
awake,
and
you
confirm
you
are
using
Ubuntu
222.
A
If
it's
not
the
case
now,
that
will
be
soon.
Yes,
it's
okay
cool.
So
the
goal
is
to
validate
the
full
Pulpit
life
cycle
and
if
puppet
works,
then
we
could
store
the
campaign
for
upgrading
Ubuntu
22
for
all
of
our
machines,
so
we
will
have
for
Azure
that
will
be
easy
for
AWS.
That's
a
topic
to
wait
for
January.
A
There
should
be
the
last,
because
that
could
mean
and
I
think
we
should
remove
all
the
per
system
services
from
AWS
and
move
them
to
Azure,
which
involved
trusted
CI
finishing
the
migration
of
package
to
both
Oracle
and
Azure,
and
then
we
will
see,
but
not
right.
Now,
right
now
we
are
speaking
about
upgrading
the
existing
machines
on
Azure.
That
should
happen
in
January
and
we
could
also
start
if
everything
works
for
every
on
the
VPN.
We
could
start
the
Packer
base
image
for
the
virtual
machines
we
are
using
on
cig
and
Kim
SEIU.
A
January
Oracle
rest
to
be
checked
quickly,
walk
in
progress,
so
the
issue
we
weren't
able
to
finish
this
week,
some
Jenkins
mirrors-
are
using
the
wrong
media
tag
for
plug-in
downloads.
That's
the
reason
initially
why
we
contacted
those
three
USL,
it's
fixed
on
those
USL.
So
thanks
they
were
really
reactive.
There
is
one
last
mile
for
us
that
will
be
updating
the
same
on
archives
during
which
is
a
mirror
that
we
host.
So
we
should
update
the
Apache
configuration
so
HPI
plugin
will
use
the
correct
content
type
as
well.
A
The
user
confirm
its
fixed
for
them
and
they
will
open
a
new
issue
if
they
find
all
the
mirrors
with
that
problem.
So
thanks
a
lot
for
that
contributor.
So
we
keep
that
issue
on
the
next
Milestone.
That
should
be
quick.
It's
a
few
Apache
lights.
B
Right,
it's
brand
new
I
started
yesterday,
I
think
and
it's
a
work
in
progress,
not
much
to
say.
A
Java
dog
build
is
failing,
so
Z
devops
for
a
jar
file
downloaded
by
the
javadog
generator
seems
to
be
corrupted
or
invalid,
zip
file.
That's
the
message
on
the
log.
I
haven't
had
time
to
to
go
further,
but
yeah
that
is
breaking
the
Java
dog
generation,
so
I
might
need
some
help
on
that
topic.
I'm,
not
sure.
If
it's
because
the
Z
develops
new
plugin
is
not
flowing
some.
A
What
a
thing
is
it
because
their
Gradle
system
does
not
create
the
jar
documentation,
javadoc
correctly,
I'm,
not
really
sure,
so
that
thing
is
built
once
a
week,
so
it
fell
this
week.
So
we
have
a
few
days
to
fix
that
I'm,
not
sure
what
will
be
the
right
person
to
help
there,
but
at
least
I've
opened
an
issue.
So
it's
known.
C
A
A
C
Kevin
and
I
are
have
been
working
on
and
Kevin's
actually
deep
into
a
review
of
all
the
issue.
Reports
on
the
website
project
so
that
we
can
make
that
thing,
remove
it
from
the
list
of
possible
projects
to
which
you
can
submit
a
bug
report
and
make
it
so
that
effectively
the
the
issues
there
become
read.
Only
because
we
switched
a
year
or
two
ago
to
using
GitHub
to
track
the
issues
for
jenkins.io.
C
Yeah
and
I
don't
know
if
we
will
actually
migrate
any
it's
right
now,
the
the
the
quantity
of
things
in
that
site
that
look
useful,
those
bugs
yeah
we
may
not
migrate.
Any
of
them
may
just
choose
to
say:
oh
they're,
all
they're,
all
quiet,
and
it's
been
years
since
we
last
did
anything
on
those
those
issues
leave
them
alone.
C
Once
once,
Kevin's
and
Kevin's
the
one
doing
all
the
work
once
Kevin's
review
of
the
website
issues
and
my
my
follow-up,
then
we'll
probably
ask
info
to
remove
it
from
the
the
pick
list
on
the
Jenkins
jira
system.
C
D
C
Right
Gavin
Mogan
reported
he
has
completed
the
transformation,
the
the
extract
from
Google
doc
into
a
portable
format,
and
so
he's
ready
for
that.
We
just
have
to
get
agreement
where,
to
put
it
Etc
yep.
A
A
As
your
cleanup
of
Resource
Group,
prod
committee
function,
so
I
was
waiting
for
feedbacks
for
one
week
before
deleting
I
had
the
proof
one
from
kv9,
plus
one
from
Alex
ER.
So
I
will
consider
that
we
can
now
delete
these
resources
right
after
the
meeting
did
them
no
opposition.
F
Yeah
I
I
didn't
look
at
it.
No.
A
Realign
reprogenkins,
ci.org
Mission,
so
I've
prepared
a
few
repository
to
tests.
I
need
to
work
on
my
Maven
on
a
maven
plugin,
so
walk
in
progress,
good
news,
it's
it
sounds
like
that.
We
should
be
able
to
only
turn
on
authentication
on
the
mirrors,
and
that
should
be
okay,
but
we
will
need
help
from
the
documentation
team,
at
least
because
we
will
have
to
communicate
to
plug-in
developers
hello.
You
need
to
follow
carefully
that
procedure
to
generate
a
settings.
Xml
Maven
file
in
your
home
directory
with
an
encrypted
password.
A
A
So,
given
oh
quickly,
people
seems
to
react
to
a
missing
documentation
or
own
clear
topic.
It
means
that
before
acting,
we
absolutely
need
to
prioritize
updating
the
Jenkins
documentation.
We
can
start
now.
There
is
no
prerequisites,
because
anyone
who
authenticate
can
already
and
continue
walking
there
is
no
constraint.
It's
just
that
we
will
have
to
communicate
that
moment
in
time.
It
will
be
one
hour,
then
one
day
then
definitively
they
will
enables
authentication
to
be
mandatory,
so
that
might
fail.
A
A
Kevin
I
will
open
issues
on
Jenkins
IO
once
I
have
a
clearer
view,
because
I
need
to
validate
the
test.
I'm
doing
and
I
need
to
challenge
the
choices
that
Morgan
Hyde
did
with
Daniel
Beck
and
bezilla
test.
So
it's
just
I'm
mentioning
that,
so
you
won't
have
any
surprise.
That
would
happen
after
Christmas
I
think.
A
A
test
in
progress
will
need
help
from
Doc
team
I
think
it
will
be
worth
it
to
involve
John
Mark
Mission
as
well,
because
he's
working
closely
on
the
plugin
on
the
program
around
plug-in
developers
at
least
beginners.
So
that
would
be
interesting
as
well
to
understand
his
view
because
he's
sometimes
struggling
with
instruction.
So
that
could
be,
let's
say,
a
great
smoke
test
to
run
it
through
job
Mark.
A
Windows
agent
on
CI
disconnect
prematurely
so
I
took
the
issue
from
the
end
of
Stefan
because
he
was
having
issues
with
his
vagrant
environment.
So
it's
on
me.
The
goal
is
to
change
the
labels
and
merge
to
update
the
acceptance
tests.
A
If
you
don't
mind
mark,
because
your
ear,
The
Proposal
I,
did
on
the
pull
request
before
we
can
close
this
issue,
we
are
changing.
I
propose
that
we
absolutely
remove
the
sequential
stage
OS
and
Java,
because
no
one
is
consuming.
D
A
C
A
F
Treated
also
VPN
VMware,
virtual
machine
and
I'm,
currently
working
on
making
prepared
manager.
This
virtual
machine
I've
also
added
a
I've
modified
in
the
carbon
weapon
image
and
repository
I've
modified
the
gov
wrapper
to
deal
with
easy
rsr,
so
we
can
create
a
client
configuration
file
in
for
several
VPN,
not
only
depended
rankings.io,
but
also
the
new
one.
Private
that's
depended,
checking
status.
A
F
A
So,
but
that's
related
to
that
topic,
so
the
answer
is
yes,
because
the
current
VPN
machine
is
a
huge
machine
that
cost
a
lot
of
money
it
Crea.
We
could
have
four
virtual
Machines
of
the
size
of
the
new
one
for
the
same
Coast.
The
reason
why
the
machine
is
that
huge
is
because
the
requirements
to
have
free
network
interfaces.
You
need
a
big
size,
sized
virtual
machine.
We.
F
A
So
a
clean
state,
but
that's
a
nice
to
have
still
good
to
have
the
the
initial
reason
why
we
need
to
create
a
new
machine
is
because
we
have
ipv4
overlap
issues
on
the
current
networks.
So
as
soon
as
we
start
appearing
the
networks
between
the
new
networks
and
the
former
one,
the
overlap
issue
will
spawn
to
the
new
networks
and
we
won't
solve
the
core
issue.
A
I'm
not
mentioning
the
complexity
of
a
setup
on
a
single
machine
that
is
able
to
peer
to
at
least
six
different
Networks
and
I'm,
not
mentioning
IPv6
right
now.
So
that's
the
reason
better
to
have
a
clean
State
and
that's
a
good
opportunity
for
us
to
be
nice
to
have
but
opportunity
to
validate
Ubuntu
22.
A
So
thanks
everybody,
because
that's
a
lot
of
work
as
well,
so
between
Stefan
and
irvy
I.
You
deserve
a
lot
of
of
Kudos
because
yeah
you,
you
did
a
lot
of
work
here,
allowing
me
to
focus
on
repo
Jenkins
CI
and
providing
a
lot
of
value
for
end
users.
So
thanks
a
lot
Steve.