►
From YouTube: Platform SIG 2019 11 07
Description
Jenkins platform special interest group meeting. Topics include AdoptOpenJDK (hotspot), AdoptOpenJDK OpenJ9, Plugin installation manager, Windows installer, and alternatives to broaden hardware support from the Jenkins docker image
A
Okay,
welcome
everyone.
This
is
the
the
Jenkins
platform
special
interest
group
I'm,
going
to
start
sharing
my
screen
and
let's
look
at
our
agenda.
First,
we're
going
to
review
the
review
the
agenda.
The
topics
on
the
agenda
be
sure
that
we've
got
all
the
topics
and
then
we'll
work
through
the
topics.
A
Adding
adopt
open,
JDK
j9
as
a
new
image
for
Jenkins,
then
we'll
talk
status
on
the
windows
installer.
We
had
a
plan
to
talk
about
Octoberfest
results,
but
Oleg
is
out
today
on
vacation.
So
we'll
defer
this
in
two
weeks
and
then
Natasha
added
the
plugin
installation
manager
tool.
As
a
topic
for
this
agenda,
are
there
any
other
agenda
items
that
people
would
like
to
add
before
we
start
working
through
the
agenda.
A
Okay,
I'll
take
silence
to
mean
mean
that
we
can
proceed
then.
So,
let's
look
at
open
action.
Items
on
the
mark
is
embarrassed.
We've
got
I
still
have
to
open
the
James
Jenkins
enhancement
proposal
for
doctor
operating
system.
Support
and
platform
selection
rules.
The
issue
there
is.
We
really
need
as
a
project
a
set
of
well-defined
criteria.
A
B
The
ticket
from
the
CDF
is
moving
forward.
They
they
created
a
new
legal
entity
in
order
to
have
an
entity,
they
can
purchase
the
code
signing
certificates
under.
So
that's
where
we're
at
they
have
established
that
LLC
and
now
we're
just
waiting
to
see
what
the
process
will
be
for
getting
the
code
signing
done.
A
Great
yeah-
that's,
that
is,
that
is
wonderful
progress
there.
That
was
the
sticking
point
for
us
getting
that
code
signing
certificate
and,
as
noted
here,
we
also
need
that
for
the
Jenkins
release,
automation
project,
that
Olivier
is
leading.
Thank
you
alright.
So
in
turn
next
item
adopt
openjdk
as
the
base
jdk
for
jenkins
images.
So
the
the
thinking
here
was
that
adopt
has
better
platform.
Support,
has
has
active
platform
support
for
some
interesting
platforms
that
we
might
need,
and
the
question
was:
what
do
we
need
to
do
next?
So
we
need
an
integrate.
A
B
A
That's
it
that's
a
good
question,
so
it
would
need
pull
requests.
You
said
for
master
for
the
doctor
slave
an
LP
slave
and
isn't
there
an
image
that
is
the
basis
for
those
two.
That's
docker
slave,
oh,
okay!
So
then
it's
ss8.
What's
what's
the
third
dollar
ssh
slave?
Thank
you,
doctor,
ssh
slave,
all,
right!
So
there's
it's
not
singular,
pull
request!
It's
multiple,
we'll!
Even
several
pull
requests.
I.
C
Think
mark
for
right
now,
due
to
adopts
limited
support
of
like
base
images
right
now.
At
least
you
know
we
talked
about
in
the
last
call
that
I'm
working
with
the
adopt
team
to
update
their
testing,
so
they
can
do
a
PR
to
the
official
docker
library
to
add
support
for
a
lot
more.
You
know,
bases
like
Santa,
ass,
Debian
stretch,
foster
and
all
that
good
stuff
right
now,
I
think
they
only
have
Ubuntu
1804
and
I'm
blanking
on
the
other
one,
maybe
ubi
I
think
they
have
official
ones.
I.
C
A
And
so
my
thought
was
that
as
I've
looked
at
the
Jenkins
docker
image,
it
seems
to
have
a
base
operating
system.
Oh
no,
that's
right!
It
does
use
a
it
uses,
something
provided
by
open,
JDK,
good,
okay,
so
Jim.
Your
point
is
that
since
adopt
doesn't
have
some
of
those
other
platforms,
that
would
be
a
really
significant
change.
Thanks,
good
point:
okay,
yeah.
C
And
that's
that
so
that
was
my
like
first
kind
of
idea
was
just
target
one
of
the
bases
they
do
have
I
know
they
have
and
Jordan
I've
been
using
the
Ubuntu
1804
base
for
adopt
on
us
490
and
we
haven't
had
any
issues.
Is
they
had
been
actually
really
really
stable
and
wrecking
really
well
unplug
and
support,
surprisingly
hasn't
been
an
issue
either.
I
know
that's
something
we
talked
about
last
time
like
oh
well,
you
know.
C
C
You
know
showing
hey
here
would
be
the
here's,
how
we
would
do
the
switch
over
to
a
dock.
For
me,
a
good
idea,
then
I'm
gonna
continue
putting
a
little
more
pressure
on
adopt
team
to
support
and
get
that
PR
underway
to
get
the
needed
base
images
so
that
we
can,
you
know,
convert
all
our
images
over
to
adopt.
C
B
B
C
Didn't
know
about
that
I
can
reach
back
out
to
them.
I
was
on
a
talk,
I
think
the
other
week
with
them
and
I
know
they
just
got
more
Linux
server
capacity.
So
that's
why
they're
more
open
to
supporting
many
more
base
images,
but
I
didn't
hear
anything
about
Windows
I
know
they
do
windows
I,
think
core,
not
nano
so
would
be
interesting
to
see
they
would
be
able
to
support.
Now.
B
C
An
automated
version
would
be
better.
Okay,
it's
something
I
have
not
touched
in
my
experience
with
docker
working
with
Windows
images,
it's
always
been
Linux
I'd
love
to
pick
your
brain
a
little
bit
more
on
that,
because
whether
you
do
a
PR
or
I
kind
of
prod
and
internally
with
a
top
team,
we
should
be
able
to
get
that
through.
A
B
A
A
C
They
had
Alpine
supported
and
if
you
look
at
their
unofficial
images,
there's
a
lot
of
Alpine
images
out
there,
but
the
official
docker
library
staff
was
a
little
concerned
with
how
they
were
implementing
Alpine.
Since
Alpine
uses
muscle
versus
live
GC,
you
know
pretty
much.
Everyone
uses
lib
GC
on
you
know
their
base
images
except
Alpine,
and
the
problem
was
the
dive
team.
Paulie
did
was
disabled
muscle
and
then
pull
down
live
GC
and
put
it
on
top
at
Alpine,
and
then
just
you
know
make
adopt.
C
You
know
work
on
top
of
that,
so
they
were
a
little
concerned
about
having
that
happen
they
were.
They
were
looking
more
for
official
support
of
muscle
with
adopt
on
top
so
I,
don't
I
talked
to
the
devs
for
the
adopt
team
and
they
look
like
they're
gonna,
try
Alpine
again
in
the
official
PR
and
I'm
hoping
it
goes
through
because
they
I
think
they've
done
a
lot
more
testing
a
lot
more
vetting.
C
But
my
concern
is
that
the
official
docker
library
staff
are
still
no
say
no
on
that
which
would
be
a
big
loss,
at
least
for
I
like
out
pine.
At
least
I
know
some
of
the
community
lakes
at
mine
too,
so
they
adopt
team
definitely
wants
to
support
it,
but
I
don't
know
whether
it
would
be
blocked
by
the
official
docker
library
staff.
So,
okay.
A
Recollection
was
that
there
isn't
an
open,
JDK
image
for
for
an
alpine
openjdk
image
for
Java
8,
but
if
I
recall
correctly,
not
for
Java
11
and
that
the
open
JDK
project
bluntly
declared
that
they
would
not
support
muscle.
That
was
my
my
that's
the
poor.
So
much
for
recollection
I'll,
double-check
I
can
do
some
I
think
that
that
that
open
JDK
refused
to
support
al
fine
with
Java,
11
and
I.
A
C
Devlin
does
getting
to
Java
11
you'd,
be
really
nice
for
everything,
but
al
exactly
bring
up
a
good
point
if
adopt
got
alpine
through
to
the
official
image.
Maybe
they
did
it
in
some
way
that
please,
the
docker
staff
they'll
be
interesting.
The
kind
of
daibul
deeper
into
that
and
see
how
they
actually
got
is
supported,
at
least
from
my
understanding
was
that
the
docker
library
staff
didn't
want
to
do
it
because
they
thought
it
was
not
I.
Guess
100%.
A
C
Open
j9
is
a
kind
of
different
implementation
of
hotspot.
You
know
what
hotspot
being
more
of
oracles
implementation
j9
has
a
different
approach.
It
was
originally
I
think
made
by
IBM,
but
then
since
open
source
state.
So
the
advantages
at
least
from
what
I've
seen
is
a
huge,
huge
ramp
up
a
huge
speed
boost
and
ramp
up
so
open
j9
has
a
much
faster
time,
ramping
up
to
against
full
capacity
or
full
for
peak
performance.
C
If
you
want
to
say
that,
and
then
we
had
a
win
on
the
call
last
time
and
he's
talking
about
how
hot
spot
usually
edges
out,
I'm
sorry,
open,
xenon,
usually
edges
out
hot
spot
in
performance,
there's
just
a
couple
of
edge
cases
where
hot
spot
you
know
you
might
you
might
want
to
go
with
hot
spot.
For
you
know
certain
use
cases
I
figured
what
he
said:
I'm
blanking
here,
mark
I,
don't
know
if
you
know.
C
A
A
One
of
the
things
I
thought
of
is
I,
think
I'm
gonna
I'm
at
a
good
point
personally,
where
I
could
take
the
pull
request
and
apply
it
to
my
tooling
and
see
what
breaks
my
tooling
involves:
Windows
agents,
many
different
linux
agents
all
hosted
off
of
a
docker
image
on
on
linux,
and
so
with
that
tooling.
That
should
give
us
a
little
bit
more
evaluation:
hey.
What
are
there
any
surprises
and
running
open
j9.
B
My
PR
for
adopt
for
nano
server
images
I
did
find
that
the
open
j9
crashed
when
it
was
when
I
was
trying
to
run
a
simple
like
Java
exe,
be
her
version.
I
haven't
reported
it
to
anyone
because
I
just
have
time
yet,
but
that
shouldn't
impact
for
master,
because
we
don't
Windows
master
images,
but
just
an
FYI.
Okay.
A
So
and
I'm
expecting
I
was
expecting
all
sorts
of
problems
just
related
to
surprises
around
garbage
collection
or
around
the
startup
sequencing,
because
Jenkins
is
huge
right,
there's
an
awful
lot
of
Java
code
in
Jenkins.
So
so
for
me
that
I
assume
we're
going
to
see
some
interesting
failures
as
we
run
it
at
larger
scale.
C
Yeah
mark
I
would
love
to
hear
about
that.
It's
you
guys
do
run
into
issues
anxiety,
I
can
definitely
you
know
kind
of
axed.
You
know
ask
the
internal,
open,
j9
team
and
see
what
they're
doing
I
know
they
do
a
lot
of
stress
tests.
That's
actually
part
of
the
test,
we're
actually
pulling
in
for
the
adopt
images
we're
actually
running
through
our
the
open,
j9
test
suite,
because
you
know
we
can
use
it
for
non
open.
C
J9
things
to
just
bunch
of
Java
tests
so
be
interesting
to
see
the
results
over
there,
but
from
Jordans
AI
implementation
of
it.
It
was
I
mentioned
this
last
time
to
mark,
but
it
was
kind
of
funny
we
we
spent
up
hot
spot
and
that's
390,
and
it
took
like
a
good
amount
of
time
for
the
Jenkins
master
to
come
up
and
get
you
know
get
to
that
web.
The
web
UI,
but
when
I
did
with
open
j9,
it
was
instantaneous
which
was
really
nice
to
see
an
interesting
to
see.
C
A
C
I,
don't
think
I
am
well,
I
did
and
there's
probably
some
performance.
Tweaks
I
noticed
they
had
a
couple
Java
Flags.
What
Jordan
I
did
was
we
just
actually
pulled
down
the
the
master
image
for
Jenkins
and
then
just
swapped
out
the
from
up
top.
So
we
were
probably
running
open.
You
know
running
on
open
j9,
but
we're
probably
not
optimized
for
anything
like
that.
So,
oh.
A
C
A
Well,
yet
because
I
know
that
890
definitely
has
some.
What
looked
to
me
like
ahead
of
time,
compile
or
maybe
it's
not
ahead
of
time,
but
some
caching
operations
where
they
invoke
something
in
order
to
get
it
pre
cached
into
the
docker
image.
So
I
think
that
maybe
even
more
interested
in
great
thanks,
Jim
yeah.
C
Oh
ping,
that
thread
and
see
if
we
can
move
along
I'll
be
sure
to
see
on
the
PR.
A
C
B
A
B
A
The
next
topic
I
actually
want
to
talk
to
hacked
over
fresh
results.
Briefly,
just
to
let
everybody
know
we
had
an
amazing
hack,
Tober
fest.
The
month
of
October
is
a
sponsored
month
where
digital
ocean
and
github
create
this
promotional
event
called
Oktoberfest,
encouraging
people
to
contribute
to
open
source
projects
we
had
by
the
midpoint
of
the
month.
We
had
over
50
new
contributors
and
50
new
pull
requests
coming
in
really
really
great
results.
Oleg
will
schedule
a
retrospective
exercise
so
that
we
can
see
what
we
learned
from
it.
A
What
we
need
to
do
better
and
differently.
One
of
the
key
things
he
noted
was
the
amazing
power
of
having
newbie,
friendly
or
first-time
user
friendly
issues
and
in
particular
having
them
as
github
issues
more
than
having
them
as
issues
in
the
Jenkins
JIRA,
because
github
has
provided
some
easy
facilitation
to
find
friendly
issues.
A
It's
made
me
think
gee,
maybe
I
want
to
shift
some
of
the
plugins
that
I
maintain
to
be
tracked
there
to
track
their
issues
in
github
rather
than
in
in
the
Jenkins
JIRA.
So
there's
very
interesting
results.
I
suspect
he'll
be
with
us
in
two
weeks
and
we
can
talk
about
it
then
now
has
Natasha
joined
us
Natasha.
Are
you
with
us?
Oh
yes,
there
she
is
I,
see
her
so
Natasha
stopa
has
the
plug-in
installation
manager
tool.
Natasha.
You
want
to
give
us
a
status
report.
Yeah.
D
Sure
so,
after
our
conversation
two
weeks
ago,
I
tried
doing
like
the
first
official
release,
but
it
got
like
an
error
and
so
like
it
basically
I
couldn't
deploy
the
I
guess
like
the
artifact.
So
we
looked
at
some
of
like
the
permissions
like
the
permissions
files
and
I
think
there
were
some
like,
maybe
naming
discrepancies,
so
we
fix
those
and
then
I
tried
doing
it
again
yesterday
and
still
I'm
having
some
issues.
D
So
I
was
just
gonna
see
if
you
guys
had
any
ideas
and
actually
overnight,
like
Tim,
had
replied
back
to
me,
but
I
don't
know
I.
So
one
of
the
things
that
we
had
done
over
the
summer
was
like.
We
had
renamed
one
of
the
jar
files
after
I
guess
like
using
maven
and
I
I.
D
Think
I'm,
like
a
little
bit
confused
about
so
I,
think
that
had
to
do
with
like
the
order
in
which
things
got
sent
to
artifactory
or
or
something
I
can't
remember
exactly
why
we
did
the
renaming,
but
I
know
that
like
without
it
that
had
caused
problems,
but
yeah
I,
don't
know
so
I,
don't
know
if
you
guys
have
any
ideas
or
that
made
any
sense.
B
D
D
A
B
B
D
A
Yeah,
so
the
dev
mailing
list
feels
like
that
was
the
place
that
I
had
to
go
to
anyway,
when
I
had
really
had
problems
doing
release,
and
in
my
case
the
problems
were
related
to
to
getting
the
right
right
bits
and
pieces
into
the
file
system
locally
and
getting
the
right
bits
and
pieces
permission
granted
on
the
remote
side.
Okay,.
D
A
C
Mark
I
had
a
one
thing:
I
wanted
to
bring
up
that.
We
come
briefly
mentioned.
Last
talk
was
and
I
thought
I
was
interesting,
or
at
least
you
I
think
I
thought
you
thought
was
interesting
was
we
were
talking
about
reclaiming
the
official
docker
image
from
the
docker
library,
the
official
Jenkins
one
and
the
interesting
part
I
know
you
guys
had
some
trouble
in
the
past
for
them
in
terms
of
availability
and,
like
you
know,
quickly,
pushing
out
images
when
you
guys
need
it.
C
The
one
thing
I
think
you
found
interesting
was
their
access,
their
build
pipeline,
which
has
access
to
pretty
much
every
single
arch
they
support,
so
whether
it's
arm
power
as
390
x86,
which
could
be
helpful
for
us.
When
we
start
you
know,
say
we
do
do
the
switch
to
adopt
and
we
get
on
something
that
has
support
for
many
different
architectures.
C
Would
it
be
worthwhile
I'll
he's
trying
to
reclaim
that
and
utilizing
some
of
their
resources
and
then
one
of
the
things
we
also
talked
about
was
kind
of
modeling.
After
how
adopt
does
it
or
adopt
has
their
unofficial
repository,
which
they
put
out
nightly?
Builds
they
push
out.
You
know
pretty
much
anything
to
in
everything
to
their
night
unofficial,
docker
hub
repository,
but
then
they
push
out
long-term
support
major
releases
to
their
official
one.
So
we're
not
swapping
the
docker
library
staff,
but
we're
just
pushing
out
our
best
images
over
there.
I
just
thought.
A
C
B
C
Put
a
damper
on
some
of
the
stuff
we
do,
but
that's
interesting.
How
does
how
do
official
images
actually
go
out
then
for
Windows?
If
it's
not
automated
Jeansonne
main,
we
have
to
go.
Do
it
well.
B
C
B
C
The
other
suggestion
that
we
use
internally
and
then
a
lot
of
open
source
communities
I've
been
working
with,
has
been
Travis
for
builds,
at
least
where
they
support
our
I,
think
they
support
arm.
It
might
be
in
their
beta
same
thing
with
power
they
lease
for
in
beta
and
then
I
think
just
recently,
s/390
got
into
their
public
beta,
so
they'll
be
interesting
to
see
if
we
could
possibly
use
the
Travis
public
images
or
public
resources
to
build
some
of
our
images.
I
don't
know
if
they
windows
support
being
I,
think
they
do
that.
B
A
At
least
for
me,
I'm
very
interested
in
Windows
Server
2019
because
of
the
addition
of
Microsoft's
supported,
OpenSSH
server.
It
makes
managing
Windows
agents
much
much
simpler
for
me,
thanks
to
that,
OpenSSH
server,
I've,
they've
they've,
given
me
much
better
results
thanks
to
that
served
a
new
server,
that's
added
in
Windows
10,
1803
and
later
and
in
Windows,
Server
2019.
C
Alex
is
the
github
actions.
Is
that
the
new
like
to
get
ho
just
pushed
out
we're
like
they
have
that
the
new
tab
up
there
that
the
only
thing
I've
seen
is
like?
Let's,
you
like?
Okay,
if
I
do
a
PR,
it
can
automatically
build
something.
Is
that
what
you
talk
about
when
you're
talking
about
actions?
Yes,.
A
And,
and
for
me
the
banging
your
head
against
the
wall
makes
you
an
expert
by
virtue
of
the
banging,
so
I
think
I
put
it
on
next
next
agenda.
Alex
review.
If
you'd
have
actions
I
think
Oleg
has
also
done.
Some
things
would
be
a
good
good
topic
to
have
next
time
that
we
meet
with
you
presenting
and
you
and
Oleg
together,
reviewing
and
discussing
sure
sounds
good.
Okay,
any
other
topics
we
need
to
cover
today.
C
Also
I
think
we
talked
about
this
briefly
last
time
is
the
Oregon
State.
Has
a
power
in
s/390
Jenkins
build
server,
you
can
do,
but
we
also
can
get
at
least
I
can
get
you
access
to
just
a
raw
server
for
at
least
s/390.
You
would
have
to
go
trace
down
some
power
people,
but
I've
done
in
the
past
to
get
power
access
that'd
be
helpful
for
you
guys,
as
we
gonna
venture
off
into
the
adopt,
and
you
being
able
to
run
your
test
cases
and
stuff
like
that.
It.
A
May
I
would
hold
that
at
least
for
two
weeks,
because
I
think
there
enough
I
think
we've
got
enough
action
items
that
will
keep
many
of
us
occupied
the
amount
that
we
can
for
at
least
two
weeks
keep
that
to
keep
bringing
it
to
us,
because
it's
a
good
reminder
that
hey
there
are
compute
resources
available
that
we
may
need
to
negotiate
with
the
for
me
until
we've
been
through
some
of
these
earlier
action
items.
Yes,
ok,
s/390!
A
Isn't
human
isn't
as
interesting
to
me
yet
because
I
haven't
even
done
the
basics
on
open,
j9
I
have
you
know,
I
things
that
I
think
I
need
to
do
with
with
equipment
that
I
already
have
available
that
I'm
conveniently
using
and
then
I'm
quite
experienced
with
so
when
problems
occur,
I
recognize
them
quickly
as
problems.
The
s/390
stuff
I
would
see
problems
and
they
would
be
complete,
surprise,
I'm,
sure,
yeah.
A
A
All
right:
well,
thanks
everybody.
Thank
you
very,
very
much
for
the
session
today.
I
propose
that
we
go
rats.
I
may
have
forgotten
to
turn
on
the
recording.
Well,
we'll
hope
that
I
have
the
recording
on
thanks.
Everybody
thanks
very
much
for
your
time.
Today.
Let's
go
ahead
and
end
our
session.
Now
I've
got
to
stop.
Sharing,
hey
I
did
record
it
thanks.
Everybody.