►
Description
Recording of the regular UX SIG meeting. Simon Symhoven has also presented the first version of the Pull Request Monitoring Plugin plugin and its user experience. The plugin offers a possibility to display and aggregate certain delta metrics for pull request in a user configurable dashboard. It relies on other plugins to provide such a portlet contains the plugin specific delta metrics for a pull request. More info: https://github.com/jenkinsci/pull-request-monitoring-plugin
A
Welcome
to
the
jenkins
user
experience
special
interest
group,
it's
the
28th
of
april,
looking
forward
to
a
good
a
good
session.
Today.
Let's
talk
over,
let's
review
our
agenda
and
then
we'll
work
through
it.
So
simone
simhoven
has
a
presentation
for
us
on
a
project
that
he's
been
working
on.
I
believe
it's
specifically
related
to
github
pull
request
status,
reporting
inside
the
jenkins
ui,
then
uli
status
of
bootstrap
5
migration
for
plugins.
A
I've
got
a
pending
action
item
on
an
online
meetup
for
the
dev
environment,
setup
experience
with
uli
julie,
I'm
behind.
On
that
sorry,
I
haven't
sent
the
invitation,
yet
I
haven't
even
sent
the
proposal
yet
I'll
get
to
that.
Pending
ux
changes
we
had
the
pipeline
visualization
demo.
There
were
some
other
changes
that
I
think
tim
you
may
want
to
to
highlight
for
us
and
then
damien.
We
had
a
topic
on
multiple
pipelines
for
a
branch,
multi-branch
job,
any
other
topics.
We
should
include
on
our
agenda
today.
A
B
A
B
B
C
B
A
A
B
I
I
built
the
demo
with
two
charts
of
mr
hoffman's
plugins
and
one
with
static,
html
content.
If
you
want
to
provide
a
view,
I
did
it
here
in
my
project.
I
had
let's
begin
with
the
second
one.
You
have
to
implement
the
interface
monitor
view
and
define
a
title
and
id.
Usually
the
id
of
the
view
is
the
class
name
and
each
view
has
to
have
a
corresponding,
monitor
generally
view,
where
defines
the
the
plug-in
contents
to
show
on
the
dashboard
and
the
factory
will
create
the
views.
D
D
So
if
you
have
a
plugin
that
wants
to
work
on
a
pull
request,
you
can
show
information.
For
instance,
in
my
warnings
plugin,
I
can
show
the
number
of
new
warnings
in
this
pull
request
or
in
the
git
plugin.
We
can
show
the
number
of
new
commits
from
this
pull
request,
so
it's
basically
up
to
the
other
plugin.
What
to
show.
A
D
D
A
Here,
and
so
so
in
the
in
terms
of
the
warnings
plug-in
you're
envisioning,
things
like,
I
could
see
incremental
code
coverage
report
in
there
or
I
could
see
an
incremental
check,
style
warnings
or
an
incremental
report
of
oh
this.
These
are
the
things
that
were:
let's
see,
what
are
some
of
the
others,
the
javadoc
warnings
or
the
java
compiler
warnings
that
these
are
all
incremental
as
a
result
of
that
pull
request.
A
E
Yeah
one,
so
that's
really
good
you're,
very,
like
the
full,
the
full
loop
that
you
can
generate
the
code
and
use
it
back.
I
understand
that
the
configuration
is
based
on
the
pipeline
content
there.
There
is
no
right
now
user-defined
configuration,
for
instance.
If
I
want
a
dashboard
inverted
compared
to
my
colleague,
but
on
the
same
request,
is
it
possible
or
is
it
a
plan
or
is
it
out
of
the
scope.
B
At
the
moment,
the
configuration
is
saved
per
per
project,
but
you
can
rearrange
the
dashboard
locally,
but
with
the
next
run
the
configuration
is
loaded
back
again
from
the
jenkins
file.
So
each
project
basically
has
one
configuration
at
the
moment
but
yeah.
Yes,
we
can
think
about
it
and
implement
it.
D
C
E
I'm
not
sure,
though,
oh
that
will
under
I'm
thinking
a
lot,
but
if
there
is
a
big
change
on
what
information
is
showing
the
view
from
the
pipeline.
If
you
have
your
own
and
there
is
a
conflict
during
the
merge
configuration,
it
can
be
not
an
easy
problem
to
solve,
to
define
which
one
is
the
most
prior
and
because
you
can
define
priority.
But
if
someone
decided
to
remove
all
the
to
remove
like
the
third
one,
and
you
still
have
it
on
your
local
user
profile,
that
might
be
a
complicated
topic.
C
B
C
C
B
A
C
C
A
B
A
B
C
D
A
B
D
Questions
from
from
others-
maybe
an
additional
comment.
I
think
this
dashboard
view
if
it
is
working
out
very
good.
We
can
use
it
on
the
build
view
or
on
the
top
view
as
well,
where
we
can
rearrange
our
charts
and
everything
else,
which
is
currently
a
little
bit
strange
only
on
the
right
side.
So
maybe
it
would
be
helpful
to
integrate
it
in
in
other
views
as
well.
C
C
Nice,
let's
go
ahead.
A
general
comment
around
there
with
thoughts
kind
of
related
to
the
mess
of
the
job
page,
but
it'd
be
great
to
look
at
redesigning
at
some
point
with
a
simple
view
where
plugins
can't
just
go
crazy
and
we
just
if
we
have
like
defined
contribution
areas
for
things
like
minimal
scm
information.
Things
like
commits,
maybe
pr
title
code
coverage
area
test,
result
area
and
like
pipe,
maybe
some
pipeline
information
or
something
but
just
having
very
specific
minimal
information.
C
Because
now,
if
you
run
like
get
plug-in
and
you've
got
a
library
and
maybe
another
library,
you
end
up
seeing
the
get
information
multiple
times,
it's
not
terribly
relevant
change,
log
information,
again,
not
terribly
relevant,
most
times
type,
timer
sort
of
thing.
The
page
is
pretty
ugly,
really
the
talking
about
the
run
page
right
now,
but
yeah,
just
a
general
redesign
of
the
run
page
and
the
job
page
configurable,
it's
good
for
some,
but
in
general,
just
assign
page
would
be
nice
and
plug-ins
contributing
elsewhere.
C
A
B
B
A
D
A
A
A
A
A
D
Actually,
this
is
just
a
small
thing,
currently
my
plugins
and
some
others
as
well
use
bootstrap
4
in
jenkins,
and
what
I'm
currently,
what
I'm
doing
is
to
upgrade
it
to
bootstrap
5,
which
is
to
be
released
in
the
next
weeks.
Let's
say
currently,
we
are
in
beta
3
of
bootstrap
and
I
migrated
all
my
plugins
now
and
everything
works
quite
fine.
So
I
think
when
the
bootstrap
5
will
be
available
for
in
the
version
5,
I
can
switch
all
my
plugins
as
well.
A
D
E
D
A
A
D
C
A
A
A
So,
pending
user
experience
changes
a
reminder
that
the
pipeline
visualization
plug-in
is
has
been
released
in
a
preliminary
version.
I've
got
it
installed.
I'm
I
continue
to
be
impressed
even
as
a
as
a
prototype.
It
renders,
and
I
haven't,
found
a
pipeline
that
it
doesn't
render
yet
so
well
done
tim.
Thank
you
anything
that
you
wanted
to
say
on
that
further
tim
or
any
other
insights.
C
C
A
E
It's
driving
that
much
time,
so
the
next
step
will
be
sending
a
mail
to
the
developer
mailing
list
on
the
line
to
ask
the
question
of
what
are
what
will
be
the
where
they're
already
attempt
to
have
to
manage
multiple
pipelines?
What
were
the
thoughts?
What
could
have
been
written?
That
means
also
for
myself
having
to
search
a
bit
of
jira
at
least
asking
the
questions
then
we'll
see
if
someone
is
ready
or
not
without
any
answer,
I
think
I
will
go
if
I
don't
have
any
answer
or
any
feedback
for
the
next
two
weeks.
E
E
The
idea
is
not
to
produce
a
poc
but
to
write
down
the
ideas,
I'm
not
sure
if
a
gep
is
the
correct
tool
for
this,
but
that
is
writing
something
like
a
state
written
statement
of
what
is
the
scope?
What
are
the
goal?
What
are
the
must?
Have
the
nice
to
have
the
idea
and
the
goal
just
to
be
sure
that
we
can
share
that
and
say:
okay,
we're
going
to
build
something
based
on
that.
A
A
F
F
E
E
Okay,
I
might
not
have
all
the
contacts,
but
did
you
did
you
try
to
open
the
jira
issue
because
it
sounds
like
a
bug
and
the
idea
is
to
provide
as
much
information
as
possible
to
allow
someone
else
on
another
machine.
Another
jenkins
instance
to
reproduce
the
issue.
So
we
will
need
you
to
open
an
issue
telling
us
which
version
of
jenkins
you
are
using
the
plugin
versions
that
you
are
using
that
could
be
related
to
that.
E
Widget
is
the
generic
reporting
information
and
personally,
I
don't
know
exactly
what
feature
it
is,
but
the
goal
is
to
explain.
Oh,
we
can
reproduce
the
same
issue
which
web
browser
you
are
using,
just
to
be
sure
it
might
be
web
browser
specific
also.
So
the
goal
is
to
allow
us
to
have
info
that
kind
of
information,
and
then
someone
will
search
confirm
based
on
that
info
and
we
can
seek
for
a
fix
or
if
you
already
have
an
idea,
you
can
totally
start
to
contribute
on
that
fixed
issue.
A
Yeah
so
diraj,
I
see,
I
see
your
comment
on
the
channel.
My
apologies
that
I
don't
think
we've
had.
Oh,
oh,
I
see
oh
and
tim
had
asked.
Okay,
build
status
should
be
above
and
yeah,
so
I
think
what
he's
saying
is
that
there
is
a
yeah.
There
are
layout
fixes
needed,
so
go
ahead
and
propose
a
a
bug
report
and
that
I
think,
may
be
something
you
can
even
propose.
Then
propo
the
fix
for
it
as
well.