►
From YouTube: Platform SIG: ATH and Java 11 sync-up, Nov 27, 2018
Description
Sync-up about testing Java 11 support with Jenkins Acceptance Test Harness toolset (WebUI and integration tests)
First sync-up: https://youtu.be/qymX7ubEAWQ
Meeting notes: https://docs.google.com/document/d/1cORivqvGbPJBm9O_fiY3JrST2aE7thHuJv47FKRz0jg/edit#heading=h.eoimylvyt8zg
B
A
Support
for
people
watching,
basically,
there
is
an
ongoing
effort,
led
by
mainly
Oleg
about
making
Jenkins
compatible
with
Java
11,
and
so
one
of
those
items
are
to
make
sure
the
acceptance
asanas
so-called
ATH
and
selenium
based
test
framework
for
Jenkins
is
accessible
made
compatible
with
Java
11.
Basically,
okay,.
A
B
B
So
I'm
just
creating
a
section
in
the
bottom
four
to
be
so.
Last
time
we
met
on
Friday
in
order
to
discuss
the
statuses
and
coordinate
on
the
effort.
We've
had
some
flops
like
so
one
of
the
major
things
that
Oliver
and
the
red
our
team.
They
have
already
launched
a
certain
stress
harness
in
eleven
so
that
we
could
probably
have
some
results
by
now,
but
we
know
that
there
are
some
pitfalls
they're
like
pipeline
compatibility
and
mine,
maybe
other
things.
So
what
would
make
sense
to
sync
up
to
understand?
C
Definitely
so
in
the
meantime,
we
managed
to
get
a
couple
of
healthy
rounds,
I
briefly
compared
a
number
of
failures
and
a
test
that
are
failing,
and
there
are
peers
to
be
just
one
more
extra
test.
Failing
for
eleven
after
we
have
integrated
the
fix
for
for
vertical
support
plugin
and
we
didn't
even
need
to
add
any
any
of
the
model,
a
model
overrides.
C
So
this
is
where
we
are
Matt
right
now,
I
started
going
through
the
individual
problems
on
fixing
them
as
I
as
I
find
them,
because
sometimes
the
text,
you
know
the
tests
are
failing
for
different
reasons.
So
there's
like
I,
don't
know
like
60
just
to
go
through
to
actually
validate
them.
So
this
is
what
it
will
be
doing
in
an
upcoming
days.
Yeah.
C
B
C
B
B
Okay,
but
anyway,
it's
great
to
see
that
it's
running
results
really
optimistic.
I
believe
that
current
acceptance
test
current
issue,
it
doesn't
include
ablution
acceptance,
test
harness
because
it's
a
supreme
Beast.
So
it's
a
separate
repository
which
we
do
not
run
for
community
s
flow
if
I
recall
correctly,
yeah.
A
B
A
B
Anyway
means
a
nice
progress,
so
one
of
the
questions
is:
how
do
we
profess
it
going
forward?
Because
we
still
need
to
integrate
it
into
a
jinx
pipeline
library
I
believe
so
that
will
enable
acceptance,
test
harness
run,
forging
his
code,
for
example,
and
there
is
still
a
number
of
patches
needed
to
do
that,
for
example,
dr.
image
and
probably
old
environment
settings,
because
you
need
to
pass
models,
etc
in
order
to
get
a
certain
size,
hardness
working.
C
Well,
I
guess
from
last
time
there
is
a
couple
of
leftover
items
for
us,
one
of
them
is
bumping.
The
the
version
of
a
th
is
running
as
a
part
of
core
PR
tests
and
perhaps
even
integrating
the
test
for
for
July
11.
So
I
guess
those
are
the
next
things
to
get
running,
to
see
some
real
progress
and,
in
parallel,
all,
would
like
to
work
on
polishing.
The
test,
feathers
of
a
th
itself.
B
B
B
C
D
D
So
now,
yesterday
evening
afternoon,
and
today,
I'm
going
to
compare
the
executions
between
July
8th
in
my
local
environment,
the
job
11
in
the
docker
container
to
try
to
classify
all
the
failures,
engineering
failures
or
just
environment.
Due
to
my
to
my
lab,
I
mean
I'm,
not
helpful.
So
far.
Due
to
that,
that's
my
my
contribution
so
far.
C
Right,
I,
just
there's
a
very,
very
short
full
up
on
that.
Please
know
that
it's
pretty
tricky
to
keep
the
firefox
in
with
selenium
that's
at
least
how
it's
been
for
for
number
two,
and
that's
the
reason
why
we
have
the
container.
So
for
a
long
time
we've
been,
you
know,
determined
to
use
the
container,
because,
basically,
none
of
us
has
the
compatible
Firefox
version,
which
was
laying
him
expected
much
less
about
having
everybody
compared
to
comparable
Firefox.
So
I,
don't
think
that
you
have
to
try
very
hard
to
get
it
working
on.
C
B
A
A
We
yeah
right
Oh
just
could
we
or
should
we
maybe
like
stars
to
an
email
thread
or
for
that
because
on
our
side
right
now,
it's
a
ramen,
that's
working
on
that
right,
so
ramen,
maybe
with
an
investor
ed
where
we
are
and
maybe
Oliver
and
maybe
more
people
on
Oliver's
side
trying
to
coordinate
or
maybe
not
doing
kind
of
exactly
what
ramen
you
were
doing.
But
you
know
focusing
on
some
given
test
because
Oliver,
you
know
it's
already,
probably
ahead
of
us
in
some
cases.
So
tonight
we
don't.
A
You
know
to
placate
him
first
and
we
try
to
adjust
actually
coordinate.
As
Oleg
is
saying,
I
agree.
It
was
simply
a
waste
of
time.
If
we
do
things
that
Oliver
already
I
run
the
I
guess
what
you
think,
how
do
you
think
Ramone
about
trying
to
better
understand
where
Oliver
is
right
now
and
trying
to
build
on
that?
Basically,.
A
C
Right,
as
I
said,
there's
probably
two
things
you
would
like
to
do
in
parallel.
I
guess,
you
know,
since
we've
been
maintaining
a
th
for
a
while,
we
have
an
advantage
against
all
of
you
right
since
your
order
to
productive
with
a
tool,
so
my
suggestion
would
be
to
narrow
down
that
bar
and
there's
one
thing.
We
have
successfully
finished
thanks
to
all
that
we
have
merged
to
build
a
plug-in
pipeline
library
step.
So
we
have
it
right
now.
C
A
So
to
summarize,
to
try
and
clarify
if
need
be,
Rahman
could
maybe
better
spend
time
working
on,
let's
say
critically
important,
plugins
I
guess,
like
so
heat
I,
think
maybe
he's
already
done,
or
maybe
not
maybe
one
of
the
good
things
to
adapt
or
to
try
to
use
ATS
there
who
didn't
make
sense.
Maybe,
for
instance,.
B
E
A
Definitely
I
now
remember
that
was
the
one
indeed
where
basically
raw
user
as
a
playground
and
frost
and
that
before
it
reached
it,
usable
state,
so
yeah,
basically
I
guess
trying
to
identify
the
the
biggest
plugins,
because,
apart
from
it
there's
a
few
of
them
and
focus
on
having
them
run
on
a
th
in
CI.
Basically,
I
was
interesting.
You
have
time
against.
Maybe
we're
basically
do
you
have
an
idea
River
about
a
plugin
that
you
think
would
be
the
most
important
one.
Maybe
after
get
or
whatever.
C
Well,
I
have
no
strong
preference
as
long
as
I
know.
There's
a
couple
of
this
support.
My
eleven
branches,
four
different
plugins,
so
I
guess
that's
something
that
might
be
interested
in
switching
to
this
new
way
of
invocation
and
other,
except
for
that
I
would
probably
start
with
those
pre-installed
by
you
know:
debris
installed
by
Jenkins
right.
B
And
other
focus
force
could
be
pipeline
plugins
because
we
know
that
the
rest
still
risks
around
pipeline
I
mean
these
dependencies.
So
if
we
speak
about
drink
estas,
harness
drink
is
test
harness,
it's
generally
covered
by
plug-in
compatibility
tester,
and
there
is
an
open
task
to
do
some
exploratory
testing,
because
a
part
of
a
weekly
je
availability
task
for
substance,
test
harness
yep
for
sentences
harness.
We
don't
have
specific
tasks,
because
we
rely
on
the
tester
on.
A
Agree
but
I
think
time
it's
yeah
such
a
different
beast
that
I
think
at
least
we
would
need
probably
some
lotion
developers
so
that
it's
actually
feasible
because
yeah
I
guess
it's
a
bit
specific
and
I'm
not
even
sure
how
to
start
this.
But
yes,
it
would
make
sense
from
an
overall
picture
standpoint,
but
yeah.
C
B
B
I
believe
that
we
should
just
take
the
topic
on
our
side
and
see
what
we
need
to
watch,
not
if
to
just
get
ETH
adopted
in
other
flows
like
essentials
test,
so
you
probably
will
just
get
it
together,
offline
and
then
as
but
it
suggests
that
we
can
start
a
thread.
Maybe
in
platform
seek
I'm,
not
sure
whether
it's
comfortable
for
you,
but
it
may
be
the
best
way.
I'll
give
it
a
shot.
You
get
er.
B
A
Know
but
I
for
some
reason:
I
wasn't
logged
in
okay,
right
and
so
here,
and
so
that's
the
place
and
there's
also
for
everyone
watching
the
special
interest
group.
That's
also
existing.
You
know,
outside
of
it
basically
does
initiative
in
the
chi-chi's
project.
So
thanks,
everyone
I
think
we
are
done
with
the
sync
up
anything
else
before
we
stop
the
broadcast
and
lean
against.