►
From YouTube: Platform SIG 2020 01 02
Description
Jenkins Platform Special Interest Group meeting January 2, 2020. The "New Years" edition. Topics include AdoptOpenJDK hotspot, AdoptOpenJDK OpenJ9, Docker agent image renaming, Windows installer, docker image platform support adding CentOS 8 and Ubuntu 18, and Google Summer of Code 2020 project idea gathering and refinement.
A
Right
there
are
many
of
us:
that's
that's,
okay,
it's
it's
the
day
after
the
New
Year's
holiday.
So
we'll
talk
about
open
action
items,
give
a
report
on
the
adopt
open,
JDK
proposed
transition
and
that
project
the
adopt
open,
JDK,
open,
j9
image
progress.
If
Alex
Earle
joins
us,
we
may
talk
about
Windows
installer.
We
may
need
to
skip
it.
Then
we've
got
a
general
topic
on
broadening
platform
support
and
google
Summer
of
Code
2020
project
ideas,
discussion
that
Oleg
has
agreed
to
lead
any
other
topics
we
need
to
add
or
like
and.
B
A
And
I
I'm
reminded-
let
me
put
an
action
item
here-
mark
create
an
epic
because
really
we've
I
like
that,
we're
using
JIRA
as
a
way
to
track
those
things
and
they
they
justify
an
epic,
because
there
are
multiple
tasks
fighting
and
especially
this
hot
spot
transition
or
open,
adopt
open,
JDK
transitional
in
progress.
So.
B
A
Don't
know
so,
okay,
all
right
so
on
open
action
items,
I
apologize
I
still
have
the
open
item
to
create
a
jet
for
docker
operating
system,
support
and
platform
selection
rules,
two
weeks
and
two
weeks
and
I'll
report
on
it
again.
Oh,
like
you,
still
got
the
item
for
a
jet
for
Windows
support
policy.
Now
maybe
I
like
there,
the
the
governance,
the
next
governance
meeting.
Is
it
one
week
from
now
two
weeks
from
now.
A
B
We
have
pocket
edge
on
the
older
game,
but
yeah
okay,
at
least
having
these
topics
would
be
nice,
though
yeah
one
of
the
things
is
the
job
process,
so
that
governance
meeting,
which
it
doesn't
have
say,
budget,
protest
right
right
now.
The
job
process
is
based
on
media
file,
not
on
the
governance
above
okay,
so
for
discussion.
I
would
rather
to
just
using
comedian
kissed,
and
if
you
need
to
sign
off
then
yes,
Dominus
meeting
like
we
did,
for
example,
for
web
browsers
last
week
last
month,.
A
A
B
A
B
Right
so
what
we
get
a
couple
of
weeks
ago,
we
created
a
new
hip,
hop
team
which
basically
streamlined
support
for
all
filtered
images.
So
all
the
kit
images
are
currently
managed
by
a
single
team,
including
Alex,
Oh,
Marc
Nico,
what
the
law
geeky
and
maybe,
if
you
are
the
contributors,
so
basically
usual
suspects
from
who
used
to
make
images
before
and
it
is
regarding
look
at
hard
permissions.
Basically,
maintenance
do
not
need
them,
but
it
so.
The
syncing.
B
A
B
The
same
problem
applies
to
agents.
Why
you
know
get
into
a
move
for
agent
builds
to
trust.
The
CIA
is
mostly
because
of
the
access,
because
nobody
from
pod
from
seek
and
from
doctor
containers
had
access
to
trusted.
Ci
our
big
situation
changed
any
recruit,
reconsider
it,
but
we
it
requires
a
my
fault.
Okay,
yeah.
You
generally
need
to
build
the
entire
pipeline.
A
B
B
B
We
have
Jenkins
file
which
basically
publishes
later
on
jank
is
for
well,
it's
really
a
Chanel
instance
for
doctor
images.
But
if
you
want
to
ship
official
images,
then
we
trust
this
guy,
because
in
the
current
state
of
vodka,
drink
I
wouldn't
have
to
look
at
how
to
load
images.
I'm
windows
images,
okay,
so
so
I
was
issued
so
so.
A
Alright
and
the
thing
that
is
needed,
there
is
trusted
CI
work,
not
work
on
docker
hub
right.
So
look
at
how
justice
and
support
in
between
those
images-
and
that
part
surprises
me,
because
the
adopt
open,
JDK,
open,
j9
folks
noted
that
docker
hub
now
supports
series
390
and
Oh
Power
PC
64
le.
So
the.
A
Okay
and
and
that
I
don't
know
the
distinction
of
that,
alright.
So,
but
nonetheless,
in
any
case,
we
would
we
we
need
the
control
that
trusted.
Ci
gives
us
of
publishing
our
own.
Our
own
images
right.
B
Actually,
we
also
need
to
stop
sending
images
at
some
point,
because
right
now,
Allegiant
beam
images
are
not
signed
and
there
is
additional
metadata,
which
is
added
to
images
and
right
now,
I
will
try
to
consider
our
images
as
untrusted
and
official
guide
and
by
dr.
that
you
shouldn't
build
building
trust
in
which
a
Samba
could
help
anyway,.
A
A
B
Are
not
trusted
sale
likely,
it
will
be
another
reduce
environment,
so
use
a
work
environment
for
jinkies
images,
I'm,
sorry
for
Jenkins
code
and
once
it's
ready
almost
like
you
have
to
deliver
the
peptide
to
that
instance.
Okay,
so
my
understanding
that
it
won't
be
a
trusted
CI
anymore,
once
the
project
is
completed.
A
B
A
A
B
Definitely
bigger,
firstly,
because
it
involves
mountain
of
inkmaster.
It
also
involves
agents
if
you
want
to
complete
the
transition,
so
it's
at
least
five
to
six
selfies.
It
all
is
involved.
Secondly,
all
kinds
of
various
pipeline
and
testing
questions
in
the
equation
and
also
the
transition
approach,
because
you
can
just
add
more
configurations.
In
such
case
it
can
be
a
bit
relaxed,
but
if
you
want
to
change
the
default
configuration,
then
it
becomes
quite
complicated
and
then
I'll
show
what
they
are
all
in
tension.
Do
we
want
to
change
in
the
default,
but.
A
My
initial
thought
was
that
we
should
change
the
default
to
insulate
ourselves
more
effectively
from
operating
system
vendors
breaking
their
jdk.
However,
that's
there
that's
trading
one
form
of
breakage
for
another
right.
If
we
get
an
imperfect
set
of
packages
inside
the
Debian
image,
for
instance-
and
it's
not
the
same
as
the
old
packages
and
some
user
depends
on
it-
they'll
be
broken,
so
I'm
open
to
open
to
either
it's
just.
It
felt
like
if
we
just
add
a
new
one.
A
B
A
Right
and
I
think
that,
given
the
amount
of
work
involved,
there
is
no
way
it
could
be
done
before
core
release.
Automation
is
done,
there's
just
there's
too
much
to
do
in
terms
of
new
testing
worrying
about
have
we
have
we
determined
the
correct
set
of
things
that
we
need
to
include
and
does
adopt
open
JDK
have
the
correct
operating
system
definition
for
what
we
need
right,
yeah.
B
You
can
still
introduce
the
image
itself
at
any
moment,
so
we
can
change
the
default,
maybe
say
in
several
months,
but
right
now
become
a
token
creations.
Okay.
So
if
you
want
to
start
affiliation,
it
would
be
a
good
step.
I,
don't
promise
that
you
will
get
a
lot
of
adoption,
but
yeah
we
invested
some
time
in
order
to
make
changes
more
visible.
For
example,
we
have
change
logs,
follow
images.
Now
you
can
also
go
announcement
on
social
media.
We
can
post
a
blog
so
that
we
start
the
revelation.
B
A
B
A
A
A
A
B
A
B
Kado
stories,
so
we
have
absolutely
for
a
terminology,
and
this
terminology
still
exists.
You
know
official
document
images
fishy,
so
we
have
Ford
okay,
Jenkins
fresh
slate,
which
in
case
Russia
s
SH
they
find
janky
/g
no
piss
wave.
So
the
suggestion
on
the
table
is
to
finally
get
rid
of
all
of
them.
A
Okay,
so,
and
so,
but
if
we
is
the
idea
that
we
would
actually
abandon
the
main
maintenance
of
Jenkins
out,
can
/
slave
or
is
it
rather
that
it
would?
There
would
just
be
a
new
image
called
agent
and
it
would
be
maintained
in
parallel
with,
with
the
old
name,
a
new
name,
both
being
published
as
releases.
B
Yeah
I
think
it
will
be
two
images
at
least
for
a
while,
so
we
did
a
mutation
as
a
part
of
Jenkins
to
do
zero.
We
introduced
in
Jenkins
organization
before
that
we
had
a
junkie
CI
and
at
that
point
we
just
recreated
that
there
be
images.
So
why
didn't
the
renaming
before
is
because
in
docker
hub
basically
auto
built
was
all
in
feature
and
if
you
wanted
to
disable
the
auto
Beals,
you
had
to
recreate
a
better
physiologist.
B
That's
why
we
didn't
rename
these
images
at
that
point,
but
right
now
we
can
do
that
and
even
into
the
plant,
not
to
trust
the
CIO
to
release
the
environment
later.
But
if
we
can
just
disable
auto
builds.
So
it's
a
lesser
of
concern
at
the
moment
and
they
were
intended
to
practically
it's
a
bit
changed
even
before
they
have
a
pipeline
change
changes.
B
B
B
A
B
Well,
we
don't
even
have
to
run
our
process.
You
can
duplicate
the
pipeline's
on
docker
hub.
It's
just
doubled
some
on
top
four
bills,
I
see
well.
Technically,
we
can
just
update
a
bit
repository.
We
create
concreting
you
repository,
for
example,
for
slave
images.
We
just
extend
additional
base
images
mark
everything
is
duplicated
put
documentation,
but
it
implies
a
lot
of
legwork
so
yeah.
If
there
is
a
consensus
that
we
want
to
do
that,
yeah
I
can
do
that.
Okay,
not
this
month,
but
yeah.
We.
A
Can
start
client
it
right
right
this?
This
is
another
one
of
those
that
that
I
assume
needs.
We
need
discussion
and,
like
you
said,
we
need
a
promotion
actively
notifying
people,
blog
posts,
etc
that
hey
here's.
This
change
coming
we're
really
getting
rid
of
this
we're
doing
more
work
to
get
rid
of
this
obsolete
terminology.
Yep.
B
A
A
Then
we've
got
broadening
platform
support,
just
to
note
that,
yes,
we
have
PRS
proposing
CentOS,
eight
and
I
think
this
was
actually
proposing.
Centos
eight
replacing
CentOS
7
I've
got
to
double
check
that
ought
to
look
at
the
PR
mm-hm.
We
have
a
proposal
to
add
an
Ubuntu
image
and
then
notes
from
previous
meetings
on
the
capabilities
that
are
available
to
do.
Platform
builds
in
other
projects
in
case
we
need
them.
B
So
I'm
not
sure
whether
we
have
enough
people
to
discuss
this
topic
here,
but
they
that
you're
looking
for
men,
d'oeuvres
we're
looking
for
project
ideas.
Last
year
we
did
several
projects
which
were
related
to
platform
seek,
for
example,
plug-in
installation
manager,
and
so
hopefully,
next
year
you
also
have
some
projects
and
doing
like
all
contributors
to
participate
and
at
the
proposed
by
ideas.
So
Marc
resolutely
proposed
here
idea
is
really
to
give
plugin.
A
A
so
I
saw
that
you
had
noted
the
concern
or
your
noted
in
the
mailing
list
about
the
proposal
startup
process
I
would
have
assumed
that
I
was
supposed
to
start
them
by
opening
conversations
in
the
mailing
list,
but
I
think
you
write
a
correct
observation
that
the
platforms
there,
that
the
g-shot
mailing
list
is
a
pretty
narrow
group.
Can
you
give
some
more
insights
on,
should
I
be
hoisting?
These
conversations
into
the
Jenkins
developers
group
for
technical.
B
The
excuse,
so
one
of
the
reasons
is
because
Jae
Seok
is
my
name
pleased
for
Jaso
coordination.
What
for
technical
discussions?
Another
reason
that
google
Summer
of
Code
is
just
one
of
the
outreach
programs
we
have.
We
also
have
community
bridge.
We
have
outreach,
we
may
have
expect
in
our
programs,
like
Alibaba
Summer
of
Code
early
summer,
who
knows
so
by
keeping
discussions
in
the
developer.
My
name
is
Christina.
Keep
your
chance
open.
B
A
B
A
And
I
like
that,
actually
I
think
that's
that's
a
good
insight.
I
would
I
would
love
to
have
more
feedback
and
you're,
certainly
right
that
there
are
many,
many
more
readers
of
the
Jenkins
developers
mailing
list
than
the
Jenkins
g-shock
project
mailing
with
us,
so
yeah.
That
makes
very
good
sense.
Yeah.
A
A
Right
right
for
yeah
safety
for
an
eventual,
because
we
can
predict
that
there
is
an
LDS
coming
right.
Whatever
version
they
choose,
there
will
be
one
and
it
will
have
well
as
an
example.
They
they.
They
warned
us
at
Java.
Eleven,
hey
we're
going
to
turn
off
certain
things.
They
then
had
to
back
off,
but
I
would
guess
the
next
LTS
they're
not
going
to
back
off
and
those
what
were
they
there's
still
a
number
of
messages
we
get
about.
Al
I'm,
embarrassed
to
admit
it:
I,
don't
in
reflective
Fluxus.
A
Yes,
yes,
illegal,
reflective
access
messages
that
that
those-
maybe
they
had
warned
in
eleven
hey
we're
gonna
make
these
hard
stop
and
they
backed
off
from
that.
But
now
in
the
next
LTS,
whatever
it
is,
they
may
say
no,
those
are
hard
stop
and
we
need
to
get
those
fixed
well
before
that
thing
releases.
Well,
it's
yet
to
be
seen.
Oh.
B
B
Single
discussion
is
about
a
girl,
vm
and
other
native
prints
tonight
images,
because
if
we
had
a
native
image
for
Jenkins,
it
would
be
so
I
need
a
prototype
watching
this
file
run
it
at
some
point,
but
the
agendas
for
low
tunnel
is
quite
specific,
but
if
we
put
find
their
ways
to
actually
visit,
for
example,
for
changes
agents
to
speed
them
up,
if
you
could
improve
classification
docker
images,
then
it
would
be
really
feasible.
Project
helpful.
A
A
B
Something
like
that,
okay,
so
basically
it's
one
of
the
stories
which
we
need
to
consider.
We
want
to
make
Jenkins
cloud
native
at
some
point,
because
Java
is
not
efficient
in
called
native
application
and
so
on
and
so
on.
It's
improved
its
improving
Coco's,
but
if
we
take
out
projects
like
travel
like
Quercus,
they
provide
a
lot
of
additional
features
which
help
use
Java
in
contingent
environments
right.
Okay,
so
it
worthless
in
this
case
I'm.
Sorry.
What
together.
A
B
A
B
A
Is
really
to
me
quite
surprising,
because,
with
all
of
the
all
of
the
things
that
all
of
the
things
that
were
such
a
challenge
in
Java
11
in
the
Java
11
transition,
I
would
have
assumed
those
plus
many
many
more
would
be
a
challenge
in
something
trying
to
run
a
native
image.
That's
that's
really
encouraging.
Well
jinx.
B
Has
it
so
not
one?
Yes,
because
you
know
what
you
are
going
to
run
there.
The
plug-in
ecosystem
is
pretty
used
there.
Well,
you
can
run
plugins
in
classic
way,
but
just
doesn't
make
any
sense.
So
in
my
case,
with
unhooked
everything
to
clean
dependencies
and
then
compile
to
this-
and
that's
made
him
for
him.
B
A
A
B
B
So
yeah,
if
somebody
has
any
ideas
in
mind,
please
submit
these
ideas
and
the
projects
could
be
quite
complex.
So
it's
not
that
we
are
looking
for
new
turf
and
the
issues
top
builders
are
this
year.
For
example,
we
delivered
features
like
like
an
installation
manager.
We
deliver
ticket
LaBranche
source,
which
are
major
features.
Important
packaging
is
community
and
let's
do
all
the
same
movies
here.
I.