►
From YouTube: Jenkins UX SIG Meeting 17 March 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
to
the
jenkins
user
experience
special
interest
group,
it's
the
17th
of
march
2021..
Let's
talk
topics
so
damian
I
had
assumed
you
might
want
to
talk
further
about
multiple
pipelines
defined
for
multi-branch.
Are
there
other
topics
you
want
to
add
or
tim?
Are
there
any
and
tim?
I
was
going
to
ask
you
about
if
you
wanted
to
review
what
you
see
is
what's
next
for
ux
improvements
and
sort
of
ux
changes,
because
I
saw
that
you've
got
a
pull
request
in
now
for
to
make
some
further
tables
to
divs
changes.
B
Yeah,
I
can
briefly
talk
about
it.
It's
quite
a
minor
one.
B
A
B
Yeah,
so
so,
there's
basically
a
pr
open
to
make
some
changes
to
the
run
summary
page
and
the
job
or
project
page
to
convert
them
from
using
tables
for
layout
to
divs.
It's
very
conceptually
different
to
the
other
one
where
the
previous
one
previous
tables
to
devs
was
known
as
tables,
but
it
was
really
form
tables
to
this,
and
so
this
one
is
changing.
B
Basically,
two
more
pages
from
tables
to
divs
and
their
pages
that
are
often
contributed
to
from
plugins,
usually
using
the
very
the
exact
same
sort
of
widgets.
B
The
run
summary
page
has
normally
got
a
little
icon
on
the
left
and
then
maybe
a
little
bit
of
text
and
then
occasionally
a
list
or
a
little
bit
of
extra
information
underneath
it,
whereas
the
job
page
is
mostly
trend,
graphs
and
like
pipeline
stage,
grab
pipeline
stage
view
or
whatever
it's
called
guys
there
and
the
odd
other
information,
but
not
it's
not
too
busy.
In
general
again,
it
uses
some
similarish
to
the
run
page,
but
slightly
different.
B
So
there
was
an
it
was
a
so.
The
main
change
really
is
that
p
summary
tag,
which
is
the
which
is
the
hudson
folder.
It
removes
the
td
elements
and
moves
it
to
using
and
just
completely
removes
them.
The
issue
with
that
is
that
layout
was
being
done
by
different
tvs
and
they
were
keeping
them
on
the
same
line
for
some
reason.
Some
plug-ins,
I
think
it's
kind
of
what's
known
as
devices
where
people
just
like
divs
everywhere,
not
really
knowing
what
they're
doing.
B
But
what
that
seemed
happening
is
a
div
there's
a
block
element
in
in
layout
and
so
we've
removed
those
table,
wrappers
and
so
you've
got
an
image
which
so
p
summary
is
basically
a
icon
and
a
block
block
of
whatever
you
want,
and
it's
usually
icon
and
then
a
bit
of
text.
So
what
a
couple
of
plugins
did
was
they
did
icon
and
then
they
wrapped
their
text
in
a
div
and
it's
a
block
element.
B
So
I
moved
it
down
to
the
next
line,
so
in
the
few
plugins
that
that's
been
done
and
that's
been
removed
as
most
warnings
in
g
mostly
so,
basically,
the
plug-in
needs
to
be
using
an
inline
element
like
span
or
nothing
if
they
want
their
text
to
be
on
the
same
line.
A
B
B
B
A
B
You
have
minor
visual
issues
on
on
some
less
common
plugins.
A
B
Yeah,
and
so
this
actually,
this
does
fix
one
plug-in
that
was
broken
without
this
change,
so
they
had
used
a
table.
B
They'd
use
a
table
in
their
action
that
they
were
attaching
to
the
page
and
the
table
was
nested
under
a
table,
and
it
was
done
in
such
a
way
that
the
browser
decided
to
fix
the
layout
and
what
ended
up
happening
was
that
anything
after
that,
anything
after
that
action
was
shoved
out
to
the
other
side
of
the
page
and
the
layout
was
broken.
B
A
B
A
Hey,
that's:
that's
healthy
self-interest,
right,
guided
self-interest!
Look
this
this
this
bugs
me.
Therefore,
I'm
gonna
work
it!
Thank
you.
Okay!
Are
there
things
that
others
need
to
do
should?
Should?
Let's
see,
I
guess
let
me
look
up
that
pr,
because
we
may
want
to
encourage
others
to
to
go.
Look
at
the
yeah.
B
Set
up,
I
should
see.
A
A
A
B
And
you've
got
again
very
little
on
there,
but
you
can
check
it
anyway.
A
C
C
A
B
A
B
B
I
need
to
get
around
to
releasing
the
pipeline
graph
view
model.
I've.
I
just
did
do
some
more
work
on
it.
Did
I
release
it?
I
might
have
released.
A
A
B
I
mean
yeah,
I
would
say
yeah
alpha
beta
experimental.
B
So
that's
releasing
at
the
moment,
so
I
think
I
managed
to
reproduce
the
graph
in
a
lot
more
other
states
than
before.
Well,
I
haven't
found
any
difference.
Basically
now
and
what's
currently
there,
it's
very
hacky
very,
very
gross.
B
B
So
the
next
bits
are
really,
I
should
say
the
next
bit
is
I
credited
a
couple
of
issues
when
I
was
finishing
this
off,
you
need
to
implement
some
form
of
polling
or
pushing
up
updates,
probably
polling,
to
start
with
it's.
Currently,
you
have
to
refresh
the
page
to
get
updates
and
then
it's
things
like
log
viewer
and
better
and
the
job
view
and
figuring
out
whether
they
want
to
move
it
to
the
main
page
or
leave
it
on
its
own
page.
For
now,.
B
Mostly
different
contributors,
it
should
be
very
easy
well,
a
lot
of
it
should
be
straightforward
to
do
and
yeah
happy
to
and
if
especially
especially
fronting
anyone
interested
in
the
front-end
side
of
it,
they
should
be
yeah
quite
straightforward.
The
back-end
happy
to
help
with
I'm
not
happy
to
do
the
other
side.
It's
on
it
all
the
time.
A
A
You
mentioned
front
end
and
there
are
a
number
of
times
when
I
sort
of
have
to
flinch
away
from
getting
people
who
volunteer
for
front
end
on
jenkins,
because
many
things
are
terribly
complicated.
This
is
a
place
where
a
typical
front-end
developer
might
fit
well
and
say:
oh
yeah,
hey
here's!
Where
you
make
your
changes,
I
mean,
or
is
this
or
is
there
still?
This
is
going
to
have
a
very
steep
learning
curve
for
a
front-end
developer,
trying
to
help
it's
just
plain
react.
B
So
I
I
wouldn't
get
them
too
involved
and
as
long
as
long
as
they've
got
a
somewhat
reasonable
data
model
assuming
a
rest
api
data
model,
then
it's
fine.
B
I
wouldn't
get
a
front-end
developer
involved
in
the
in
the
back
end
of
it.
So
much
is
that
this
stuff's
quite
complex,
but
the
front
end
is
just
fairly
modern
react
fairly
the
well
then
they
can
write
the
new
stuff
in
modern,
it's
on
a
slightly
old
version
and
it's
using
components
using
class
components
rather
than
function,
components
which
could
be
rewritten.
But
it's
that,
but
it's
just
extracted
from
blue
motion.
B
A
C
So
the
the
next
step
that
I
did
not
work
on
since
our
past
meeting
is
to
bring
that
topic
to
the
pipeline.
You
sig!
U,
in
order
to
see
what
have
if
there
have
been
any
faults,
any
tries
any
prototypes
about
this,
I'm
sure
there
we
can
we're
going
to
discover
discussion
about
the
pro
and
cons
of
this
solution.
C
So
the
goal
is
to
start
by
learning,
watching
and
listening
and
why?
Why
is
it
not
a
thing?
There
might
be
a
lot
of
reasons
and
also
bring
the
the
ideas
and
the
use
case
to
see
if
it
differs
from
what
we
had
in
the
past.
C
C
It's
it's
not
an
option.
I'm!
I
won't
write
scripted
pipeline
if
I
don't
have
to
because,
depending
on
the
people,
you
have
in
front
of
you,
some
people
are
more
at
ease
with
script
tips.
Let's
say
more
scripted
view.
Some
are
at
ease
with
the
dsl,
but
in
the
end
most
of
the
other
ci
tools
are
not
even
thinking
about
whatever
complexity.
C
They
delegate
that
to
real
tools
that
can
be
tested,
and
here
my
goal
is
to
say
there
are
a
lot
of
use
cases
that
I
see
today.
So
I
want
to
ask
the
other
or
will
you
use
solve
that
problem?
And
if
the
answer
is
you
scripted
pipeline
or
then
yeah,
but
I
think
we
can
have
a
middle
ground
there,
because
they
they
might
have
some
mechanism
that
could
be
used.
The
goal
is
not
to
have
a
fancy
ideas.
It's
more.
How
could
we
change
the
existing
to
fit
the
model
of?
C
A
C
C
If
you
manage
and
use
jenkins,
that's:
okay,
that's
not
an
issue,
because
in
both
cases
it
will
be
code
in
a
repo.
However,
most
of
the
time,
the
people
using
jenkins
are
not
the
people
administrating
jenkins
and
the
time
between.
Okay,
I
want
to
add
these
new
pipelines
on
my
repo.
I
push
the
branch
and
then
the
time
where
this
pipeline
are
there
and
you
are
currently
working
on
that
the
feedback
loop
today,
it's
not
acceptable
to
speak
more
than
five
minutes
between
both
right
yeah.
C
C
Why
is
that?
Why
is
I
don't
have
a
web
so
here
here's
the
point
I
want
to
to
to
push
to
the
pipeline.
I
don't
know
when
will
when
is
the
next
plan
sag
pipeline
plans,
I'm
not
sure.
A
A
This
idea,
that's
rolling
around
in
the
ux
cig,
any
any
guidance
on
it
and
it
may
be
worth
a
conversation
with
stephen
turana
of
the
of
the
sig
just
a
one-on-one
conversation
he's
based
in
us
east
coast
and
has
done
a
bunch
of
a
lot
of
shepherding
of
pipeline
templating
concepts.
And
how
do
you
get
there.
A
C
I
have
the
event
calendar.
The
next
one
will
be
next
friday.
It
will
be
at
5
00
p.m
for
my
time,
so
that
should
be
that
will
be
known
for
the
east
coast.
It's
a
bit
early
in
the
morning
for
the
west
coast.