►
From YouTube: Jenkins & Java 10+ Hackathon. Day 5. Results and Demos
Description
At this call we present the Jenkins & Java 10+ Hackathon results and show demos: Running Jenkins on Java 10/11 with Pipeline, Easy-Jenkins project on Java 10, Building and Testing Jenkins plugins on Java 10, etc. Slides: https://docs.google.com/presentation/d/1hWWa6mYv86Kn8Ulu7uGlRJ9h2XTHlvHolO9CeRnnvcI/edit
Project doc: https://docs.google.com/document/d/1ed6wFOlq4cWrSL6UkCSzFbaY80AT-sk8ncB4Fz5QXyM/edit?usp=sharing
A
A
So
do
we
see
my
slides,
we
see
your
healing
screen
okey,
so
there
is
no
way
to
get
rid
of
that
yeah.
So
Jenkinson,
java,
10,
kakoton
and
today
is
a
big
five.
We
were
hiking
all
the
week
on
different
topics
of
Java,
ten
eleven
supporting
Jenkins,
so
we
are
going
to
present
some
results
we
achieve
giving
this
week.
So
I
will
have
a
brief
hackathon
introduction.
Then
I
will
have
a
status
updates
for
different
teams
and
then
we
will
perform
demos.
A
So
we
have
three
scheduled
demos
like
randomly
Jenkins,
with
Java
10,
easy
Jenkins
from
our
Jean
Paul,
and
also
building
testing
Jenkins
from
Sam
and
Devon.
If
somebody
else
wants
to
present
his
results,
please
feel
free
to
in
me,
after
the
demos,
and
we
will
conduct
additional
demo
sessions.
If
you
interested
to
ask
any
questions
that
we
have
a
channel
in
Peter,
so
it's
a
Jenkins
Jenkins.
You
can
log
in
there
and
ask
any
questions.
So
colleagues
on
the
call
will
be
monitoring
these
sessions
and
then
they
will
ask
questions
to
me.
A
A
Java
11
LTS
is
coming
soon,
I
presume
Utley
in
September
2018,
and
we
ain't
interested
to
keep
jenkins
up-to-date
in
order
to
make
it
available
for
users
as
soon
as
possible.
So
previously
we
did
some
operation,
for
example,
as
a
part
of
jenkins
world
hyper
tones
and
in
offline,
and
then
we
decided
that
we
want
to
have
a
kind
of
online
hackathon
and
of
the
to
push
this
efforts
to
get
something
working
and
to
make
relation
packages
available.
So
it
was
our
interest
for
this
heck,
and
that
is
what
we
are
going
to
present.
A
But
yeah.
One
of
another
objectives
was
to
just
work
together,
share
experiences
and,
of
course,
have
fun
so
that
everybody
of
participants
would
have
an
opportunity
to
chart
to
study
something
about
Jenkins
or
maybe
to
contribute
something
interesting
and
we
have
had
several
contributors
who
did
live,
shows
contributions
to
join
his
during
this
happy
time
so
yeah,
that's
it
I'm
going
to
present
some
results.
Later
generally,
we
had
25
contributors.
A
It's
an
approximate
number
I
still
need
to
calculate
how
many
computers
behind,
because
we
bare
your
people
are
doing
some
exploratory
testing,
reporting
issues
or
doing
three
misses
force.
So
I
would
expect
this
number
to
grow
a
bit
and
we
had
several
teams.
One
of
the
teams
was
working
on
core
and
packaging
beads.
We
were
working
on
pipeline
Sam,
Jeff
Damian
Nicola
also
spent
a
lot
of
time
when
development
tools
in
order
to
have
a
test
and
build
flows
running,
and
he
also
had
people
doing
exploratory
testing
in
different
areas.
A
So
I
will
just
summarize
status
updates
before
the
meeting
teams
provide
updates
in
the
Google
document,
so
I
just
copy-paste
to
be
some
dates
and
polish
them
a
bit
so
for
junk
discordant
packaging
in
order
to
support
Java,
10:00
and
11:00,
mostly
to
pipeline,
we
needed
to
apply
fixes
like
awesome,
Ruby,
bytecode,
transport
net,
also
gene
our
packaging,
etc.
In
order
to
do
that,
we
created
separate
feature
branches
for
Java,
10
and
11.
We
set
up
continuous
delivery
for
what
undoctored
packages
and
now
everybody
is
able
to
just
try
them,
and
there
are
links
here.
A
So,
if
you're
interested
to
try
packages,
you
can
just
go
to
this
blog
post,
and
here
you
may
see
how
to
run
Jenkins
in
a
Dockyard.
We
have
several
images
like
Java
weekly
releases,
also
latest
from
our
feature
branches
lotion.
This
pipeline
bundle,
which
runs
that
out
of
the
box,
and
you
if
you
want
to
run
locally,
it's
also
possible.
So
there
are
run
examples
for
jawad
10
and
Java
11,
whichever
11.
You
also
need
to
do.
A
Okay,
this
all
the
way,
the
core,
the
garden
pipeline.
Our
major
update
that
we've
got
my
plan
working
when
you
start
in
the
hackathon
and
pipeline
was
flashing
immediately.
Nothing
worked,
but
after
several
hits
us
in
the
core
in
packaging
in
pipeline
support
planning,
we
were
able
to
get
all
major
features
of
pipeline
working,
including
declarative,
pipeline
scripted
pipeline,
shared
libraries,
etc,
etcetera
and
lotion,
as
you
may
see,
on
the
screen
also
works,
and
if
you
want
to
try
it,
you
just
need
one
command.
A
A
Regarding
development
tools
and
we've
had
an
objective:
firstly
ensure
that
we
can
test
core
and
plug-in
patches
on
Java
10,
so
we
are
sure
that
we
ship
working
leads
for
them
and
then
there
was
an
interested
to
fix,
I
built
and
build
tools
in
order
to
support
Java,
9
plus,
but
without
break
in
a
Java
each
compatibility.
So
there
was
lots
of
work
around
it
as
I
said:
Sam,
Nikhil,
Jeff,
Darin
and
also
Oliver
Ptolemy,
and
probably
a
missing
other
contributors.
A
Clean
up
labeled,
objective
access
warnings
in
Jenkins
core,
so
it's
under
development,
but
it's
also
available
for
evaluation,
a
nucleolus,
a
explored
how
to
build
Java,
8
and
Java
10
plugins.
So
all
main
problem,
a
bit,
maybe
in
compiler
plug-in,
is
still
not
compatible
with
such
mode.
Obvious
multi
released
jars
and
we
needed
a
workaround.
So
Nicoli
did
some
exploratory
testing
and
you
can
find
his
blog
post
about
how
to
do.
It
is
Jenkins
examples
so
yeah,
if
you're
interested
you
can
just
follow
this
link
and
sneak
out
and
be
done.
A
It
will
be
million
now
just
follow.
The
religious
survey
will
share
all
these
slides
after
the
presentation
and
the
link
is
already
she
ate
in
the
chat.
So
if
you're
interested,
you
can
just
join
and
follow
the
links
and
regarding
exploratory
testing
yep,
there
were
many
contributors
joining
cars
and
the
exploratory
testing
was
one
of
them.
Newbie
friendly
tasks
and
we've
got
lots
of
evaluation
for
different
bits,
including
pipeline
blue
ocean,
many
popular
plugins.
A
In
our
instances,
we
may
test
that
maybe
two
hundred
of
plugins
in
total
it
means
most
smoke
tests,
but
they
work
also
major
features
like
configurations
code
work
well
with
Java,
10
and
11
and
yeah.
We
should
test
that
we
low
support
it
works
well.
So
we
feel
that
a
very
good
problems
with
support,
then
we
updated
the
documentation.
So
there
is
a
new
Java
support,
page
pending
preview.
There
are
some
plug-in
pull
requests
and
releases
submit
by
our
contributors
and
those
demo
project
updates.
A
A
So
what's
next,
we
have
a
lot
of
high
arches.
Some
of
patches
still
meet
a
intimidation,
so
some
library
patches
on
the
review
and
we
want
to
integrate
them
at
some
point.
We
also
want
to
top
stream
patches
too,
but,
of
course,
to
be
clear
releases.
We
also
already
start
this
problem
process,
but
it
will
take
a
while.
We
need
to
decide
how
we
approach
pipeline
support
plug-in
in
order
to
get
it
available
to
users
so
yeah.
There
are
lots
of
things
ahead
and
we
need
to
decide
how
we
approach
them.
A
So
it's
just
from
the
top
of
my
head.
What
we
need
to
do
and
today
we
will
have
a
discussion
what
else
we're
missing.
Actually
the
next
agenda
item
was
demos
but
yeah.
Since
we
have
many
contributors
on
the
call
we
could
defeat
because
the
status
and
what
we
want
to
do
next.
So
if
anybody
wants
to
make
any
comments
about
the
status
and
about
the
next
steps,
please
just
tell
us
about
it:
yeah.
B
A
So
for
extreme
etc.
We
have
issues
with
illegally
reflected
foxes,
so
it's
one
of
the
major
issues
in
Java
9
and
beyond,
and
we
had
a
lot
of
a
long
discussion,
this
project
to
jigsaw
contributors
on
Wednesday
about
it.
So
we
want
to
clean
them
up
and
there
are
ongoing
activities.
So,
for
example,
this
mini
library
from
Nicola
is
one
of
potential
approaches
to
clean
up
for
this
leg
of
a
reflective
foxes,
and
there
are
many
other
patches.
So
Nicola
was
started
from
step
layer,
warnings
and
from
extreme
warnings
and
that's
how
he
got
there.
C
To
like,
for
most
of
the
you
know,
third-party
dependencies
we
had
most
of
the
issues
were
like
well
like
I,
saying
just
that
illegal
reflective
access,
which
is
not
currently
you
know,
a
serious
blocker,
so
most
of
the
stuff
we
were
focusing
on
at
first
was.
We
cannot
compile
at
all.
We
cannot
test
at
all.
We
cannot
run
pipelines
at
all,
but
it
turns
out.
You
know
like
that
extremes.
Illegal
reflective
access
certainly
should
be
cleaned
up,
but
for
now
there's
not
like
any.
You
know.
A
We're
not
going
to
ship
Java
ten
support
tomorrow
for
sure
yeah.
We
did
have
a
great
progress.
Many
things
work
libraries
will
likely
need
more
updates.
We
also
reported
a
lot
of
issues
about
potentials
patches
nudity
in
a
virus,
signature
libraries,
but
yet
there
are
still
things
to
do
thanks
cream.
Any
other
questions.
A
A
Okay,
so
I
have
a
package
which
is
based
on
a
GD
key
blows
and
Emma.
So
just
it's
my
computation
s
code,
so
it's
based
on
the
stock
valuation
dome
demo,
Bishop
I've
started
it
and
yeah.
Here
you
may
see
that
Jenkins
is
actually
starting.
You
may
see
a
new
login
screen
introduced
in
the
latest
weekly
release,
so
we
are
up
to
date.
It
may
take
a
while
for
Jenkins
to
start
up
because
it
has
configuration
is
code,
including
contributors,
code
plug-in
and
some
groovy
streets,
but
yeah.
Here
we
are.
A
And
here
we
see
the
demo
so
in
this
demo
may
see
that
there
is
ablution,
but
there
is
a
development
environment
with
some
pipelines
and,
for
example,
I
have
pipeline
library.
It's
a
fork,
not
a
fork.
It's
just
a
local
development
instance
for
edge
in
case
I
own.
It's
a
Jenkins
on
Jenkins
instance.
We
use
in
the
Jenkins
project
to
run
continuous
integration
and
I'm
going
to
run
one
of
the
demos.
So
this
demo
just
executes
a
pipeline.
A
So
you
just
run
your
Jenkins
instance
on
Java
10,
like
you
would
run
it
on
Java
eat
in
docker,
so
it's
fully
compatible
with
all
standard
packaging,
and
this
is
John.
Paolo
will
present
it
more.
So,
let's
take
a
look
at
our
pipeline.
Give
me
city
it's
building
something
running,
and
here
you
can
go
that
and
see
that
blue
ocean
is
also
works
with
all
incremental
things
in
place
once
it
completes
the
built,
it
will
publish
tests,
artifacts
and
other
things.
I
will
probably
not
spend
time
on
that
because
we
have
been
next
to
them.
A
A
So
actually
that's
all.
For
me,
this
demand
may
look
boring
because
everything
works,
but
they
actually
it's
one
of
the
main
actions.
Music.
All
of
the
patches
use
all
of
the
custom
tweaks.
We
have
got
it
working
and
the
we
haven't
even
discovered
any
broken
features
so
far,
but
we
tried
all
of
us.
They
almost
have
to
be
so.
For
me,
the
most
challenging
thing
honestly
was
to
build
lotion
because
even
without
tests,
it
took
something
like
40
minutes
on
my
machine
to
package
it
and
regarding
the
court.
A
I
would
say
that
the
challenging
thing
was
to
just
a
great
all
our
purchased
as
new
releases,
because
there
were
lots
of
things
and
actually
this
work
hasn't
been
done
only
by
me.
Some
did
a
lot
of
artists
that
work.
I
find
support,
I
mean
then
you
he
helped
us
miss
as
rapid
bundles
Devon
contributed
watches
to
join
our
support.
So
even
if
I
demoed
it
it's
not
just
my
effort
is
a
team
effort
mean
during
this.
A
D
Hopefully,
I
am
sharing
my
screen
now
and
good
evening
from
the
litany.
I
am
unfortunately
I'm
out
of
the
office
opening
a
conference,
so
I
hope
that
my
letter
connection
will
not
betray
me.
Someone
confirm
that
I'm
displaying
something
yes
miss.
You
scream,
ok,
so,
first
of
all,
I
really
appreciate
having
taken
part
of
this
packet
of
I
am
not
dead,
a
junkie
developer,
or
at
least
ie
warden
until
this
week
and
I
really
thank
to
be
the
other
colleague
supporting
me
to
be
able
to
achieve
such
what
I
did.
D
So
just
flown
the
rifle
easy
Jenkins
and
then
run
me
and
that's
it
so
that
supports
a
number
of
contain
and
SBM
results.
You
will
get
the
URL
and
initial
password
to
populate
the
the
detector.
There
is
a
photo
so
far,
but
I
said
it
was
not
easy
for
me
at
the
beginning
and
I
try
to
make
it
easy.
The
result
you
have
is
the
usual
rankings
based
on
Java
10.
D
So
there
is
a
smaller
Android
after
they
running
with
the
on
a
container
on
a
given
a
PDK
that
they
used
on
these
very
target
I've
been
using
it
to
kind
of
the
Raspberry
Pi.
There
is
a
subset
of
the
agility,
the
platform
support
that
they
have
not
enough
volume
on
my
local
machine.
So
this
build
is
breaking
broken
for
the
purpose,
but
I
will
show
on
a
more
powerful
machine.
I
have
in
the
office
that
depth
actually
works
quite
well,
so
some
HTML
publisher,
some
simple
doctor
file
and
whatever.
So.
D
Basically,
we
try
to
test
the
the
most
important
relevant
plugins
we
have
been
using
in
our
real
development.
We
are
doing
in
the
in
the
work
so
and
not
particularly
thanks,
except
that
this
is
working
and
worked
quite
well
after
the
initial
fixes
were
made
earlier
this
week
and
I
was
able
to
catch
up
the
thanks
to
the
support
of
the
of
the
people,
organizing
this
hackathon
and
I'm,
just
verifying,
as
you
did
earlier,
that
I
really
running
the
Java
10.
D
Ok,
let's
move
to
this
machine,
so
I'm
tallying
link
to
SSH
to
the
office.
So
this
is
the
mighty
mini
pipeline.
So
if
someone
has
ever
been
a
medium
we'd
be
jdv,
so
this
is
an
open
source
project
or
making
a
Linux
and
open
source
surveys
in
vehicle
if
attainment.
So
this
is
the
let's
take
the
DP
master,
so
the
master
branch
of
the
optically
double
image.
D
It's
a
built
completely
on
sources,
the
bootloader
Linux
kernel,
a
user
landed
many
application
up
to
104
gigabytes
binary,
it's
about
60
million
line
of
code
that
are
compiled
around
8
hours.
If
I
remember
how
long
it
took,
let's
just
check
much
to
clearing
the
beast.
So
part
of
the
challenge
for
me
was
to
wait
until
the
the
build
was
completed
and
it's
a
prophecy
a
couple
of
times
during
the
week.
But
after
last
iteration
everything
was
good.
D
So
at
the
moment
I
have
no
broken
deals,
except
for
one
on
the
hosts
that
have
not
enough
capacity.
So
take
this
example,
so
they
this
was
a
complete
stretch,
build
that
took
about
nine
hours
on
a
8
tor
machine
with
16
gigabytes
of
RAM.
So
it's
not
for
the
faint
of
heart,
but
this
is
how
we
are
building
the
real
embedded
of
the
development
in
entertainment.
And
for
me
this
is
a
non-trivial
use
case
we
put
into
into
test
during
this
week.
D
D
The
dockerfile
will
be
stable
at
the
moment
I'm
using
the
experimental
branch
on
dog
the
base,
doctor
image
and
Calif
full
of
plugins,
namely
the
workflow
support,
and
probably
this
is
the
only
one
now
this
morning.
I
also
try
to
work
with
the
configuration
and
thought
because
for
the
use
cases
we
are
playing,
it's
really
really
helpful,
and
this
is
the
other
fix.
I
will
try
to
progress
after
they
act
and
if
there
are
no
question,
that's
the
end
of
my
demo.
D
A
D
D
B
A
E
B
Then
we
have
to
be
delicious
all
over
then
at
the
end
is
office.
He
runs
on
em,
like
no
special
cities
necessarily
enter
it's
going
to
be
tough
to
think
instruct.
No,
he
does
no
no
crusty
fun,
there
are
snow
nothingness
and
then
it
comes
up
and
then
the
plugin
that
is
the
axpy
it
works.
I
find
some
random
plugins
that
that
does
something
to
do
with
the
RPM
package
vehicle
and
then
it
verified
at
Delphi
that
it
works.
B
B
Hey
I
think
I'm,
you
know
what
the
computer
the
hole
is
having
with
each
other,
so
I
guess
he
liked
it
just
by
one
at
least:
hey
didn't
we
touchscreen,
you
didn't
see
anything
internal
at
the
start,
which
is
kind
of
already
yet
it
signs
that
it's,
let's
see
it's
probably
padded
and
I.
Think
I'm
gonna,
like
a
handi-vac
deity
for
this
type
of
airs.
A
A
E
A
E
All
right,
so
one
of
the
key
challenges
we've
faced.
We
were
very
lucky
to
get
pipeline
billing
initially
without
too
much
extra
work
beyond
what
was
put
in
up
front,
but
we
found
that
a
lot
of
very
basic
things
didn't
work.
So,
for
example,
it's
it's
impossible
to
build
Jenkins
directly
with
Java
10.
That's
the
compiler,
a
lot
of
the
core
plugins
maintenance,
dev
tooling,
as
well,
will
fail
things
like
annotation
processing
things
like
code
and
a
lasat
static
analysis
and
all
the
access
modifier
stuff.
E
There's
also
things
like
differences
in
way
the
module
structure
works.
That
mean
we
need
to
start
looking
at
the
multi
release.
Jars,
so
I
won't
go
into
too
much
detail
in
each
of
these,
but
Nikolas
did
some
investigation
on
multi
release
jars
and
put
together
a
very
useful
blog
post
from
that
a
variety
of
different
people
have
submitted
fixes
upstream
for
a
different,
tooling
I.
A
E
E
Okay,
so
you
sorry
go
back
to
master
it's
all
here.
I'll
show
you
the
outcome,
so
this
is,
after
applying
a
series
of
fix
this
to
the
palms
and
building
on
top
of
some
of
the
initial
Jenkins
runtime
fixes
primarily
fixing
some
broken
annotation
processing.
Let's
see
it,
it
builds
and
compiled
successfully
I'm,
not
running
tests
right
now.
We
do
still
have
a
few
test
failures
and
find
loads,
of
course,
doesn't
work
with
this
version
of
the
system.
E
If
I
go
back
to
our
master
branch,
though
you
can
see
that
up
slightly,
this
is
the
wrong
IPV
session.
Let
me
go
back
to
chicken
score
here.
We
go
there.
We
go!
That's
that
that's
what
it
should
look
like.
You
can
see
that
this
is
building
the
original
master
branch.
Before
the
changes
you
can
see,
it
fails
very
quickly.
It
doesn't
even
make
it
to
the
core
plugin.
E
E
E
E
E
So
that's
there's
a
little
bit
of
standing.
Work
still
left
to
do
there
yep
fully
fully
up
and
running,
but
even
the
fact
that
we
can
get
these
tests
running
I
think
is
further
than
we
were
expecting
at
the
beginning.
A
pack
best
I
think
that
what
it
looks
like
what's
what's
left
will
be
manageable.
E
A
A
A
F
And
I
can
give
a
quick
summary
of
just
what
we
tried
and
what
we
learned
this
week
was
mostly
testing
out
the
docker
container
at
first,
and
that
was
nice,
because
Oleg
had
set
that
up.
It
was
pretty
straightforward
to
to
run
it,
and
especially
once
pipelines
was
running
then
to
just
go
through
and
test
it,
and
then
on
Wednesday
was
a
main
session.
We're
invited
Jonah
Graham
to
join
in,
and
we
did
some
sort
of
pair
programming
around
development,
so
I
guess.
F
The
first
thing
was
that
yeah,
it
was
just
really
straightforward
to
get
set
up
with
the
dev
environment.
Oh
like
did
a
good
job
on
just
giving
us
what
to
expect,
and
we
sort
of
took
that
and
with
the
instructions
on
the
web,
it
was
very
straightforward
but
to
set
up
for
individual
plugins
and
also
just
get
that
set
up
on
core
development.
Yes,
that
was
the
easy
part.
F
F
We
start
looking
at
things
and
just
realize
that,
well
it
looked
like
it
was
likely
we
could
just
get
rid
of
the
use
of
fine
class
or
something
it
seemed
like.
You
really
needed
to
have
a
deep
understanding
of
the
architecture
or
the
intent
when
someone
put
it
there,
so
it
wasn't
necessarily
going
to
be
straightforward
to
just
say:
oh
well,
this
is
what
we
think
it
should
be
and
we
could
change
it,
and
that
will
be
that
yeah.
So
we
ended
up
starting
to
look
at
and
I
guess.
F
F
Having
said
that,
then
it
led
to
this
whole
issue
of
well.
We
can't
just
update
to
Java
9
or
Java
10
api's,
because
have
this
multi
jaw
issue
solved
player,
focusing
just
to
sort
of
see
how
that
involved,
yeah
and
then
loads
at
the
with
the
Java,
SE
folks
and
jigsaw.
Folks
I
think
was
interesting
to
hear
about
the
signal,
because
we
looked
at
signal
fixes
as
well
and
yeah.
F
I
think
it
just
makes
sense
that
Java
they
have
to
provide
a
new
library
to
replace
that
and
it
doesn't
make
sense,
do
deprecated
those
but
yeah.
Overall,
it
was
a
lot
of
fun
I,
really
like
the
fact
that
everybody
was
doing
things
and
it
was
progressing
and
certainly,
from
my
perspective,
I
hope
it
does
become
a
regular
thing,
which
does
seem
to
be
necessary
just
to
keep
up
with
the
quick
changes
in
Java,
so
yeah,
looking
forward
to
to
the
next
one
where
we
won't
be
newbies
as
much.
A
Yeah
with
regards
to
the
next
steps:
yeah,
you
have
jenkins
world
events
in
autumn
so
like
we
would
be
organizing
something
like
heck
it
on
there.
So
if
you
come
to
these
events
reach
out
to
us,
maybe
we
set
up
some
time
to
work
on
java
11
support.
Maybe
at
that
time
or
maybe
something
else
and
yep,
it
was
a
just
online
hackathon
experience
for
our
project.
I
would
say
so
yeah.
A
F
One
last
thing,
I
think
I'd
like
to
say
yeah
a
big
thank
you
to
yourself,
Oleg,
just
for
pulling
everything
together
and
making
us
feel
and
I
think
you've
just
been
there
for
every
day.
Every
session
on
hand
to
deal
with
people's
issues,
so
I
think
he
just
couldn't
have
gone
as
well
as
it
did
without
the
work
and
effort
you
put
in
so
I'm
gonna
ask
everybody
on
your
mics
and
let's
get
Oleg
a
big
round
of
applause.
If
you
can
virtually
so.
A
But
yeah
just
honest
I
wouldn't
be
able
to
do
it
alone,
so
there
was
lots
of
prep
work
and
Tracy
named.
Who
is
unfortunately
not
on
the
call
today.
They
also
helped
us
a
lot
to
get
it
running,
but
then
they
were
Jenkins
contributors,
helping
us
miss
doing
releases
so
yep.
It
was
a
major
community
effort.
We
will
do
some
preparation
metrics,
but
it
wasn't
just
about
a
lake.
It
was
a
huge
community
of
work,
so
I'm
happy
that
there
was
a
part
of
it.
E
Spreading
credit
around,
although,
like
you
and
Liam,
did
a
really
great
job.
Setting
this
up
and
I.
Think
having
so
much
of
the
tooling
and
the
environment,
ready
to
go
and
the
instructions
ready
to
go
made.
It
possible
to
just
focus
on
getting
down
to
fixing
things
right
off
the
bat
and
that
made
a
huge
difference
for
us
made
for
a
very
effective
hackathon,
I
thought
and.
C
D
A
Thank
you,
John
Pollock.
It
was
really
interesting
to
see
this
easy
gentes
project
as
well.
Actually
yeah
I've
seen
Geneva
project
before
sometimes
so,
but
yeah,
it's
great
to
see
that
there
are
some
efforts
on
automation.
There.
Tracy
is
also
from
hardware
name
by
this
space.
So
basically,
okay,
yes,
so
yeah
I,
guess,
let's
eat.
So,
let's
try
all
projects
we
create
it,
and
if
you
want
to
try
a
Jenkins
on
Java
10,
everything
is
available
now.