►
From YouTube: Jenkins UX SIG Meeting - 2 September 2020
Description
A short Jenkins UX SIG meeting took place. A new member Cliff Meyers joined and there was some discussion about how to move the Pipeline Visualization out of Blue Ocean into the classic Jenkins UI.
B
I
was
just
gonna
introduce
myself
to
the
group.
I
think
some
of
you
may
have
seen
some
messages
from
me
on
gitter
and
some
interest
that
I
have
and
trying
to
contribute.
Essentially
the
pipeline
graph
view
from
blue
ocean
back
into
classic
in
a
way
that
we
can
leverage
that
visualization
there.
So
if
can
definitely
talk
about
at
the
end,
I'm
sorry
new
first
time
joining
the
sig
so
a
little
getting
used
to
the
to
the
process.
Here.
A
Yeah
absolutely
welcome
very
much
cliff
and
thanks
yeah
more
than
happy
to
chat
about
that
today
or
at
any
point
in
the
future,
but
but
yeah
absolutely
welcome.
We
have
a
small
group
today,
but
we're
trying
to
grow
this
sig
and
and
we're
excited
to
have
you
thanks
felix
for
adding
that
cool.
Well
with
that
introduction,
let's
hop
into
our
first.
Our
first
item
here.
B
A
A
A
So
what
this
is?
Essentially
you
get
it
jenkins
user
experience
sig
overview.
These
are
all
things
that
that
most
of
us
know,
but
cliff.
This
would
be
really
valuable
for
you
to
poke
around
as
well
more
about
the
sig,
but
we
are
what
we
do.
This
sort
of
information
kind
of
lives
at
the
beginning
of
our
design,
decks
that
we
usually
review,
but
that
can
be
a
bit
inaccessible
for
people
too.
A
There
are
a
number
of
different
resources
here.
Dedicated
getter
space
is
just
our
channel
and
it's
just
pointing
people
in
that
direction.
Essentially,
but
the
real
meat
and
potatoes
here
is
the
ui
design
guidelines
where
I've
created
these
pages
and
kind
of
gave
an
overview
of
the
idea
of
these
guidelines
and
created
these
pages
of
pages
of
jenkins
design
principles,
the
typography
and
fonts
the
color
palettes.
A
A
This
is
just
a
resource
consolidation,
but
actually,
I
should
point
out
one
additional
item
here
is
that
each
of
these
pages
would
have
at
the
bottom,
this
very
simple
type
form
where
people
can
go
and
submit
feedback
and
the
idea
being
that
the
the
sig
group
can
ideally
grow
a
little
bit
and
also
benefit
from
more
asynchronous
feedback
and
communication.
This
way,
perhaps
I
can
gear
this
up
so
that
when
someone
submits
it,
it
gets
posted
to
get
her
channel
or
something
like
that
shouldn't
be
too
hard.
A
D
My
first
thinking
is
that
it
should
land
in,
especially
as
we
are
mostly
brigading,
the
wiki,
the
wiki
on
jenkins
io.
You
know
prairie
landing
and
under
the
jenkins
ioc
ux
website.
As
I
as
I
posted,
the
link
off
in
the
chat,
pretty
would
make
sense
yeah.
I
don't
think
I'm
not
sure
what
the
others
do
in
general.
You
know
with
regard
to
how
to
put
their
resources,
I
mean
it
would
probably
make
sense
to
you
know
as
you've
done
here.
D
I
think
actually
we'll
eat
already
overlaps
with
some
of
the
things,
because
I'm
pretty
sure
we
already
have
the
meeting
calendar
some
of
the
links
to
various
mailing
lists.
So
yeah
we
would
probably
just
add
you
know
the
I
don't
know
the
design
check
archive
and
then
you
know
basically
the
thing
that
we've
not
put
there
yet
sorry,
I'm
fighting
with
my
baby.
A
C
A
D
D
It's
quite
easy
to
contribute
because
it's
actually
backed
by
it's
a
statically
generated
website
and
I
think
it's
all
struct,
I'm
not
sure
which
tool
it's
using,
but
basically
I've
just
put
it
the
link
of
it's
back
backed
by
and
you
can
submit
the
pr.
So
we
can
help
if
you
you're
not
gonna,
go
with
that.
But
then
the
rest
is
mostly.
D
You
know
potentially
reworking
things
in
ascii
docs,
but
I
don't
think
it
would
be
a
problem
for
you
and
you
know
basically,
posting
links
and
whatever
I
I
just
saw
a
few
seconds
ago
and
there's
obviously
by
definition
a
lot
of
examples
in
that
thing
and
you
can
run
it
locally
before
you're
filing
your
pr
so
yeah.
I
think
it
should
be
easy
or
it
is
doable
for
a
lot
of
contributors
out
there
so
yeah.
Maybe
you
can
open
the
links
for
that.
D
I
posted
on
the
chat,
especially
for
people
who
may
be
watching
the
recording
afterwards
and
may
not
have
access
to
the
the
comments
so
that
you
know
it's
helping
for
potential
contributors,
sure
basically
yeah.
This
is
where
somebody
could
so
someone
could
file
a
pr
and
once
the
vr
is
just
merged,
it's
immediately
going
to
be
published
well
immediately
after
a
few
seconds
or
minutes
after
it's
basically
rebuilt
but
pushed
against
the
public-facing
io
website.
D
A
Structure
so
yeah,
if
we
can,
it
sounds
like
we
can
get
it
over
there
on
to
jenkins.io
in
a
way
that's
useful
and
super
visible
in
the
current
destination.
I'm
totally
fine
with
that.
So
baptist
I'll
follow
up
with
you
about
where
to
get
started
with
that
sure
pleasure,
okay,
so
then
yeah
in
coming
weeks.
I
can't
promise
a
specific
time,
but
in
coming
weeks,
we'll
we'll
look
to
consolidate
all
of
this
stuff
and
have
it
a
little
bit
neater
and
have
these
resources
a
lot
more
visible.
Hopefully,.
D
Yeah,
I'm
literally
ecstatic
about
what
cliff
and
felix
and
and
many
others
could
be
delivering
together,
because
I
think
what
cliff
you
were
saying
something
like
if
I'm
wrong
but-
and
I
think
felix
did
it-
gave
it
a
try.
Quick
quick,
try
is
to
you
know,
find
some
way
to
extract
basically
the
kind
of
pipeline
pipeline,
rendering
capabilities
of
fluorescent
inside
so-called
classic
ui.
C
Yeah,
I
I
did
try
to
just
taking
blue
ocean
code
and
put
it
into
yeah,
I'm
creating
a
plugin
or
just
you
know,
creating
a
react,
app
embedded
into
the
classic
ui
and
using
pollution
code
and
thing
is
the
blue
ocean
ui
code.
It's
really
tightly
coupled
to
the
javascript
code,
to
the
business
logic
which
just
ties
the
couple
to
some
rest
api
and
the
authentication
is
weird
I
could
I
couldn't.
I
wasn't
able
to
get
anything
to
work
after
release,
so
I
sort
of
gave
up
on
that
one.
C
So
my
suggestion
would
be
to
if
anyone
wants
to
work
on
this
to
just
use
relocation,
api
and
maybe
build
the
whole
thing
from
the
from
the
ground,
because
understanding
the
way
blue
ocean
works,
the
they
have
the
api,
the
stream
model
and
everything
it's
a
challenge.
I
would
just
go
with
the
api
and
start
building
something.
D
Yeah,
maybe
just
that's
something
cliff-
can
talk
to
talk
about,
but
yeah
I'm
like
it
looks
to
me
as
a
newbie.
You
know
outsider
that
the
you
know
the
rendering
of
pipelines
is
not
is
more
than
just
api
call
it's
a
lot
of
work.
So
if
you're
saying
we
rewrite
everything
about
that,
I'm
like
probably
going
to
take
a
lot
of
work
and
a
lot
of
rework
and
basically
rewriting
from
scratch.
So
maybe
I'm
missing
something
or.
C
You
can
sort
of
with,
with
with
some
especially
react
knowledge
you
can
sort
of
copy
and
paste.
You
can
just
go
into
this
component
boom
copy
and
paste
the
sbg
code,
which
is
basically
what
you're
referring
to
the
svg
code.
You
can
just
copy
and
paste
that
one
and
migrate
it
into
any
other
javascript
framework,
because
that's
the
basic
it's
the
difficult
part
is
the
other
one.
Basically,
and
it's
the
one
that's
really
difficult
to
extract
from
blue
ocean.
C
B
Yeah
I'll
kind
of
reintroduce
myself
a
little
bit
in
a
little
bit
more
detail,
so
I'm
actually
a
former
bee
myself.
I
worked
for
cloud
b's
kind
of
during
like
2016
2017
time
frame.
I
guess
you
could
say
I
was
maybe
one
of
the
principal
contributors
to
the
blue
ocean
ui.
I
did
a
little
bit
on
the
back
end
with
building
out
like
some
of
the
github
integration
rest
apis
over
there.
B
D
B
Go
to
a
jenkins
instance
that
I
have
somewhere
and
grab
essentially
just
the
rest
api
response.
Payload
that
I
know
is
responsible
for
kind
of
rendering
that
graph
and
just
start
there
and
just
see,
if
I
can
slam
literally
like
some
some
object,
literal
json
into
the
react
component
and
just
get
it,
get
it
to
render,
and
then
at
least
we
kind
of
got
to
that
point.
C
C
B
How
many
other
pieces
want
to
come
along
for
the
ride,
because
obviously,
there's
like
a
ton
of
as
to
your
point
like
vivek-
did
a
ton
of
work
building
like
essentially
a
whole
new
rest
api
framework
almost
from
from
the
ground
up,
so
it
may
may
have
a
lot
of
dependencies
that
we
need
to
try
to
untangle
as
we
get
to
that
part.
So.
B
B
B
You
know
firewall
setup
in
our
organization,
so
we've
had
to
kind
of
shift
all
of
our
users
back
into
the
the
conventional
ui
and
and
of
course
the
the
pipeline
graph
is
like
the
one
thing
that
they're
that
they're
missing
so
excited
to
do
some
open
source
contribution
again.
Definitely,
but
this
will
also
kind
of
help
us
out
big
time
at
the
day
job
as
it
were
so.