►
From YouTube: Jenkins UX SIG Meeting November 11 2020
Description
An update was provided about the Tables to Divs transition. Most of the major plugins (1000+ installations) were now issue free. But work is still ongoing to make sure all sizable plugins work with new code base. An update provide on the JQuery Update to the latest version. Tim Jacomb provided an overview of the work that he had done on optimizing the performance of the load time of the Plugin Manager.
A
B
D
E
B
Anyway,
here
in
the
progressions
that
we
are
tracking
are
are
appearing,
we
are
putting
them
under
under
that
topic
and
sorry,
under
that
word
dashboard,
and
then
we
sometimes
we
can.
We
may
link
them
to
actual
non-issues.
For
example,
we
have
a
if
we
have
an
issue,
that's
related
to
another
ticket
that
we
have
on
the
main
epic.
We
just
link
it.
B
B
C
B
D
Most
of
it's
no
more
than
20
or
30
minutes
right.
So
there
was
only
three
major
plugins
that
were
broken
branch,
api,
cloud-based,
folder
and
http,
well,
http,
request
and
artifactory.
So
four
major
pl,
four
plugins
that
were
used
by
quite
a
lot
utter
artifactory
plugin
was
the
only
one
we're
aware
of
before
we
shut
up
and
the
rest
of
them
are
all
a
thousand
users
or
less
pretty
much
yeah.
D
F
D
F
C
D
So
the
plugins
need
to
be
fixed.
If
and
quite
a
few
plugins
have
been
fixed,
the
only
one,
the
only
one
with
pending
ones.
I
think
there's
two
with
pending
reviews
post
build
task
which
appears
to
be
up
for
adoption
in
like
2012
and
then
adopted
in
2017,
and
then
nothing
done
and
the
current
maintainer
is
not
replying
so
it's
about
on.
I
think
next
next
monday,
the
adoption
timeout
expires
so
and
then
rihanna's
seen
a
pr
for
conditional
build
step
yeah.
D
D
D
So
hopefully
that
will
help
and
then
it's
just
if
they
haven't
checked
the
list.
Checking
if
one
of
those
plugins
is
one
of
the
known
ones,
because
the
last
three
ones
have
all
been
artifactory
and
was
two
using
the
conditional
build
step
plugin.
I
think
no
sorry,
not
that
one,
the
post
build
task,
so
I
haven't
found
any
new
plugins
in
the
last
few
days
that
have
issues
right
and
yesterday
was
when
the
branch
api
and
cloud
base
folder
was
released
with
the
fixes
all
right.
B
D
B
B
B
We
are
also
monitoring
the
any
possible
stuff
in
jenkins
core
that.
I
also
think,
for
example,
like
myself
uncle,
maybe
a
lot
of
their
and
yeah,
and
we,
of
course,
even
if
some
planets
are
not
supported,
we
will
help
try
ash
and
you
know,
diagnose
and
point
users
to
the
documentation
and
stuff
which,
when
maintainers
starts
full
request
for
recipes
and
implementation.
So
the
whole
thing
yeah.
So
that's
what
we
are
going
to
do.
D
B
Okay,
I
think
I
would
like
to
give
a
brief
after
updating
the
equity
work
update.
Well,
as
we
mentioned
one
month
ago,
on
the
last
on
the
last
exit
meeting.
Microbes
are
working
on
updating,
jquery
versions,
all
jquery
versions
to
3.5
many
on
the
most
notable
plugins
and
the
reason
for
that
and
the
huge
security
vulnerabilities
I'm
basically
in
representing
the
inquiry
detached
in
as
many
places
as
I
can.
So
this
would
be
the
most.
B
This
was
the
most
difficult
one
in
pipeline
stage
view
I
just
wasn't
able
to
update
it
to
from
js
builder,
to
webpack,
and
I
needed
to
comment
out
one
unit
test.
I
will
try
to
to
make
it
work
without
unit
test,
but
it's
one
new
unit
test
after
out
of
39
that
doesn't
work
and
the
reason
that
it's
difficult
to
test
is
I
updated
jquery,
json
versions
and
it's
it's
just
impossible
to
appear
inside
and
to
see
what's
going
on
in
the
test.
E
B
D
B
B
D
Yep
yeah,
I'm
just
opening
it
up
yeah.
So
basically,
I
finally
got
sick
of
sitting
there
waiting
for
plugin
manager
to
load
while
I've
been
installing
plugins.
So
it
takes
between
like
three
and
five
seconds
for
me
locally
just
sitting
there
waiting,
which
isn't
very
nice,
so
I've
reworked
it
to
do
the
so.
D
The
major
problem
really
is
that
it
loads
all
of
the
plugins
into
the
browser
all
like
15
1600
and
it's
all
on
the
page,
just
hidden,
and
then
it
searches
from
client
side,
whereas
sort
of
changes
it
to
do
basically
is
load
is
not
is
to
only
load
like
20,
plugins
or
sorry.
The
top
20
lazy
loading.
Basically,
I
was
not
lazy
loading
as
such
loads
like
20,
and
then
you
just
have
to
search
in
the
box.
D
I
think
a
follow-on
improvement
would
be
pretty
well,
you
could
add
an
infinite
scroll
sort
of
thing,
whereas
you
scroll,
you
could
add
more
and
you
just
go
from
like
popular
ones
down,
but
you
could
do
it
as
a
follow-on.
I
can
quickly
just
show
it
just
to
show
it
working
and
so
other
people
can
see
it
sure
it'd
be
great.
D
D
This
is
my
custom
built
version
and
if
I
go
to
I've,
just
got
a
complete
load
time
of
556
milliseconds,
which
is
like
a
40
35
times
improvement
based
on
that
previous
one,
that
you
just
saw
it's
something
here,
so
you
see
here
that
there's
some
plugins
are
loaded,
so
I
think
these
are
some
of
the
most
popular
plugins,
a
lot
of
them.
A
lot
of
them
are
very
old
ones
that
just
to
be
installed
by
default
and
a
lot
of
things.
What's
about
map
db
api?
D
D
Another
improvement
that
I
did
was
I
kept
selected.
Plugins,
so
what
happened
in
the
previous
version
is
that
if
you
say
I
want
slack,
you
take
that
and
then
you
go.
I
want
pipeline
and
you've
locked,
you
don't
know,
what's
still
selected,
it's
actually
still
selected
and
when
you
click
install,
it
will
get
installed,
but
you've
got
no
context
of
what
you've
got.
There's
no
way
to
tell
what
you
have
currently
selected,
whereas
here
I've
changed
it.
When
you
update
your
search,
it
will
always
keep
the
selected
ones.
B
D
H
G
B
Yeah,
thank
you
tim
and
did
you
do
you
think
I'm
taking
the
chance
and
to
move
it
to
the
usb
drive
chain?
Sorry
yeah!
I
thought
about
it
because
my
reasoning
is
that
you
can.
If
you
keep
it
in
in
webpack,
then
you
can
split
common
for
the
javascript
utility
functions
for
they
also.
They
are
the
sorry
install
sorry
for
the
javascript.
B
D
D
B
D
B
D
D
D
Proper,
if
I
did
like
a
do
a
do
method
and
then
did
a
request,
dot
and
and
then
like
set
the
headers
and
everything
properly
through
the
state,
for
the
request
should
be
able
to
fix
do
that
properly,
but
then
we'd
have
to
change
it
to
instead
of
so.
Currently,
it's
using
jenkins
is
that
the
bind
functionality
we
go
like
var
view
equals,
bind
and
then
the
current
descriptor
or
object
back
or
the
backing
object.
D
D
B
D
D
B
C
I
think
I
mean
I
I'm
guessing
that
people
are
gonna
have
a
problem
with
this
implement.
Some
people
will
have
a
problem
that
you
know
I
can't
browse
through
plugins
properly
anymore.
That's
I
mean
it
seems
like
a
big
improvement,
but
we're
going
to
want
to
have
some
kind
of
either
lazy,
loathing
or
pagination
just.
D
G
So
one
one
problem
that
might
actually
be
real
and
new
when
it's
only
20
plugins.
What
happens
when
you
type
blue
ocean,
because
the
problem
is
the
blue.
The
actual
blue
ocean
plugin
is
the
least
popular
blue
ocean
titled
plugin,
because
every
other
blue
ocean
related
plugin
is
a
dependency
of
it.
So
you
may
be
able
to
install
blue
ocean
jira
without
having
blue
ocean
installed.
G
So
if
we
sort
since
resort
by
popularity,
it's
the
least
popular
one
actually
not
able
to
install
blue
ocean
right
now,
given
how
this
works.
Even
if
you,
even
if
you
remove
this,
perhaps
if
you
remove
the
space
motion
combined,
it
might
show,
but
it
may
not
nope,
and
the
same
will
happen
for
the
pipeline.
G
G
And
so
the
workaround
would
be
to
install
them
one
by
one
until
blotion
finally
shows
up
in
the
list,
because
all
of
the
others
are
moved
to
installed.
So
that's
still
a
bit
of
a
weakness.
Now,
obviously,
the
ordering
by
popularity
could
be
improved
a
bit
in
such
a
situation,
but
it's
simply
not
expected
to
have
a
dozen
or
two
dozen
plugins
when
one
would
suffice.
D
D
C
D
C
H
H
D
A
D
G
H
D
G
G
D
Yeah
yeah,
so
does
this
layout
update
callback.cool,
which
is
what's
responsible
for
yeah,
it's
responsible
for
moving
those
buttons
down
so
before
sometimes
well
without
that
hack,
it
was
always
here
on
initial
page
load
and
sometimes
in
the
old
solution.
It
ended
up
in
weird
places
if
the
page
loaded
quickly,
so
I've
changed
it
to
delay
a
little
bit
so
that
the
the
rows
get
added
and
it
seems.
B
B
Yeah
and
there
are
lots
of
aph
tests
that
are
flaky,
because
you
know
the
form,
for
example
this
I'm
degreasing,
but
yeah
just
two
seconds,
and
there
are
forms
that
you
load
a
forum.
For
example
the
ath
expects
to
click
something
and
because
the
buttons
haven't
moved
yet
with
javascript,
the
ath
fails.
So
it's
a
termination
so
that
I
I
agree
that
james
north
created
a
ticket
to.
I
think
it
was
in
order
to
convert
this
to
css
it's
on
my
radar
and
hopefully
I
will
be
able
to
tackle
it
somewhere.
B
D
D
Or
you
even
add,
like
a
field
where
the
user
can
limit,
how
choose
how
many
plugins
they
want
to
limit
it
by
and
you
go
like
20
100
all,
so
that
would
change
it
from
like
just
a
search
box
to
a
search
and
limit
or
something
you
know.
If
anyone
has
any
thoughts
on
that,
but
it
wouldn't.
It
certainly
wouldn't
be
hard
to
implement.
B
G
D
C
C
A
Okay,
my
update
is
a
bit
of
a
downer,
which
is
why
I
saved
it.
For
last,
this
will
be
my
last
ux
sega
session.
Unfortunately,
my
time
at
cloudbees
has
come
to
an
end,
I'm
taking
a
different
opportunity,
and
so
I
won't
I
won't
be
involved
beyond,
since
this
is
every
other
week
beyond
this
session,
it
really
has
been
a
pleasure
to
work
with
you
all.
A
I
know
a
few
of
you
already
knew
this
and
tim
and
uli,
of
course,
you're
not
at
cloud
b's,
but
I
so
appreciate
the
work
that
you've
done
over
the
past
year
honestly
and
your
openness
to
collaboration.
So
thank
you
very
much,
but
yeah
this.
This
will
be
my
last
six
session.
I
know
that
there
will
be
another
designer
taking
this
role.
I
don't
know
exactly
when,
but
we'll
keep
the
sig
updated
on
that
transition
and
yeah.
That's
it
any
questions.
I
guess.
C
A
I
I
think
this,
I
think,
pulling
off
something
like
a
sig,
and
I
know
that
it
hasn't
like
scaled
tremendously
and
it's
fluctuated
in
size
a
little
bit
as
a
group,
but
pulling
this
off.
I
still
think,
is
really
impressive.
It's
you
know
it's
a
testament
to
everyone
on
this
call
and
and
other
people's
devotion
to
jenkins
as
a
project,
and
I
admire
it
a
lot.
So
thank
you.
Everyone
appreciate
it
yeah.
Thank
you.