►
Description
Sync-up about testing Java 11 support with Jenkins Acceptance Test Harness toolset (WebUI and integration tests). Meeting notes: https://docs.google.com/document/d/1cORivqvGbPJBm9O_fiY3JrST2aE7thHuJv47FKRz0jg/edit#heading=h.plak84qmvpho
A
Hi
today
we
have
a
shot
sync
up
about
Jenkins
acceptance,
test,
harness
and
javelin.
So
in
the
platform
platform
special
interest
group,
we
are
working
in
Java
eleven
support
and
there
is
a
good
progress
there.
So
effectively
we
had
a
meeting
on
Monday
where
you
can
find
all
the
information
it's
linked
from
platform
seek
page
and
one
of
the
workers
we
have
right
now
to
atleast
preview.
Availability
in
Jenkins
is
actually
a
test
automation
because
we
want
to
have
some
test
automation
and
Jenkins
test.
Harness
is
kind
of
done
now.
A
There
is
good
progress
with
speedy.
There
is
good
progress
with
acceptance
test
harness
by
Oliver
and
yeah.
This
meeting
I
would
like
to
just
sync
up
on
a
certain
stance
harness
to
understand
how
we
can
run
it,
how
to
test
it
and
what
is
more
important,
how
we
can
how
to
get
this
task
finalized.
So
I
have
created
sync
up
document,
so
I'll,
just
post
it
in
the
pod
from
cheap,
chug
and
chug.
A
Just
a
second,
oh
yeah,
I,
don't
shame
my
screen
right.
You
know
yep,
no
you're,
not
okay,
and
now
it's
one.
It
wasn't
very
useful.
I
bought
the
recording,
but
whatever
its
internal
thing.
Okay,
so
I
have
pasted
the
link
to
the
status
document
here,
import
from
chick
so
effectively
what
we
have
now
yeah
there
is
a
status
update,
presentation.
I
was
talking
about
so
it's
linked
here.
It
just
deletes
lists
all
the
current
information
and
current
progress
and
yeah.
There
is
a
pull
request
by
Oliver,
which
actually
adds
support
for
Java
on.
A
B
I
certainly
can
as
usually
no,
we
started.
You
know
putting
things
together
on
on
how
professor
needs,
and
at
that
point
the
automation
was
broken
because
of
switch
to
selenium
tree,
and
so
I
mean
to
working
for
us.
So,
ultimately,
the
quite
big
change
was
integrated
yesterday,
so
I
started
following
and
following
with
this
work,
actually
the
first
decent
build
of
the
effort.
I
got
running
this
morning,
preventing
sooner
so
you're.
Finally,
getting
some
test
results.
B
There
are
some
failures:
I
managed
to
briefly
look
at
the
ED,
where
we
are
we're
still
identifying
some
problems,
both
in
the
test
suite
and
in
some
of
the
pipeline
plugins.
So
it
would
be
able
to
us
to
have
look
at
the
result.
I
expect
it
to
complete
sometime
this
afternoon
today
have
a
look
at
where
we
are
and
we
can
start
working
up
until
now.
It
was
all
just
getting
thing
you
know
getting
at
us.
We
started
and
running
pace,
so
we
can
still
have
a
look
at
it
as
failures.
Yeah.
A
A
This
is
what
you
need
to,
including
the
ability
if
you
wanted
to
test
my
plan.
So
here's
the
latest
snapshot
I
created
yesterday,
because
batiste
also
does
experiments
with
every
ring
and
we
needed
to
top
stream
that
so
we
you
know
that
to
run
anything
against
pipeline
you
need,
but
otherwise
pipeline.
Just
friends.
B
A
B
A
Right,
I
just
put
it
to
the
stuck
with
a
status
document.
Okay
I
still
share
my
screen
right,
okay,
so
yeah
you
can
just
go
there
and
pick
a
reaction
from
there.
Okay,
before
that,
just
doesn't
make
sense
to
test
pipeline
they've
got
some
changes
integrated
on
the
core
side,
but
yeah
I
believe
that
true
150
eggs.
A
C
A
B
Right
I
put
together
Jenkins
file
in
a
way,
so
it
actually
builds
both
on
Java,
8
and
Java
11.
So
on
looking
at
Venapro
request
verification
now
seeing
in
the
CI
Jenkins
IO
is
probably
the
preferred
way,
except
that
there
is
a
way
how
long
should
locally.
Just
in
case,
you
would
like
to
experiment
or
quickly
iterate
locally,
but
I'm
afraid
this
is
not
documented
anywhere.
So
I'll
just
put
it
into
the
into
the
pork
butt,
so
people
can
have
logo.
A
A
C
B
B
As
I
said
until
yesterday,
we
were
stuck
that
some
even
more
essential
thing
didn't
work,
so
I
get
some
real
progress
on
that
last
night
and
this
morning,
so
it
required
some
changes
because
there
was
no
way
to
provide
these
enable
answers
about
what
about
those
optioning
to
actually
provide
this
tool
to
Jenkins.
So
why
get
it
smooth
since
this
morning
or
something
oh
I,
have
a
better
description
of
the
forecast
which
hopefully
I,
have
an
instruction
of
how
to
run
this.
A
And
just
a
second
I'm
refreshing,
the
page
for
you
so
enable
future
Java
Firefox
Altius.
Do
we
also
need
to
pass
specific
environment
for
javelin,
because,
if
I
recall
correctly
so
at
least
BCT
tests
for
you?
If
you
do
not
pass
models,
how
does
it
work
with
Java
11
I
mean?
How
does
it
work
with
acceptance
discovers
well.
B
B
Well,
I'm
trying
to
put
to
have
everything
run
against
that
and
see
how
far
it
goes.
This
is
the
first
decent
round
we've
been
running,
so
we
haven't
even
got
anywhere
close
to.
Actually,
you
know
evaluating
what
was
working
or
not
in
Jenkins
core.
We
have
this.
What
is
it
called
smoke
test
category,
which
is
a
very
small
subset
of
core
based
tests?
So
I
guess
it
would
be
a
very
nice
low
hanging
fruit
to
get
running
against
core
once
we
actually
make
sure
that
it
makes
sense.
A
A
A
B
A
204
sorry
jab
2,
1,
100
100.
So
here
we
have
testing
section
and
there
is
a
Google
Doc
which
actually
contains
all
the
tests
we
about
running.
So
now
it's
pretty
much
empty,
but
here
what
we
were
doing
for
jab
200
and
what
makes
sense
to
do
it
here
if
you
hit
any
issues,
just
put
it
to
this
Google
Doc
and
yeah.
If
you
submit
the
tickets
link
it
from
there
so
that
we
have
a
kind
of
central
document
for
issues
we
discover.
A
What
I
want
to
get
in
the
beginning
in
the
end,
reject
to
suddenly
believe
so,
injector
solvent.
There
is
also
testing
and
there
should
be
200
testing
nodes.
Oh
it's
a
pretty
big
document.
We
created
together
with
Jay
cyclic
and
some
other
testers.
It's
what
we
would
test
and
kind
updating
before
the
job
200
release
in
the
weekly.
Oh
yeah,
something
like
20
pages,
but
here
each
document
is
rather
something
like
that.
So
what
we
heat
what's
linked,
if
applicable,
pull
request
and
yeah,
that's
it
mm-hmm
for
job
200.
A
A
A
B
Yeah
I
mean
speaking
for
myself.
This
certainly
helps
more
guidance
of
what
to
do.
How
to
proceed
would
definitely
be
good.
Unfortunately,
I
do
not
have
you
know
enough
information
for
what
are
specific
areas
from
da
th
with
me
mean
hell,
because
that's
that
you
only
get
it
running
this
morning,
but
I
presume
that
they
would
have
that
tomorrow
or
something
like
that.
So
we
do
with
our
hands
dirty
player,
mm-hmm.
A
What
is
what
needs
to
be
done
on
a
th,
but
we
also
have
Jenkins
infra,
biplane
library,
Oh,
currently
Lincoln's
core,
so
in
Jenkins
core
we
have
enabled
to
Jenkins
test
harness
for
javelin,
but
we
didn't
enable
acceptance
test
harness
so
far
because
we
depend
on
this
running
th
step
and
they
advantage
of
this
run
it
each
step
that
actually,
it
allows
pinion
version.
So,
for
example,
since
you
are
doing
patches
in
your
repository,
it
would
be
possible
to
just
get
her
edgington's
Jing
means.
A
C
B
Think
review
whether
the
core
build
is
actually
have
a
healthy
round
of
ATH,
just
failing
or
something
terrible.
So
we
can
update
it
to
at
least
get
a
chance
to
succeed.
If
you
know,
even
if
it
would
work
for
Adam
and
I'm,
just
browsing
to
rerun
a
th
just
to
verify
whether
we
need
to
change
anything
on
a
first
place,
there's
a
chance
that
a
doctor
would
actually
make
the
changes
in
the
for
requests
in
ATH
I've
got
open
Whitney.
B
A
B
It
doesn't
seem
to
be,
you
know,
any
objection
of
an
interesting
discussion.
I'm
sorry
I
might
not
seen
your
comment
there,
but
the
point
is
that
one
would
certainly
help
me
to
finish.
This
is
to
have
a
way
how
to
get
it
tested
or
what
was
the
process
of
getting
it
actually
actually
deployed
to
CI
Jenkins
I,
oh
okay,.
A
B
C
A
We
come
again,
so
it's
already
big
and
the
meeting
schedule,
but
it
should
be
fine,
so
this
patch
already
allows
running
good,
but
we
need
to
somehow
support
both
versions
and
here
what
Oliver
implemented
in
this
pull
request,
so
yeah
I
believe
it
can
be
merged
right
now,
but
yeah
double
check
and
then
provide
review
feedback.
It.
B
A
Yeah
so
I
believe,
that's
it.
So
we
have
some
tasks.
We
definitely
need
to
do
to
get
all
the
stories
over
the
fence.
A
C
A
A
A
B
That
was
certainly
work.
I
understand.
There
is
quite
a
lot
of
you
managed
to
cover
real,
like
I,
mean
I
sort
of
envy
Oh,
like
that,
he
managed
to
understand
all
that
and
keep
track
of
all
this.
So
definitely
Oh
like
thank
you
for
bringing
it
all
this
effort
mm-hmm,
because
I
have
no
idea.
How
would
it
work
without
you?
I
do
quite
a
lot
to
cover.
So
perhaps
oh
you
guys,
if
we
I,
don't
know
narrow
the
scope
where
you
know
where
you
can
actually
go.
B
A
So
we
will
give
you
these
tusks
and
try
to
break
them
down
somehow.
So
there
are
many
people
on
this
call
and
yeah.
Let's
see
how
we
can
organize
together:
okay,
yeah
yeah
thanks
a
lot
for
doing
all
this
work
with
acceptance
test
harness
yeah,
it
should
really
help
and
yeah.
This
think
we
also
paint
a
bit
of
course,
okay,
and
do
we
have
anything
else
to
discuss
for
now.
A
A
A
So
Tuesday
it
is
then,
so
it
will
just
help
us
to
understand,
what's
left
on
the
quality
side
of
it
or
maybe
even
Wednesday,
because
I
would
also
like
to
involve
Kevin
it's
one
of
engineers,
working
with
test
automation
and
test
quality,
of
course,
but
yeah,
maybe
Tuesday
or
Wednesday,
most
likely.
We
will
need
to
rerun
ETH
with
pipeline
clocks
by
this
time
so
but
yeah.
If
we
do
that,
there
should
be
some
information
for
discussion
right.