►
From YouTube: Jenkins UX SIG Meeting 24 Nov 2021
Description
User experience SIG meeting with Ildefonso Montero showing Jenkins customizable header and Jan Faracik showing most recent changes and ideas being explored for the future.
1:34 JEP-234 Jenkins customizable header
22:32 UI improvements in Jenkins 2.319.1
23:17 Upcoming UI improvements
1:02:32 Search bar idea being explored
A
A
A
C
A
A
A
B
B
Main
idea
here
is
mostly
or
how
I
reason
this
approach,
and
what
motivates
me
to
do.
That
is
because,
right
now,
if
we
want
to
update
this
header,
we
need
to
use.
We
have
several
approaches
to
follow
like,
for
example,
use
the
simpleson,
plugin
or
other
approaches
regarding
this.
That
is
mostly
based
on
try
to
customize
css,
javascript
or
other
static
content,
but.
B
Also,
there
are
other
alternatives
like,
for
example,
using
this
mac
diff
patch,
medium
plugin.
That
also
can
help
us
to
replace
some
parts
based
on
static
content
also
basis
on
patches,
mostly,
but
I
tried
to
set
up
a
dummy
example
to
illustrate
what
I
wanted
to
do,
which
is
mostly
here.
It's
mostly
okay,
with
this
tooling
that
they
have
these
days.
B
Can
I
create
a
new
header
to
set
up
a
kind
of
configurable
message
and
also
other
other
things
from
the
header
like,
for
example,
using
why
not
two
or
three
or
whatever
search
boxes
or
whatever
so
main
idea
here
was
try
to
make
this
to
happen
and
identify
things
to
that
can
be
improved
on
that
plugins
or
also
on
the
jenkins
core.
So
for
that
purpose,
I
I
realized
that.
Finally,
simple
thing
plugging
was
not
enough.
B
I
can
do
it,
but
has
to
that
requires
me
to
do
a
lot
of
hacky
things
which
are
not.
I
don't
like
it
to
be
honest,
the
solution.
I
will
prefer
to
have
something
on
on
jenkins
core
that,
as
for
other
components,
provide
me,
the
extensibilities
and
the
capabilities
to
perform
this
in
a
cleaner
manner,
mostly
using
extension
points.
B
B
So
what
I
did
is
to
set
up
oh
well.
Let
me
show
you
what
what
is
exactly
what
I
wanted
to
have,
at
least
for
this
example,
which
is
something
like
this
okay.
I
was
trying
to
do
something
quite
simple
like
having
a
quick.
This
is
you
know
it's
so
simple,
but
it's
trying
to
illustrate
what
I
was
looking
for.
Okay,
it's
trying
to
include
a
new
search
box
here,
also
including
here,
a
new
label
which
could
be
custom,
disabled.
B
B
What
I
wanted
to
do,
then,
is
to
try
to
use
extension
points
or
try
to
set
up
the
header
as
an
extension
point,
first
of
all
trying
to
set
up
expectations
here.
If
you
in
case
you
didn't
read
the
the
jab
jet
I
was
trying,
I
was
not
trying
to.
I
think
it's
a
good
idea,
but
I
was
not
trying
to
in
perform.
B
Extension
points
for
each
section
of
the
header
I
mean
I
am
going
to
do
an
extension
point
for
the
total
replacement
of
the
heater
by
itself.
I
was
not
proposing,
I
think
it's
a
good
idea
and
can
be
a
follow-up
of
this
jet
to
have
an
extension
point
for
modifying
or
doing
an
incremental
change
for
the
logo,
for
the
message
about
jenkins
branding
for
the
search
boxes
for
the
administrative
monitors,
etc,
etc.
Okay,
but
this
is
not
the
scope
of
this
jet.
This
is
this.
B
B
Also,
this
extension
point
here
provides
a
method
that
I'm
going
to
come
back
later
to
this,
but
it's
called
get
it
and
it's
mostly
doing
a
search
for
all
the
extensions
loaded.
All
the
extension
points
from
headers
that
are
enabled
okay
trying
to
get
all
the
headers
that
you
can
provide
the
plugins
and
providing
you
the
first
one.
B
The
first
one
is
because
we
are
introducing
I'm
going
to
show
you
later,
but
I
can
show
you
in
advance.
We
are
using
the
ordinal
from
the
extension
to
try
to
set
up
a
prioritization.
I
mean
I
can
prioritize
what
header
wants
to
be
rendered
based
on
this
on
this
value.
Okay,
if
there
is
no
header
enabled,
we
will
provide
the
junkies
heater
as
the
default
heater,
okay
and
jenkins
heater.
B
Now,
it's
being
refactored,
it's
a
new,
a
new
extension
point:
it's
not
in
the
jenkins
core
yet,
but
based
on
this
approach,
it's
a
new
heater
and
it's
always
being
enabled
by
default.
Okay,
so
given
say
that
if
I
have
a
jenkins
code
with
this
capabilities,
I
am
able
to
create
a
custom
plugin
for
setting
up
any
header.
Okay,
and
I
can
provide
a
header
like
I
was
looking
for
in
the
example
that
I
showed
you
before.
B
So
this
approach
is
reducing
to
the
minimum,
the
that
fi
that
resource
from
the
core,
mostly
invoking
the
method
get
of
the
extension
point
header
and
try
to
inject
the
content
of
the
header
provided
by
each
plugin.
So
we
move
the
entire
pitch
header
jelly
from
the
jenkins
core
to
a
new
file
called
header
content,
and
this
header
content
is
provided
by
this
jenkins
header.
Okay,
if
you
create
a
new
one,
you
should
provide
a
new
header
content
and
that
heater
content
can
be
called
as
you
prefer.
B
Okay,
one
important
topic
here
is
about
the
backward
compatibility
we
try
to
guarantee.
But
what
compatibility
here
in
this
approach
by
means
of
introducing
two
intermediate
extension
points,
which
are
the
full
header
and
the
partial
header
full
header-
is
going
to
represent
any
header
that
doesn't
require
any
resource
from
jenkins
core
in
terms
of
css,
javascript,
icons,
images,
etc.
Okay,
it's
about
okay!
If
something
changes
on
jenkins
core,
my
header
is
not
going
to
break
because
I'm
not
referencing
any
style,
any
images,
any
icon,
etc.
B
Partial
header
is
the
opposite.
If
my
header
is
partial
header,
I
can
be
affected
by
changes
on
the
genqueus
code,
because
I'm
using
in
my
header,
content.jellyfile
references
to
css
icons
whatever
so
we
provide
for
partial
header
and
a
specific
field
called
compatibility.
Header
version,
which
needs
to
be
updated
every
time
the
jenkins
core
modifies
any
of
these
resources
that
can
be
can
make
me
to
be
incompatible.
B
B
B
Let
me
show
you
in
a
few
minutes
how
it
looks,
but,
as
I
told
you
before,
this
is
the
implementation
of
the
full.
Here,
it's
a
header
and
it's
always
going
to
be
compatible
because
it's
totally
unrelated
it's
separated
from
the
changes
that
can
happen
on
the
jenkins
core.
So
you
can
always
extend
for
this.
If
you
are
going
to
provide
your
own
resources,
your
own
images,
your
own
style,
etc.
B
For
setting
up
a
replacement
of
the
jenkins
code-
header,
okay,
partial
either,
no
sorry
heater
is
the
one
the
most
important
one,
which
is
the
extension
point
that
I
propose
in
this
pr,
which
is
mostly
checking
if
the
header
is
going
to
be
available
based
on,
is
going
to
be
compatible
and
is
enabled
okay.
So
my
get
method
is
mostly
evaluating
that
if
the
header
is
compatible
and
is
available,
let's
see
his
priority
number
based
on
the
ordinal
of
the
extension,
and
let's
use
this
in
case.
It's
the
maximum
one.
B
So,
as
I
told
you
before,
every
let's
say
the
agreement
is
that
if
you
are
going
to
modify
things
related
to
the
header,
you
should
update
this
number
to
make
the
other
possible
extension
points
provided
by
plugins
to
take
a
care
about
it,
because
you
can
break
the
things
that
are
in
in
that
plugins,
okay
and
yeah,
and
it
provides
also
a
method
called
incompatible
headers
to
create
a
administrative
monitor.
In
case
your
instance
detects
that
there
is
a
header
that
is
not
compatible.
B
B
A
B
The
from
my
side,
the
only
point
in
this
pr
that
requires-
maybe
some
attention
is
because
at
the
very
beginning
there
was
some
confusion
about.
Let
me
try
to
identify
where
it
is
okay
here
there
is
a
comment
from
olek
also
he
is
reviewing
again.
If
yesterday
I
guess
he
started
to
review
again
the
apr,
because
there
are
some
expectations
about
what
this
is
doing.
Okay,
as
I
told
you
at
the
very
beginning,
this
is
about
a
total
replacement
of
the
header.
B
B
C
C
I
don't
usually
like
it,
but
it
works,
and
as
long
as
and
cloudbees
will
support
lts
versions
and
they'll
test
it
before
they
update.
So
it's
not
realistically
going
to
affect
cloud
base,
it'd
be
a
little
bit
riskier
for
people
with
a
weekly
release.
If
someone
was
to
add
this
feature
with
a
weekly,
then
we'd
do
something
to
the
header
and
then
things
break,
but
I
don't
really
see
many
people
gonna
going
to
do
it.
E
C
C
B
E
E
B
A
So
it
sounds
like
my
interpretation
of
tim's
comments.
Was
he's
okay
with
it
going
forward
it
and
as
he
phrased
it,
it's
a
it's
a
big
on
off
switch,
not
an
incremental
small
thing,
but-
and
it's
probably
only
useful
to
to
large-scale
vendors
like
cloudbees
and
that's,
but
I
think
that's
that
was
meeting
your
need.
It
was
alfonso,
so
I
think
we're
ready
to
go
to
the
next.
Unless
somebody
has
other
comments.
A
A
A
A
D
Awesome
sweet:
can
you
guys
see
my
screen?
Yes
sweet,
so
I
just
thought:
I'd
give
a
quick
demo
of
of
kind
of
merged
in
ui
changes,
and
also
some
upcoming
ones,
slash
kind
of
experimental
ones,
and
so
I
just
minimized
that
so
recently,
we've
just
got
the
table
redesign
merged
in,
and
I've
also
had
a
pr
since
then
to
update
some
other
tables
such
as
the
nodes
table.
D
D
So
again,
I've
got
a
branch
open
now
called
update
forms
which
goes
through
one
of
the
components
and
updates
them
so
they're
all
consistent.
So
this
is
the
configure
screen
someone.
Unlike
the
current
release,
everything
is
now
styled
correctly,
with
the
exception
of
some
plugins,
so
say,
text
areas
have
the
correct,
styling
select
now
properly
styled
in
and
only
use.
The
kind
of
browser
theme
check
boxes
have
styling
now
as
well
as
well
as
the
little
kind
of
conditional
drop
downs.
D
D
So
if
we
just
scroll
to
the
bottom
of
the
page,
we'll
see
kind
of
this
plug-ins
using
the
built-in
input,
so
it
gets
styled
correctly.
It's
using
the
correct
check
boxes,
so
it
gets
styled
kind
of
out
of
the
box
for
free,
but
sadly,
here
that
this
little
select
isn't
being
styled,
so
it'll
be
a
fairly
small
pr
just
to
just
to
clean
that
up.
But
it
wouldn't
be
anything
major.
D
D
D
D
D
Yeah
see
the
new
plugin
manager,
it's
got
the
new
table
design.
It's
got
the
tab
bar
new
input,
it's
missing
the
check
boxes
and
right
now,
so
I
just
need
to
update
that.
So
it's
using
the
new
check
boxes,
it
does
feature
at
the
install
page,
some
toggle
switches
and
some
new
buttons
using
the
new
icons.
D
D
D
D
D
D
D
F
Now
sorry
yeah,
I
guess
I
just
had
a
question.
Well,
it
was,
I
thought
you
were
sort
of
finished.
It
was
mostly
a
comment,
a
bit
of
feedback
regarding
the
boldness
of
the
copy
on
the
tables.
It's
just
that
if
everything's
old
it
defeats
a
bit
of
the
purpose
of
it
being
well.
I
I
didn't
know
if
that
was
by
design
or
it
would
if
that
was
intentional,
because
but
you
just
said
it
that
it
wasn't
so,
and
another
thing
is
that,
can
you
can
you
go
back
to
a
table?
F
Please
sure?
So
I
I
did
see
a
comment
on
a
ticket
regarding
the
accessibility
of
the
tables,
because
there
were,
there
was
a
feedback
on.
I
don't
know
in
which
issue
regarding
the
table
headers
that
first,
the
the
text
is
spacey
in
the
letter
spacing
the
chance
was
a
bit
difficult
to
read
for
some
people
and
the
capitalization,
and
I
I
it
would
be
great
to
have
fully
here
here
because
full
on
capitalization.
We
have
we.
D
D
C
In
that,
I
think
it,
I
think
somehow,
the
if
you,
if
you
create
apple
with
a
capital,
a
banana
with
a
capital
b
and
then
apple
lowercase,
a
and
banana
lowercase
b,
or
not
quite
like
apple
one
banana
one.
Then
it
goes
like
apple
banana
apple
banana
rather
than
apple
apple
apple,
because
the
sorting
is
broken
and
then
the
cut
in
the
back
end
code.
F
D
D
E
Yeah,
so
this
is
actually
why
I
showed
up
today
and
I'm
all
for
the
the
making
life
simpler
and
a
cleaner
ui.
I
just
have
some
concerns
about
this
particular
implementation.
A
couple
things
have
have
been
mentioned,
but
the
first
one
I
I'd
say
is
in
in
reading
the
pr
I
actually
saw
that
there
were
really
three
different
changes.
E
E
So
I
I'm
not
sure
what
rules
there
are
around
or
guidance
around
pull
requests.
But
you
know
in
my
three
decades
of
configuration
management
experience.
I
would
have
recommended
that
those
be
three
separate
pull
requests,
because
if
you
want
to
take
one
and
not
the
other,
then
you
can
manage
that
far
easier
and
in
terms
of
those
three
specific
things
you
know
in
terms
of
the
icon
change
the
jenkins
65124,
which
is
the
nobody
likes,
the
samey
weather
icons.
E
I
check
the
numbers
and
it's
in
in
the
reported
issues.
It
was
the
number
one
issue
reported
in
the
the
lts
releases
so
far,
50
more
than
the
utf-8
change,
not
working
and
the
tables
to
divs
breaking
things.
So
it
seemed
to
have
drawn
a
lot
of
attention
and
that
hasn't
been
addressed
and
hasn't
been
linked
to
this
change
at
all.
E
You
know.
Personally,
I
find
it
strange
that
we
have
faster
and
faster
video
cards
and
gpus
and
yet
we're
presenting
more
monochromatic
monochromatic,
simple
uis,
but
you
know
that
that's
a
personal
taste
thing.
I
just
think
another
change
before
you
resolve
the
first
one
would
probably
throw
a
lot
of
people
off.
E
The
other
one
in
terms
of
the
spacing
I'm
not
sure
if
I
can
share
my
screen,
because
what
I
did
is
I
actually
pulled
up.
The
the
oldest
instance
that
we
have
running
is
actually
121
1
and
created
a
little
example
to
compare
what
you
see
today
to
to
what
it
used
to
be,
and
I
don't
know
if
I
can
share.
A
E
E
The
other
one
is
on
the
headers
here
you
can
see.
This
is
the
new
presentation
and
we
actually
have
you
know
we
use
folders
for
product
categories,
views
for
product
and
we
actually
have
a
split
naming
convention
where
the
the
application
names
are
part
of
the
job
in
uppercase
or
the
the
first
part
is
the
the
application
name,
there's
a
corresponding
folder
and
uppercase
and
the
type
of
job
that
we're
using.
E
If
it's
a
deploy
we
use,
it
has
deploy
in
the
title,
for
example,
and
it
would
be
a
lower
case.
You
know
it
would
be
one
of
these
bananas
or
lemons
for
deploy
or
security
analysis.
So
we
grouped
those
together.
We
took
advantage
of
the
bizarre
little
naming,
but
you
know
just
looking
at
this
field
of
words:
it's
really
hard
to
to
visualize,
where
the
buttons
are
in
comparison
to
to
where
the
tabs
were
so.
I
don't
know
if
anything
can
be
cleaned
up
for
that
and.
C
E
E
E
So
I
don't
know
if
there's
a
way
to
just
tag
all
the
sorting
presentation
issues
together
as
an
epic
and
and
have
a
a
global
approach,
possibly
even
with
a
user
preference
as
to
whether
you
care
about
case
sensitivity
or
not,
and
I
know
that
too
may
present
an
issue
in
windows
that
doesn't
seem
to
care
whether
it's
case
sensitive
or
not.
But
this
is
running
on
windows,
so
we
are
seeing
it.
F
Yeah
I
just
wanted
to
comment
about
the
typography.
I
don't
think
I
want
to
comment
about
is
that
we
changed
the
typography
either
on
the
lts
of
march
or
of
june
in
2020,
no
yeah
2020,
and
the
reason
was
that
one
of
the
things
we
changed
it
first.
It
was
because
it
was
really
really
really
inconsistent
it.
It
had
really.
It
went
as
low
as
nine
pixels.
In
some
cases
it
it
had
mixed
mixture
of
11
12.
F
So
what
we
did
was
basically
we
looked
at
basically
all
tools
that
we
have
the
github
gitlab
and
other.
Basically,
everything
that
deals
with
systems
management.
Everything
almost
all
software
in
the
industry
goes
with
a
14
pixel
font
based
font
size,
which
is
what
we
are
using
here,
and
basically,
we
sort
of
standardize,
fonts
in
sizes
of
12,
14
and
and
16..
F
F
I
don't
know,
but
definitely
not
lower
than
that,
which
is
what
you
may
be
showing
because
it,
the
typography,
should
really
have
lots
of
issues
with
consistency
and
at
least
now
it's
consistent
and
about
the
whites
and
the
vertical
spacing.
That's
also
something
that
came
up
a
lot
with
the
form
changes
when
they
will
see
this
dips
happened,
and
I
don't
know-
maybe
I
I
think
it's
also
a
matter
of
personally.
I
think
it's
a
matter
of
being
used
to
modern
compact
stuff
about.
F
E
I
do
recognize
it
is
a
sort
of
trend
in
the
industry
that
it
seems
that
you
know
land
might
be
the
most
expensive
thing
in
the
world,
but
apparently
screen
real
estate
is
free,
so
people
just
use
as
much
as
they
want,
but
you
know
on
a
smaller
screen.
You
do
end
up
doing
a
lot
of
scrolling.
You
know
we
have
some.
I
don't
know
about
you
guys,
but
we
have
some
things
that
have
200
jobs
on
a
particular
page
and
you
got
to
scroll
up
and
down
see.
E
F
Next
on
this
having
horizontal
form
groups
just
didn't
really
scale,
and
there
were
a
lot
of
issues
with
that,
namely
the
famous
git
configuration
a
git
pipeline
configuration
and
then,
if
you
all
remember
that
it
just
went
overflowing
the
container
in
your
screen.
So
that's
why
and
what
the
the
downside
vertical
spacing
the
forms
are
taller.
E
E
Stretched
out
looking
font,
so
it's
almost
like
a
a
monospace
font
on
everything,
and
it
just
seems
you
know.
The
the
one
thing
that
remains
kind
of
in
the
old
style
font
seems
to
be
the
the
content
of
the
table,
but
that's
the
most
important,
but
the
least
visually
striking
part
of
this
page.
You
know,
like
tim,
said,
I'm
just
drawn
to
that
banner
of
random
words
right,
but
I
I
agree
on
what
you're
saying
that
the
many
of
the
plug-ins,
especially
that
I've
looked
at,
are
like
wow.
E
You
know
people
have
kind
of
done
their
free
form,
interpretation
of
how
best
to
to
do
a
a
form
layout,
but
I
I
do
think
this
kind
of
size
font,
you
know
would
still
be
acceptable.
Maybe
it's
just
the
choice
of
font.
That's
been
used
here,
and
maybe
it
would
make
sense
once
everything
is
the
same
font.
I
think
it's
the
same.
F
E
Okay,
so
yeah
I
mean
that's.
That
was
the
the
concerns
I
had.
You
know
the.
The
first
is
the
three
issues,
because
if
you
decide
not
to
go
with
one
of
them
right
now,
you've
got
them
all
lumped,
so
I
don't
know,
and
unfortunately
it's
already
in
322,
so
I
don't
know
what
can
be
done
about
that.
If
you
know
you
kind
of
now
have
to
take
them
all
or
not
into
the
lts
right.
D
A
Three
months,
yeah
we've
got:
we've
got
three
months
for
evaluation
and
at
least
two
months
before
lts
selection.
So
this
is
exactly
the
right
time
for
this
to
have
arrived
so
that
we
can
discuss
it
hone
it
refine
it
in
future,
weeklies
so
yeah.
This
is.
This
is
a
perfect
place
to
give
feedback
and
to
work
on
it.
Yeah,
okay,.
E
E
As
a
governance
group
say,
this
is
the
changes
we
are
proposing.
I'm
just
not
sure
how
I'm
glad
the
jp
234
was
presented,
but
in
terms
of
the
other
one
you
know,
there's
I
didn't
see
a
jdp
on
it
on
the
the
table
layout
changes,
I
didn't
see
a
jira
issue
on
it.
It
just
sort
of
appeared
same
thing
with
the
style
icon.
A
A
E
E
C
E
C
D
C
D
D
So
previously
the
theme
plugin
presented
you
a
list
of
radio
buttons
each
listing
what
the
theme
was.
The
downside
is
this,
doesn't
give
you
a
proof
of
what
theme
actually
is,
so
you
might
come
across
the
solarized
theme
and
have
no
idea
say
what
solarize
looks
like
so.
The
advantage
of
this
is
you'd
have
a
small
preview
of
the
little
theme.
D
A
D
A
C
D
C
D
C
D
D
C
A
F
I
think
I
think
this
is
lovely
I
I
would
only
have
a
few
stylistic
changes
like,
but
I
think
those
can
be.
I
can
give
the
feedback
in
the
pr
sure
I
I
I
just
think.
For
example,
the
configuration
title
may
be
a
bit
superfluous.
I
don't
know,
but
definitely
I
would
only
try
to
make
sure
that
the
the
most
important
thing
in
my
opinion
is
that
it
has
the
same
width
as
a
sidebar.
So
that's
not
too
big
changing
layout,
widths
and
stuff
like
that.
F
F
E
Yeah
just
two
really
quick
thoughts.
I
think
one
was
mentioned
already,
which
is
set
a
really
realistic
expectation
of
how
wide
the
screen
should
be
at
a
maximum,
because
I
think
there
was
a
ticket
raised
the
other
day
about
somebody
complaining
that
we
didn't
take
advantage
of
all
the
whip
and
he
had
a
27-inch
wide
bonder,
but
that
would
completely
destroy
most
normal
people
who
are
working
on
a
smaller
screen.
E
E
E
D
C
It's
a
thing
for
people
who
are
managing
their
jobs
manually.
You
can
comment
on
what
changes
you're
doing
it.
It
records
whenever
anyone
saves
things,
and
it
just
creates
a
box
on
the
page.
That
says,
please
comment
your
changes
and
it
has
a
little
text
area
where
you
can
write
a
description
of
what
you
changed.
E
D
D
Sure
the
last
thing
is
kind
of
really
experimental.
It's
kind
of
a
new
search
review
for
jenkins,
so
one
of
the
kind
of
issues
I've
had
past
day
of
jenkins
is
kind
of
finding
builds
or
kind
of
jobs
and
stuff.
I
found
the
search
not
terribly
helpful
before
jenkins
and
was
never
particularly
clear
what
you
were
clicking
on.
So
I
wanted
to
kind
of
explore
ways
to
address
that.
So
I've
got
this
kind
of
new
search
reward.
F
I
I
will,
I
think
it
is
a
good
approach.
I
will
just
try
to
make
sure
that
I
don't
think
we
are
using
modality
like
this
anywhere
in
jenkins,
so
I
think
it's
a
bit
of
a
new
pattern
to
increase
just
for
search
does
feel
a
bit
of
aggressive.
I
do
think
like
better,
but
the
results
could
be
an
idea.
Maybe
there
are
many.
F
D
F
I
think
you
might
as
well
just
create
a
new
screen
to
be
honest
or
aim
or
something
that
same
model
that
just
I'm
sure,
you've
seen
this
sort
of
thing.
That's
a
model
that
takes
a
full
page
with
an
x
on
the
on
the
top.
Just,
but
it's
not
that
obvious
this.
As
you
said,
it's
a
two-spot
lighty
too
in
for
my
taste,
but
I
think
the
the
cons
has
potential
and
the
interaction
pattern,
which
is
the
most
important
thing,
really
does
have
potential.
A
Yeah
so
so,
for
me,
this
looks
marvelous
and
I
think,
even
even
if
that
modality
is
not
con
has
not
been
used
in
jenkins
before.
I
think
this
is
a
great
approach
because
for
me,
when
I'm
searching,
I'm
truly
no
longer
thinking
about
the
other
things
that
are
on
screen.
I
am
really
focused
on
so
for
me
that
the
modality
that
you've
implemented
it
fits
my
use
model
perfectly.
So
I
guess
I'm
I'm
inverse
of
felix's
observations.
D
C
D
C
C
I've
almost
got
the
form
element
path,
pr
merged,
which
means
we
can
change
it
inside
of
the
jenkins
itself,
without
relying
on
that
and
that
should
unlock
unblock,
hopefully
some
of
the
form
stuff,
but
I
know
the
buttons,
the
buttons
pr
really
broke,
ath
a
lot
just
selectors
and
markup
changes
where
I
haven't
really
checked
how
much
the
form
one
is
affected
or
not
those
damn
capitalization
changes
in
the
tables
broke
a
whole
bunch
of
tests.
I
have
to
fix
sorry.
D
A
C
Oh,
we
got
it
so
it's
been
reliably
green,
it
got
broken
and
a
couple
of
the
ones
recently
I
fixed
up
until
maybe
the
2.321.
I
think
I
think
it's
fixed.
I
think
it's
still
green,
like
full
melon
path.
Pr
ran
this
morning
against.
I
don't
think
it's
run
against
two
three.
I
don't
think
it's
running
against
the
last
weekly
from
yes.
Actually
I
think
it
has
so
I
think,
up
to
last
weekly,
everything's
green.
C
Stable
was
green,
although
stables
kind
of
broken,
because
I
didn't
add
full
compatibility
and
one
of
the
tests.
The
stables
got
like
one
or
two
tests
failing,
but
they
don't
matter
really.
I
upgraded
it
because
what
plug-in
made
a
change?
I
had
to
make
a
change
for
the
plug-in,
but
then
yeah,
but
it's
basically
quite
unstable.
C
You
know
it's
reliably,
green,
which
I
think
was
one
thing.
We
need
to
make
sure
really
sure
all
of
these
bi
tests
we
run
both
ath
and
bomb
against.
Otherwise,
it's
just
a
pain
of
having
to
fix
them.
Afterwards,
we've
had
to
fix
a
few
bomb
things,
but
basil
got
quite
mad.
I
think
we
got
quite
annoyed
when
a
whole
bunch
of
bomb
tests
started
breaking
for
some
of
these
things,
but
I
fixed
all
those
and
you
have
friend,
ath
and
bomb
get
some
of
the
new
ones.
A
C
C
Is
that
something
yeah
you
just
change
it
from
the
latest
weekly
version
to
to
your
incremental,
build
and
for
ath
there's
a
script
called
run.sh
and
it
fetches
latest
weekly
from
mirrors
to
jinx.io,
and
you
just
change
that
url
to
point
to
your
artifact,
so
just
change.
It
change
it
from
fetching
that
to
where
just
some
some
file
that
can
be
downloaded
and
a
pr
and
then
it
will
just
run
it.
It
took
me
a
little
bit
to
figure
out
the
best
way
of
doing
it
or
where
it
was
even
there.
C
But
you
can
see
some
of
my
recent
pr's
where
I've
ran
some
ath
things
from
pr's
the
benefit
of
running
in
the
ath
repo
is
it
does
the
split
thing
where
it
splits
the
test
into
like
10
different
groups
of
tests,
and
it
runs
them
all
in
parallel
on
different
machines.
If
you
change
core
to
run
all
the
tests,
then
it
takes
like
eight
hours
plus,
whereas
if
you
run
it
in
the
ath
reaper,
it
takes
40
minutes.
A
C
C
E
C
A
Excellent,
thank
you
any
we're
we're
about
15
minutes
over
anything
else
we
need
to
discuss
here.
Are
we
at
a
point
where
we
need
to
consider
switching
back
to
every
two
weeks
for
ux
sig
rather
than
every
four
weeks?
The
four
weeks
was
a
long
gap
since
our
last
meeting.
I
think
we
should
do
two
weeks
at
least
this
time,
given
it's
almost
christmas
for
the
next
one,
actually
right,
the
next
one
would
be
probably
right
in
the
christmas
holidays.
A
A
Okay,
all
right
so
next
next
session,
next
meeting
in
two
weeks
and
I'll
get
the
calendar
updated
to
schedule,
it
thanks
mark
any
other
topics,
all
right
ian.
Thank
you
for
being
here,
jan,
thank
you
for
being
here,
el
defonso
as
well
thanks
very
much
meeting
ends
recording
will
be
uploaded,
probably
within
24
hours.