►
From YouTube: Platform SIG 2019 11 21
Description
Jenkins platform special interest group meeting from Nov 21, 2019. Topics include Hacktoberfest, AdoptOpenJDK, Windows, macOS and more
A
Welcome
everyone:
this
is
the
Jenkins
platform
special
interest
group
great
to
have
everyone
here.
Let's
take
a
look
at
our
agenda
first
and
we're
going
to
talk
through
the
agenda
after
we've.
Looked
at
the
agenda
will
then
work
work
on
the
items
on
the
agenda
so
we'll
talk
through
open
action
items
as
one
then
adopt
OpenJDK
as
a
potential
replacement,
image-based
jdk
for
jenkins
images.
Talk
about
the
current
status
of
that
then
the
evaluation
of
adopt
open,
JDK,
open
j9
as
an
additional
image.
A
Then
hacked
best
results
plug-in
installation
managers
on
our
agenda.
If
Natasha
arrives
we
made
will
and
they
have
a
deeper
discussion.
Otherwise
it'll
just
be
brief.
Mac
o
as
a
native
installer
deprecation
topic
with
Oleg
potential
topic
on
broadening
platform,
support
for
docker
images,
then
Mac,
OS
native
installer
updates
nothing.
A
B
A
That
that's
good,
let's
lead
with
Oktoberfest
that
way.
Yeah!
It's
also
it's
a
great
story,
I
think.
So,
let's
do
that
all
right!
Excellent!
Thank
you.
Okay,
so
open
action
items,
I'm
sincerely.
Sorry
I
still
have
the
open
action
on
it
will
probably
remote
remain
open
for
another
month
to
open
a
jet
for
a
process
to
choose
how
we
do
docker
operating
system
supporting
platform
selection
rules.
A
B
A
B
The
project
is
president:
we
had
some
reviews,
he
and
there
only
did
the
water
from
hands
months
for
the
artists,
automation,
infrastructure
now
I'm
trying
to
document
it
a
bit
and
review
the
meaningful
requests,
but
it
puts
fifty
boots
right
now,
so
yeah
they
certificate
is
yet
to
be
obtained.
But
at
least
this
measure
first
result
and
then.
C
B
It's
just
the
technical
process
so
spend
some
time
today
was
already
on
the
call
to
request.
They
stated
key
I
mean
I,
just
Lee
yeah,
it's
EDF
set
that
for
a
bigger
entity.
So
that's
why
it
took
so
long
because
we
needed
a
special
legal
entity,
his
very
foundation.
Then
they
created
the
digit
search
account
and
after
that
we
were
able
to
do
the
request
for
the
sixty
kids.
So
these
steps
are
done
and
now
we
just
need
to
get
a
real
certificate.
B
A
B
A
B
B
But
yet
there
is
more
than
100,
be
a
new
comer
contributors
and
it
was
history
high
months
for
Jenkins,
so
we
had
915
a
unique
contributors
and
almost
200
companies
contributing
so
yeah
really
Incans
and
let's
see
whether
we
can
retain
and
these
numbers
for
the
next
month,
probably
not,
but
we
could
always
try
yeah
regarding
the
rest
yeah
and
we
have
250
how
to
purchase
pool
requests.
So
these
are
confirmed
ones.
We
don't
know
who
exactly
participated
in
Oktoberfest.
So
it's
just
an
estimation.
B
Anything
regarding
their
changes,
I
put
some
highlights
in
the
list.
Yeah.
You
can
see
that
there
are
changes
here
and
there
you
know
what
is
might
have
for
that.
One
special
interest
route:
yeah,
it's
just
Li
a
lot
of
really
spot
documentation
updates
on
bombs.
Then
we
had
changes
inject
additional
scope
again,
so
hopefully
we
will
officially
move
with
two
basic
umbrella,
but
yeah.
B
There
is
a
lot
of
documentation,
a
lot
of
test,
a
framework
improvements
while
taking
the
ongoing
discussion
about
drink
is
2.19,
probably
not
not,
but
at
least
we
are
getting
somewhere
so
yeah.
There
is
a
lot
of
changes
there
and,
of
course
there
is
Marx
platform
level
plug-in
which
also
good
a
lot
of
economists.
B
A
Yeah,
what
a
great
story
that
is
yeah!
Thank
you
very
much
for
leading
that
effort.
That
plugin
documentation
story
in
particular
is
quite
amazing.
All
right.
We
had
a
crucial
infrastructure
challenge
with
the
wiki,
but
but
now
it's
turned
into
something
very,
very
positive,
as
you're
getting
much
better
plug-in
documentation
in
a
much
more
maintainable
location,
yeah.
B
B
A
A
Right
next
topic
that
adopt
openjdk
hotspot,
so
Jordan
thanks
very
much
for
being
here
with
us,
I'm
I,
don't
have
any
progress
personally
to
report
on
adopt
OpenJDK
hotspot
changes.
I
haven't
evaluated
that
I
used
my
time
to
evaluate
open
j9,
but
the
transition
poll
request
is:
let's
see
if
I
recall
correctly.
It
has
not
yet
been
submitted
for
this
one.
A
E
A
A
D
A
A
Hackfest,
definitely
not
I,
don't
know
if
they
plan
to
livestream
any
portions
of
the
conference
in
the
past
they've
livestream
the
keynote
addresses
about
I,
don't
know,
I,
don't
know,
I
haven't
seen
anything
saying
that
Lisbon
will
be
live-streamed.
I
know
the
San
Francisco
a
portion
of
it
was
okay.
E
B
E
E
B
B
A
B
A
Okay,
yeah
and
I
I
agree
with
alike
that
there's
no
issue
for
for
the
Jenkins
project.
As
far
as
I
can
tell
if
alpine
does
not
support
Java
11,
we
already
have
alpine
support
for
Java
8,
but
the
open,
JDK
team's
decision
to
not
support
Java
11
lobbies
that
we
don't
have.
We
it's
not
as
big
an
issue
and
I
haven't
heard
much
press
from
other
consumers.
Looking
for
Java
11
base,
open
JDK
or
Java
11
Alpine
support.
E
A
D
I
just
wanted
to
kind
of
run,
Digital
testing
to
make
sure
there
weren't
other
issues
that
need
we
fix
before
a
foal
like
nano
server
image
can
be
like
you
know,
approved
I
can
say
so.
I
did
try
and
get
some
of
the
stuff
going.
I
need
to
change
my
image
to
include
things
like
census
to
compile,
and
things
like
that,
so
I
haven't
had
a
chance
to
do
that.
Yet,
okay,.
E
If
you
need
any
help
with
that,
I
can
give
you
an
email
and
a
slack
channel
available.
I
can
just
put
it
in
the
sig
chat
and
then
I
also
want
to
just
say
that
adopting
is
really
excited
to
keep
moving
forward
with
you
guys,
they're
really
interested
in
becoming
more
involved
with
the
open-source
community.
A
D
Think
they're
fine
for
now
answer
her
I
submitted
a
PR
to
adopt
of
the
JDK,
build
nano
server
images
I
thought
my
guess
is:
they
will
only
be
in
the
unofficial
list
for
a
period
of
time,
but
at
least
it's
it's
rolling
that
I
had
issues
with
the
open
j9.
So
that's
why
it
was
not
submitted
this
play
that
ER,
and
so
this
work
is
to
be
able
to
on
support
open
gene
items
as
well
for
nano
server
I
see.
Thank
you.
Okay
and.
B
E
Lastly,
with
that
890
full
request
with
the
optimizations
with
the
open,
JDK
je9
image,
I
believe
it
was,
we
did
locate
that
individual
who
made
PR
requests
and
unfortunately,
today
his
manager
was
not
able
to
join,
but
there
is
Drive
behind
that
full
request
and
there's
active
work
going
on
with
that.
Behind
the
scenes.
A
E
D
Sure
so
there
is,
a
branch
has
been
created
in
the
packaging
repository
and
so
Oleg
changed
the
target
of
an
IPR,
so
that
which
is
great
so
that
is
kind
of
tracked
in
the
right
place.
He
also
made
some
suggestions
to
you.
The
pull
request
and
I
have
incorporated
those
changes,
so
I
think
it's.
It
would
be
good
to
get
some
more
eyes
on
it.
I
don't
know
if
there's
anybody
else
who
has
experience
with
with
windows
installers,
but
just
getting
some
eyes
on
it
would
be
good.
That's.
B
More
reviews
I
was
able
to
build
the
install
that,
maybe
two
months
ago,
I'm
tested
so
to
work.
Fine
on
my
machine
good
point-
and
this
is
it's
an
experimental
branch
I
think
we
could
you
just
go
ahead
and
break
it,
because
this
story
blocks
chorus
automation,
so
why
we
need
this
experimental
branch.
B
There
are
two
political
s.
One
is
from
Alex
to
consider
Windows
packaging,
but
we
cannot
know
right
away
because
it
would
impact
Kiki's
automation
for
Jesus
because
he
relies
on
scripts.
So
there
was
agreement
to
just
integrate
everything
at
once.
So
the
new
quote
on
this
automation
wouldn't
put
new
windows
packages
and
that's
why
we
need
this
story
and
integration
branch
is
a
group,
a
good
approach
for
us,
because
we
can
just
learn
this
change
and
even
build
something
from
the
top.
B
A
B
Thing
that
yeah,
since
we
have
this
automation
in
the
works,
maybe
we
could
adjust
the
kill
to
highest
and
test
the
beats
produced
by
release
automation
flow
right,
yeah.
Basically,
whatever
we
immerse
now,
it
won't
impact
the
production
in
20,
but
Jenkins,
weekly
or
LCS
reduces
so
that
we
can
be
quite
relaxed
out
what
we
integrate.
A
A
B
A
B
C
A
A
B
So
yeah
moccasin
a
difference,
daughters.
If
we
go
to
the
repository
which
we
already
discussed
few
times
the
packaging,
there
is
a
pull
request
for
yeah
for
new
built
environment
and
one
of
the
things
today
that
yeah,
that
is
quite
long,
to-do
list.
Okay,
what
works
is
expectation
is
not
marked
and
yeah.
B
There
is
a
reason
for
that,
because
you
know
our
sex
package,
you
need
Marcos
somewhere,
and
this
is
the
problem
for
our
new
environment,
because
it's
based
inside
kubernetes
yeah
thanks
to
Alex,
we
have
window
support,
but
we
don't
have
mono
support
and
the
basically
there
is
no
expectation
of
having
clicked
anytime
soon,
and
so
obviously
we
could
have
used
external
service,
for
example,
Mach
stadium
or
whatever,
to
build
these
images.
But
the
question
was:
were
they
really
make
sense?
B
B
Graphical
user
interface
installer,
so
therefore
Marcos
we
have
similar
installed
as
for
Windows,
but
yet
the
problem
that
we
cannot
really
build
it
and
the
idea
was
that
what
if
we
duplicate
it,
and
instead
of
it
just
say
that
homebrew
is
our
new
package,
which
we
would
recommend.
So
that
was
a
threat
in
the
developers,
made
a
list
about
that
and
need
to
build
the
consensus.
B
B
B
I
have
screenshots,
so
I
don't
need
to
run
anything.
So
we
will
have
a
new
page
which
basically
promotes
homebrew
is
a
default
package,
a
native
install.
It
will
be
still
there
but
difficut
it.
They
building
bulging
mirrors,
so
everybody
will
be
able
to
take
the
religious
and
that
these
packages
will
be
considered
as
a
third
party.
So
we
don't
make
in
them
and
setting
this
project,
but
yeah
they
will.
B
The
baby
will
be
still
available,
so
yeah
that's
the
depth
on,
and
that
is
also
a
blog
post,
which
belongs
to
that
one
of
interesting
thing
there
that
define
some
detail,
duplication
plan
and
this
plan
is
quite
complicated
a
because
we
cannot
say
when
we
release
confirmation.
So
what
I
did
here?
I
said
that
okay,
starting
from
the
next
weekly
and
next
LTS,
we
consider
the
pages,
is
duplicated
and
then
once
a
new
code
release
automation
for
who
is
done.
Basically,
we
will
stop
shipping
packages
yeah.
B
So
one
problem
there
is
that
ETA
has
security
implications,
because
if
you
stop
shipping
packages,
close
means
to
stop
shipping
security,
religious
for
those
who
use
packages.
So
there
is
some
mediation
guidelines.
Well,
I
think
I
was
unable
to
test
them
because
I
don't
have
much
choice
anymore,
but
yeah
this.
There
are
some
pointers
to
people
who
want
immigrate
so
yeah.
This
is
a
summary
of
the
story.
B
Reviews
are
pending
and
we
will
be
able
to
enter
them
soon
and
I
guess
that
the
documentation
is
also
similar
to
what
we
need
to
do
for
Windows
packages,
because
once
we
so
now
we
have
chocolaty
packaging.
So
maybe
we
could
do
something
like
that.
So
we
put
reference
in
storage
it.
Obviously
we
doing
duplicate
them,
so
they
would
be
involved,
but
we
also
pay
no
deference
homebrew
on
their
landing
page,
and
you
know
installation
guidelines.
Sorry
not
some
real
chocolatey
so
that
we
just
close
the
loop
there
and
have
better
documentation.
A
B
A
B
If
one
cost
packages
I
mean
it
generated,
no
need
to
change
anything
and
when
they
stopped
being
generated.
Okay,
a
we
can
kill
that
one
open
question
is
actually
weasel
tears
because
yeah
well
as
tempted
to
say
that
so
ten
new
baseline
is
2.2.
Oh,
for
this
is
the
discussion
with
the
developers
male
increased
now,
but
it's
not
uncommon
but
yeah.
B
Usually
our
process
said
that
we
don't
duplicate
anything
between
LCS
releases
and
he
it
may
might
happen,
but
for
the
one
is
released.
This
Monaco's
package
and
the
next
release
is
a
released
result,
among
course,
package
and
to
make
it
more
fun.
I'd,
maybe
also
a
security
release
so
yeah.
This
is
the
gap
which
concerns
me
a
lot,
but
yeah
I
think
that
in
this
case
you
will
just
cut
in
a
twisty
key
to
make
sure
that
the
two
or
the
three
releases
also
released
with
Marcos.
A
B
So
how
currently
work
so
if
you
go
to
packaging
day,
we
have
master
branch.
Basically
master
branch
is
used
for
weekly,
but
for
stable
releases.
So
there
are
other
branches,
so
you
can
see
them
there,
so
it
means
but
yeah.
It
is
French
for
the
currently
release
and
for
the
next
there
will
be
another
one
and
what
it
means
so
that
yeah,
even
if
we
integrate
this
experimental
branches
in
the
weekly
base
line,
it
won't
be
a
problem
for
years
and
yet
for
weekly.
If
something
stops
working,
okay,
we
can
live
with
it.
B
A
D
B
A
Alright
last
topic
is
on
broadening
platform
support
for
docker
images.
Actually,
this
is
one
Jordan.
Is
there
anything
that
you
needed
to
report
there?
I
have
not
had
any
further
conversations
with
these
potential
folks
and
so,
for
instance,
Oregon
State
University
with
their
available
images,
and
we
have
been
any
further
discussion
on
the
docker
image.
Auto
Bild,
so
I
was
prone
to
leave
this
topic
and
let
it
wait
for
our
next
platform
sig
meeting,
which
will
be
in
about
a
month.
A
E
A
A
A
Thanks
very
much
for
reminding
next
meeting,
so
our
next
meeting
that
would
be
scheduled
would
be
for
two
weeks
from
today
which
we
are
at
the
21st.
Okay,
so
I'm
just
gonna
bring
up
my
calendar.
It
would
be
the
fifth
of
December
no
way
I
will
be
unavailable
that
day.
So
then,
the
next
logical
one
would
be
the
19th
of
December
right
before
the
holiday
break.
A
B
A
B
A
B
A
B
A
So
my
I
apologized
last
night
I
had
to
go
to
bed
before
I
could
get
to
the
changelog
in
the
LPS,
so
my
mark
to
create
change
log
and
upgrade
guidelines
today.
So
you
will
probably
see
them
for
review,
as
you
start
your
working
day
tomorrow
that,
given
that
I'm
I'm
gonna
be
most
of
the
day
today
in
these
webinars-
and
it
won't
be
till
the
afternoon
my
time
that
I
start
on
them
so
delayed
until
reviews
until
Friday
morning.
B
A
D
B
So
just
the
for
information
yeah,
so
Martin
already
knows
the
story,
but
we
had
basically
in
the
pick,
your
poison
state
and
because
there
was
a
fix
for
assistance
model
on
the
star
top
in
version
2.1,
sorry
to
dot
$1.99,
and
they
were
just
a
recreation
discovered
in
Jake
asked
after
this
kicks.
So
you
know
we
check,
take
it
at
2.2,
for
these
some
cases
on
Jake
asked
site,
or
we
take
version
before
$1.99,
but
at
the
same
time
the
legitimate
bucks
and
contrition
man
and
safe.
A
B
A
D
A
B
B
A
A
C
B
C
D
B
Yeah
so
one
thing
committee
in
the
next
changelog,
so
the
next
we'll
see,
is
baseline.
We
all
need
to
put
the
comment:
the
packaging
changes.
So,
for
example,
if
you
want
some
look
at
the
image
on
new
platforms,
it
would
be
really
great
if
we
add
them
to
the
changelog.
Finally,
because
we
don't
do
it
right
now,
I
just
introduced
it
and
github
produces
a
little
package
and
this
summer,
but
I
think
of
it
this.
It's
that
this
major
highlight
should
be
in
the
main
change
log
and
pretty
much
the
same
for
duplications
like
MCOs.