►
From YouTube: 2020 08 27 Platform SIG
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
Welcome
everyone:
this
is
the
platform
special
interest
group.
It's
the
27th
of
august
2020.,
we're
recording
this
session.
It
will
be
available
on
the
platform
playlist
agenda
review.
Adopt
open
jdk
for
docker
on
alpine
is
a
topic
wanted
to
give
a
final
status
report
on
that
then
adopt
open,
jdk
8
for
docker
on
deviant
centos.
A
A
Agenda
then,
let's
go
ahead
and
go
so
adopt
open
jdk8
for
docker
on
alpine
is
done,
delivered
in
jenkins,
2.2
35.5
in
jenkins
2.200.
I
believe
53.
A
A
B
A
C
D
A
Okay,
well,
that's
that's,
okay,
good
to
hear
that
somebody
was
using
it.
That's
that's
a
win.
There
was
a
period
where
it
was
being
shipped
or
something
derived
from
alpine
was
being
shipped
by
cloudbees,
but
I
think
they
found
that
to
be
critically
painful
and
shifted
away.
A
B
We
have
a
pr
for
the
debian
portion,
but
for
centos
we're
using
we're
still
just
installing
from
yum
okay.
B
So
I
guess
what
we
should
determine
is
whether
we
want
to
install
a
specific
version
of
java
or
if
we
just
want
to
continue
to
rely
on
the
package.
A
B
A
A
A
A
B
There,
I
don't
know
if
it's,
but
it's
not
specific
to
this,
but
I
know
daniel
has
voiced
his
concern
about
the
number
of
images
we
publish
and
having
to.
B
All
of
those
images
for
security
releases,
so
I'm
wondering
if
we
want
to
do
something
where
we
have
an
official
set
of
images
that
are
the
like
main
image
of
jenkins
and
we
publish
and
then
ancillary
ones
that
we
do
publish
but
are
not
like
the
main
support
ones.
I
don't
know
if
that.
A
Makes
sense
yeah
so
still
leave
them
in
the
in
the
jenkins
ci,
but
but
acknowledge
we
are
not
going
to
claim
official
support
for
these
yeah
more.
Like
would
you
envision,
I
mean
it
seems,
though,
that
that
would
that
may
still
cause
daniel
heartache,
because
he'll
get
people
who
are
badgering
him
saying
I
want
this
security
fix
on
this
thing.
That
is
not
officially
supported,
yeah
yeah,
but
this
I
think
it's
one
thing
to
consider
adopt
open
jdk
does
something
like
that
right.
Where.
D
B
Trump's
sbi,
yes
for
the
for
the
official
repo,
it's
untrusted.
For
that
we
do.
I
couldn't
find
the
last
time
I
was
working
yeah.
B
A
D
That's
fine
yep,
so
it's
in
the
latest
weekly
replaces
the
install
plug
and
study
sage
script
with
the
plugin
installation
manager,
cli,
which
was
a
gstop
2019
project,
and
it's
had
a
number
of
improvements
over
the
last
few
months.
D
The
biggest
new
feature
is
probably
being
able
to
automatically
update
your
plugin
file
with
the
cli,
which
saves
20
to
30
minutes
of
tedious,
reviewing
and
finding
new
versions
to
just
a
like
a
script
that
takes
one
to
two
seconds
to
run.
D
Yeah,
nice
yep,
and
also
it
also
works
in
the
yaml
file
as
well,
and
it
can
output
it
to
your
console
as
well
as
just
like
a
human
readable.
If
you
want
that,
if
you
just
want
to
see
what
the
new
versions
are,
it's
in
the
latest
weekly
version
only
so
2.254
and
it'll
be
in
the
next
lts
in
a
couple
of
weeks.
I
guess.
A
D
One
thing
said
daniel
beck
wanted,
I
think,
there's
a
pull
request
open,
which
makes
the
install
plugins,
perhaps
more
compliant
with
the
update
center.
It
uses
less.
You
use
the
directory
structure
less
than
guessing
versions.
D
D
I
think
it's
yeah,
so
I
think
there's
a
poor
request
that
daniel
just
wanted
merged.
It's
open
against
the
install
plugins
script.
B
A
A
D
Can
have
a
dedication
warning
or,
or
even
just
say,
hey
try
just
hey.
Do
you
want
to
try
the
new
the
new
plugin
manager
cli?
It
has
automated
update,
support
and
and
is
better
tested,
yeah
next
generation
cli.
D
A
A
A
A
A
Great,
so
let
me
let
me
put
that
on
put
that
on
on
there
and
I'll
review
I'll
rely
on
reviewers
to
correct
me.
If
I
say
something
too
bold
or
not
bold
enough
about
eventual
obsolescence,
it
certainly
won't
have
any
timeline
timeline
on
it,
but
rather
stating
that
we
intend.
Actually
maybe
this
is
the
place
to
highlight
the
update
center,
has,
is
using
https
and
should
also
highlight
an
invitation
to
add
more
mirrors.
Are
we
at
the
point
where
we're
ready
to
recruit
more
mirrors.
A
E
No,
definitely
it's
definitely
good
to
promote
it.
More
is
the
better
I'd
say.
A
Okay,
so
I
may
I'm
a
ping
I
may
ping
daniel
back
to
see
if
you'd
like
to
be
involved
in
in
contributing
to
that
blog
post,
because
it's,
I
think
the
http
to
https
transition
is
an
important
thing
to
highlight
for
people,
and
this
is
a
good
excuse
to
say,
hey,
look
it's!
This
is
we've
gotten
smarter
about
what
we're
doing
with
the
update
center.
A
D
D
But
now
update
center
is
always
serving
https
links,
although
you
can
still
access
it
initially
on
http,
which
will
hopefully
remove
at
some
point
and
that's
due
to
java
issues
with
cross
protocol
and
your
browser
will
upgrade
seamlessly
http
https,
but
java
won't
do
it
without
a
lot
of
extra
code
that
isn't
in
there
currently
so
yeah,
that's
one.
So
end-to-end
is
the
style
which
was
gained
from
switching
from
mirror
brain
to
mirror
bits
all
of
our
mirrors
support,
https
and
so
any
new
mirrors.
D
The
other
bit
was,
I
think,
was
about
plugins
being
available
immediately
after
release
previously
was
about
an
hour
to
two
hours
after
release,
you
would
quite
likely
get
404s
and
it'll
be
impossible
to
install
a
plugin,
so
you
installed
the
get
client
plugin
you've
got
300
000
instances
running
it,
but
for
the
next
two
hours
it's
impossible
to
install
get
so
basically
it's
impossible.
It's
still
possible
to
start
a
new
jenkins
because
it's
depended
on
by
so
many
things,
but
so
now
it's
available
immediately.
D
D
To
just
add
a
new
file
which
includes
all
of
the
recent
releases
for
the
last
three
hours,
and
we
only
sync
those
on
every
push
we
have.
One
complication
that
we
need
to
keep
an
eye
on
is
that
originally
our
fullback
was
something
called
archives.jstr.org,
and
so
that's
so
we're
currently
only
mirror
jenkins
wars
and
not
sure
about
plugins,
but
definitely
just
because
that
have
been
released
in
the
last
year
and
we
include
everything
on
archives
against
all.
D
But
the
machine
is
incredibly
slow
and
it
was
okay
for
war
files
for
people
that
weren't
updating,
but
there's
an
issue
with
mirabets,
where
it
doesn't
seem
to
pick
up
plug-in
releases
or
just
doesn't
notice
something's
in
the
mirror.
For
an
hour
and
a
half,
it's
got
two
stages
where
it
does
a
local
refreshing
sync,
where
it
seems
to
take
about
15
minutes
to
notice
that
the
plug-in's
on
mirror
bits
and
then
it
will
hash
it,
and
it
will
look
to
see
if
it's
available
anywhere
and
then
it
does.
D
D
Whether
it's
upgrading
archives,
whether
it's
texas,
mirror
while
improving
mirror
bits
to
allow
us
to
tell
it
that
a
specific
thing
has
just
been
updated,
so
with
mirror
brain
that
did
have
that
capability.
So
there
was
a
specific
mv
scan
and
you
could
pass
the
file
path
and
sort
of
amerigrain
you
could
so
that
was
what
was
done
during
security
releases.
D
So
security
releases
didn't
have
that
issue,
and
so
it
allows
an
immediate
sync,
but
yeah
mirrorbox
is
missing
that
feature.
So
possibly
we
could
contribute
it.
I
I
asked
no,
I
see
if
I
didn't
get
a
response
and
I
haven't
had
time
to
raise
an
issue.
A
D
Yeah
yeah
probably
cost
management's
the
best
place.
I
mean
I'm
looking
at
directly
at
the
storage
account,
which
shows
the
amount
of
bandwidth,
and
I
was
calculating
that
based
off
the
pricing.
We
just
got
a
quick
look
and
cost
analysis
for
the
last.
A
D
Yeah,
that's
so
that's
been
applied.
I
raised
this
issue
on
olivia,
so
it's
it's
in
olivia's
github
account.
There's
the
murabits
doctor
image
we
used.
I
raised
an
issue
there
that
we
never
updated.
It
and
olivia
decides
to
reply.
Oh.
D
And
he
told
me
that
we
should
just
run
it
regularly
from
infra
jenkins
and
update
the
image,
but
I
think
I
found
a
better
way.
I
didn't
really
want
to
have
to
meant
to
manually,
approve
and
merge
the
answer
all
the
time.
D
It
was
a
waste
of
our
time
and
I
found
a
jio
ip
update,
docker
image,
which
is
an
official
one
which
they
published,
which
will
just
and
you
can
pass
it
an
argument
which
is
how
often
you
want
to
refresh,
and
it
will
just
it
just
updates
it
for
you.
D
I
added
it
to
another
container
and
announced
the
grp
data
in
both
containers,
and
so
it
runs
every
24
hours
now
and
at
least
it's
it's
updated
at
least
once
let's
say
that,
so
previously,
it
was
january
was
when
it
was
last
built
and
the
last
modified
date
is
now
august.
D
Great
excellent,
thank
you,
and
that
was
so
someone
someone
raised
an
issue
with
an
irc
saying
that
the
data
well
they're
us.
They
said
they
were
going
to
mirror
they
shouldn't
be
and
that
their
grp
data
used
to
be
wrong
and
it
was
fixed
at
some
point
so
that
led
us
to
oh
yeah.
That
hasn't
actually
been
updated
in
a
while.
I
assume
that
it
was
being
outdated
by
cron,
but
it
wasn't.
A
I
was,
I
was
delighted
to
have
pushed
a
new
version
of
the
get
get
plug-in
and
had
no
complaints
about
being
unavailable
and
delighted
when
I
updated
a
plug-in
yesterday
morning-
and
it
only
released
51
minutes
earlier,
and
I
saw
no
no
problem
there
either.
So
very
nice
thanks
any
other
topics
we
need
to
discuss
today.
A
All
right
that
covers
it,
then
recording
will
be
posted
I'll
update
the
action
item
list
after
the
meeting
to
be
sure
that
it
records
action
items
we
added
to
the
session
thanks
very
much
vivek
was
there
anything
that
you
had
topic
that
you
needed
to
add.
While
you
were
here.