►
From YouTube: Jenkins UX SIG Meeting 19 Jan 2022
Description
Jenkins user experience special interest group 19 January 2022.
00:00 Introduction
07:00 New dropdown menus
08:00 New tooltips with subtle animations
08:17 New job configuration layout using sidepanel navigation by sections (better use horizontal screen space)
11:28 Updated icons on "Manage Jenkins" that adopt the user theme
12:05 Manage plugins with progress indicators inside the page
14:00 Consolidate update and install plugins to single page
15:15 Badges on available plugins more attractively placed
21:18 Review of pull requests in progress
A
A
tim,
I
think
you're,
the
probably
the
topic
to
be
that
voice
lts
status
briefly
for
me
weekly
status,
and
then
we
had
a
topic
for
ui
plug-in
for
prism
for
source
code,
highlighting
if
ooly
joins
us
and
ui
improvements,
so
tim
and
tim
and
jan,
I
think
there
we've
got
the
the
this
will
be.
The
bulk
of
the
meeting,
any
other
topics
you'd
like
to
put
on
the
agenda.
A
A
I
like
tim's
proposal,
tim's
proposal
was
hey:
let's
do
it
after
the
lts
baseline
is
selected,
and
that
way
it
will
naturally
arrive
in
the
june
june
lts
release
and
we
may
need
to
make
other
changes
like
make
edge
tier
one.
Instead
of
the
current.
I
don't
remember
where
it
is
even
on
the
tiering
list.
A
A
But
I
want
to
spend
my
time
on
the
java
8
jep
first
before
worrying
about
this
one
tim.
Do
you
mind
if
I
do
a
jenkins
enhancement
proposal
for
this
one,
just
to
be
sure,
we've
got
the
right
plan
in
place
or
is
it?
Is
that
too
much
for
this
one?
I
think
it's
too
much
for
us.
I
think
it's
just
we
just
just.
A
B
A
B
A
A
A
I
mean
the
weekly
gets
as
long
as
it
wants.
Doesn't
it
I
I
think
it.
Oh
I
you're
right.
I
think
it
does
and
now
then,
but
then
there
is
a
failure
in
the
tests
good
point,
but
there's
a
failure
in
the
test
that
I
can't
duplicate
locally,
and
so
my
assumption
was
the
reason
I
can't
duplicate
it
locally
may
be
tied
to
timing
or.
B
A
A
So
I'm
considering,
if
I
need
to
go
talk
to
kosuke
and
see
if
he
uni
he
can
appeal
through
a
side
channel
into
the
into
the
jfrog
management.
We
doesn't
feel
like
we're
getting
the
response
that
we'd
hoped
for.
No,
they
shouldn't
just
be
ignoring
us
right,
okay,
so
I'll
I'll
continue
that
angle,
anything
else
on
2.331.
A
B
A
C
A
C
C
So
this
is
basically
a
kind
of
consolidation
of
various
branches
and
kind
of
works
in
progress,
all
kind
of
shoved
into
one
branch,
without
kind
of
testing
or
whatever,
just
just
for
demo
purposes,
so
that
this
branch
includes
the
new
kind
of
drop-down
menus.
So
the
breadcrumbs
are
kind
of
consolidated.
Now,
there's
only
one
chevron
versus
two
and
we
have
the
new
kind
of
tooltips
and
menus
that
replace
the
yuhu
ui
stuff,
which
is
still
a
work
in
progress.
C
C
C
If
I
just
push
that
down
there,
if
I
open
up
a
job
and
then
hit
configure,
there's
an
updated
kind
of
configuration
screen
which
follows
on
from
the
forms.
Prs
also
follows
on
from
the
work
that
I
showed
on
the
november
meeting,
so
idea
being
to
take
better
use
of
screen
space
not
to
just
modernize
the
appearance,
so
it
kind
of
looks
like
so
then.
Some
of
the
work
I've
done
as
well
is
just
to
update
the
kind
of
draggable
components.
C
A
C
C
A
C
A
C
A
C
So
that's
the
configuration
page
and
if
I
go
to
the
new
plugins
page,
one
of
the
changes
before
I
get
there
is
I've
updated
the
icons
for
the
manage
jenkins
page,
there's,
currently
a
branch
for
that
kind
of
preliminary
work
for
this.
So
it's
just
using
the
new
kind
of
ion
icons
for
the
plugins
and
all
the
other
kind
of
sections
here.
So
they
kind
of
look
like
series.
They
look
a
bit
more
modern
and
they
also
adopt
kind
of
the
user's
theme.
C
B
C
B
A
C
A
A
C
Suppose
you
can,
you
can
also
select
them
and
you'll
get
an
install
selected
button,
but
just
for
demonstration
I'll
just
show
you
the
button.
So
the
difference
now
is
everything
happens
in
line.
So
previously
we
would
switch
another
page
and
you'd
see
the
status,
whereas
now,
if
I'm
still
the
mailer
plugin,
hopefully
it'll
start
installing
without
losing
context
of
what's
happening.
So
it
should
install
and
you'll
get
a
little
green
tick.
When
it's
done.
C
Yeah
I'll
install
all
the
kind
of
dependencies
as
well,
so
that's
kind
of
one
thing.
That's
kind
of
missing
from
this
approach.
Is
you
don't
see
whatever
plugins
are
installing
at
the
same
time,
but
if
I
hit
the
new
kind
of
updates
install
plugins
page,
these
are
previously
two
tabs,
but
now
I've
been
consolidated,
it
looks
like
so
and
you'll
see
the
mailer
plugins
have
been
installed.
A
C
C
Box
in
the
lower
left
corner-
okay-
just
it's
just
not
enabled
in
this
field
right
now,
but
yeah,
it's
a
little
orange
pop-up.
It's
really
really
in
your
face,
so
it
looks
like
that.
It's
a
little
bit
simpler
and
if
you
go
to
advanced
settings
again,
it's
how
it
looks
before
I've
just
added
the
kind
of
a
quick
link
to
the
installations
and
operator
page.
What
does
that.
A
C
A
A
B
C
A
So
could
you
go
back
to
the
go
back
to
the
plug-in
manager
just
to
let
some
more
questions
so?
Okay?
So
in
this
this
view
is
refined
with
things
now
being
inside
right
inside
the
page,
no
separate,
no
separate
page
during
the
download
process
and
install
process.
It's
all
done
live
right
inside
the
page.
Yes,.
A
B
A
A
B
A
Excellent
yan
this
is
this
is
brilliant
work.
Thank
you
so
much
for
what
you're
doing.
Thank
you.
Thank
you.
Now
tim,
you
had
a
question
about
in
terms
of
getting
it
in.
Are
there
any
things
there
that
that
guidance
or
things
where
you're
looking
for
additional
help,
or
I
should
be
lobbying
for
other
people
to
give
help
to
to
evaluate
things,
etc?.
B
B
A
Either
right
right-
and
I
agree
with
that-
I
think
331's
content
makes
a
good
choice
for
lts
baseline
this
we,
I
would
dream
of
it
being
in
the
next
lts
in
june
this.
This
looks
like
a
great
next
round,
so
so
in
terms
of
the
kinds
of
things
that
we
should
be
testing
for
or
checking
for
our
or
maybe
yang,
could
you
open
up
the
list
of
pr's,
one
of
the
so
from
let's
see,
github
github
yeah.
A
A
B
A
B
B
Yeah,
let
me
know
if
you
need
a
hand
on
them,
don't
understand
it,
take
a
little
bit
to
get
used
to
them,
but
they're
generally
just
selenium
tests
with
some
some
weird
compatibility
layers
and
stuff,
but
the
main
thing
on
them
is
to
try
and
keep
them
compatible.
The
change
is
compatible
with
because
people
use
it
for
so
when
it
needs
to
be
needs
to
pass
on
both
your
pr
and
against
master,
and
it's
like,
ideally
keeping
the
tests
compatible
with
lts
as
well,
but
kind
of
not
the
biggest
deal.
A
A
B
Understand,
no
so
in
the
acceptance
test,
harness
reaper
or
it
always
runs
the
full
set.
Oh
okay,
so
yeah
on
core.
It
only
runs
like
two
or
three
tests,
and
it's
really
quick,
but
but
on
the
ath
repo,
it
runs
all
of
them,
but
it
also
runs
them
with
like
10
10
sets
in
parallel.
So
it's
not
too
long.
It's
quicker
than
bomb.
It's
something
like
40
50
minutes,
I
think
to
run
a
full
set
of
them.
So
it's
not
too
bad.
B
Yeah
yeah
yeah,
the
problem
is
incremental.
Bills
tend
to
be
a
bit
too
slow
because
core
build
times
are
insane
these
days,
especially
since
windows
was
re-enabled
which
doubled
the
core
pr
time.
So
you
generally
just
do
it
if
sit,
go
and
go
into
the
award
direct.
If
you've
just
pushed
a
change
well
locally,
you
just
build
it
locally
and
you
can
just
run
with
the
local
checkout.
B
B
A
A
C
Yeah
I
just
felt
like
we
wanted
to
use
color
for
the
for
the
icons
already
from
have
a
dev
standpoint.
It's
really
easy
to
add
color
to
the
icons.
We
can
also
use
the
color
variables
from
css.
So,
depending
on
your
theme,
it
can
change
color,
which
is
nice,
but
from
the
kind
of
design
standpoint.
I've
not
really
got
too
much
of
a
view
really.
I
think
it
will
depend
on
the
context
really
yeah.
C
B
I
don't
think
the
same
concern
is
valid
on
this
page.
The
concern
was
for
icons
that
are
used
for
people
to
get
an
understanding
of
a
status.
So
it's
like
you've
got
a
success
icon
and
you
remove
the
color
from
it
or
even
failed,
or
something
like
a
failed
with
a
red
means,
a
lot
more
than
a
failed,
that's
grey
and
so
weather
was
used
to
have
like
grey
clouds
and
like
snow
and
or
sunny,
and
when
the
colour
went
from
those
people
who
are
using
it
in
that
way.
A
B
C
B
A
B
C
B
C
C
C
B
B
Maybe
just
remove
the
discussion
from
the
title
now,
if
you've
got
it
working
and
really
just
need
to
check
that
ath
passes
and
quite
like
and
bomb
quite
likely
won't,
I
would
say:
there'll
be
places
that
are
clicking
sp,
clicking
images
or
something
and
selenium
isn't
high
level
enough
that
you
can
just
say
click
and
it
will
work.
You
need
to
handle
buttons
and
inputs
and
all
these
things
slightly
differently.
B
C
B
C
B
B
So
yeah,
I
guess
so
those
two
powers
look
really
easy.
It's
a
modernized
form
just
really
need
daniel
to
finish
his
review
that
he
is
said.
He'll
do
but
it'll
likely
be
not
so
we
probably
won't
merge,
even
if
we
did
get
that
if
we
wouldn't
merge
it
this
week,
just
do
a
last
build
for
lts
and
then
yeah
that
ionicons
one
looks
quite
straightforward.
B
B
So
basically
so
these
pr's
they
load
the
they
they
load
the
strings
so
that
you
can
have
an
inline
svg
previous,
and
so
they
load
them
using
the
java
resource
class
resource
loading
using
the
class
loader
previously
in
the
svg
icon.
That
felix
did
he
was
using
like
sprite
sheets
and
he
was
getting
the
browser
to
load
them
to
load
the
resources
with
a
url
and
then
so
that
worked
because
of
the
stapler
was
loading
at
the
resource
that
way
just
like
how
it
load
any
other
resource.
B
But
yeah,
that's
nothing!
That's
not
the
most
recommended
way
of
working
with
svgs.
Normally
you
have
them
in
line
as
far
as
I
know,
but
yeah,
so
each
gun's
kind
of
done
the
recommended
way,
but
then,
but
because
we're
loading
it
through
java
resource
loading.
There's
a
class
loader
involved
now,
so
we
either
need
to
get
plugins
to
pass
the
class
loader
or
use
some
sort
of
uber
class
loader
or
something
I
think
but
yeah.
I
need.
A
A
B
I
mean
it's
fine
to
do
it.
There
I'd
probably
join
something
like
the
credentials
plug-in
because
it's
on
the
managed
wall
or
configurations
code
plug-in
because
they're
on
the
manage
page
and
they'll
be
quite
obvious.
If
they
don't
fit
in
makes
sense.
Credentials
is
probably
a
pretty
obvious
one
to
do
it
on,
because
it'll
be
installed
everywhere
and
it'll
look
slightly
out
of
place,
probably
good.
A
A
B
C
C
B
We
can
still
fix
the
plug-ins
up
to
be
ford
compatible
if
we
can,
but
some
of
them
will
need
bigger
changes
but,
and
we
can
set,
we
can
see.
If
we
can.
You
can
even
do
things
like
set
a
variable
in
the
jelly
context,
which
means
that
this
feature
is
is
now
a
thing
and
then
you
can
check
for
that
variable
in
the
plugins
and
then
render
it
differently.
A
Yeah
sounds
good.
Now
tim
has,
I
know,
you've
submitted
several
fixes
to
the
plugins.
I
maintained
that
that
make
them
more
modern.
Are
there
things
we
should
do
in
terms
of
detecting
plug-ins
that
have
those
those
bad
behaviors
or
was
it?
Is
it
inevitably
a
single
thing
where
oh
every
programmer
made
their
own
set
of
mistakes.
B
So
we
added
console
warning
to
the
to
the
browser
console,
for
I
think
the
one
you're
talking
about
which
was
the
repeatable
delete
where
they've
copied
it
into
the
plugin
or
they've
just
used
the
plain
html
rather
than
the
markup,
rather
than
the
jelly
control.
So
there's
a
browser
console
warning
for
that,
telling
you
to
switch
to
the
proper
one,
and
so
you
get
plug-in
before
that.
So
we
we
did
a
fixing
call
which
which
looks
for
it
and
fixes
it.
B
B
And
then
it
warns
in
the
browser
for
that
and
gives
you
the
element
that
it
was
and
you
can
click
on
that
to
find
where
it
was,
and
you
can
use
that
to
find
out
which
plugin
it
is,
and
so
you
get
plug-in
was
the
test
one.
For
that
there
was
nothing
else
on
the
page
from
the
default
install
to
get
plug-in.
Is
the
only
one
in
default,
but
there
are
there's
a
I
searched.
I
searched
github
before
I
did
that,
just
to
check
and
there's
a
lot
of
them.
B
A
Want
well
so
one
of
the
one
of
the
things
that
and
that's
that's,
probably
a
good
one
for
me
to
highlight
to
people
is
open.
The
browser
console,
while
you're,
using
while
you're
in
development
mode
to
see
if
you
get
any
warnings
or
alerts
during
during
your
development
testing
right,
so
that
browser
console
now
has
information
in
it.
That
may
not
have
been
there
before
yep.