►
From YouTube: Meet Blue Ocean 1.0, a new user experience for Jenkins
Description
James Dumay will present Blue Ocean; a new user experience for Jenkins based on a personalizable, modern design that allows users to graphically create, visualize and diagnose CD Pipelines. Blue Ocean is more than putting a modern face to Jenkins, it’s a complete revitalization of the way developers use Jenkins that helps them adopt Continuous Delivery. James will take the group through all the new capabilities, tips and tricks that will make Blue Ocean work powerfully for your team.
A
B
B
Well
time
flies
and
before
that
I
working
at
another
logic
company
where
I
worked
on
a
kind
of
similar
development
tool,
but
really
it's
my
mission
in
life
to
build
really
great
developer
tools
for
the
so
that
I
guess
you
know
developers
can
you
know,
stop
worrying
about
the
tool
so
much
and
get
back
to
doing
what
they
do
best,
which
is
writing
code.
So
for
me,
any
tool
that
kind
of
gets
out
of
a
developer's
way
and
gets
them
productive
really
quickly
is
the
best
kind
of
development
tool.
B
So
I
mentioned
blue
ocean,
so
you
haven't
haven't
heard
about
blue
ocean,
yet
it's
not
just
a
new
user
experience
for
Jenkins.
It's
a
whole
new
way
to
use
Jenkins.
So
what
we
mean
by
that
is
that
you
know
we
could
have
gone
ahead
and
just
updated
the
styling
of
of
Jenkins
as
knowing
and
love.
Today,
however,
you
know
given
the
opportunity
we
thought
well,
you
know
Jenkins
was
built
over
ten
years
ago.
In
software
you
know
the
practice
of
software
engineering
has
changed
dramatically
since
the
inception
of
Jenkins
and
so
have
the
practices.
B
What
that
meant
was
that
our
mission
here
was
to
you
know,
solve
the
practice
of
software.
Engineering
is
constantly
changing.
So,
if
you
think
back
to
even
five
years
ago,
you
know
containers
and
docker
and
those
sorts
of
things
really
weren't.
Even
on
the
scene,
I
mean
we
were
dealing
with.
No
people
running
the
vm's
inside
a
virtual
box
or
vmware,
and
that
technology
didn't
exist
in
the
capabilities
that
you
know
that
we
all
that
we
all
get
out
of
it
today.
B
You
know
it
just
wasn't
possible
and
even
sort
of
you
know
a
little
bit
further
away
than
that
is,
you
know,
distributed
version
control
systems.
You
know
one
a
thing
when
Jenkins
was
created,
so
things
have
moved
on
significantly
and
I.
Think
what's
really
important
here
to
recognize
is
that
they're
really
truly
relevant
tools,
the
ones
that
developers
will
always
keep
it
in
their
toolbox
of
the
device?
Are
the
tools
that
integrate
with
all
of
the
new
the
new
things
and
take?
B
You
know
you
know,
exercise
the
benefits
of
of
those
new
tools
in
a
way
that
you
know
sorry
I'm,
gonna
start
again.
So
sorry,
so
I
guess
like
the
best
tools
and
the
ones
that
developers
keep
in
their
toolbox,
other
ones
that
are
the
most
relevant,
and
what
that
means
is
that
the
kinds
of
tools
that
people
use
tend
to
be
and
love
tend
to
be
the
tools
that
integrate
with
all
of
their
other
stuff
so
and
and
kind
of
fits
monthly
into
whatever
they're
doing
so.
B
B
You
know
blue
oceans
going
to
be
there
making
sure
that
you're
productive
with
those
those
tools
or
if
a
new
practice
comes
along.
You
know
we
had
continuous
integration
now
we're
working.
You
know.
A
lot
of
people
are
talking
about
continuous
delivery.
If
that
new
practice
does
come
along
blue
oceans
going
to
go
there
as
well,
so
really
what
this
means
is
that
Jenkins
is
going
to
be
constantly
reinvented
and
made
relevant
for
whatever
sick,
whatever
wherever
our
industry
is.
Go
and
when
we
were
thinking
about
blue
ocean,
it
was
really
around
this.
B
You
know
practice
of
continuous
delivery
that
we
thought
was
very
important.
To
kind
of
you
know,
to
kind
of
take
a
nod
to
and
to
deal
with
in.
You
know
in
a
very
native
way,
so
before
blue
ocean
really,
the
practice
of
continuous
delivery
was
for
the
experts
and
I
think
you
know
we're
taking
the
opinion
that
it
really
shouldn't
be
for
the
experts,
and
so
what
I
mean
by
that
is.
If
you
want
to
create
your
pipeline
for
you,
you
know
you
continuous
delivery
pipeline
before
blue
ocean.
You
have
to
learn
a
scripting
language.
B
You
had
to
be
a
Jenkins
expert
or
you
had
to
you
know
you
had
to
have
built
worked
with
people
who
had
built
continuous
delivery
pipelines
before
you
can
create
your
own
right
and
it
wasn't
very
clear
where
to
start
the
tooling
was
very,
you
know
as
I'm
the
documented
the
sometimes
there's
there's
so
much
choice
in
the
tooling
as
well.
It
can
be
very
hard
to
figure
out.
B
Well,
you
know
what
what
tool
do
I
even
pick
is
Jenkins
the
right
tool
if
I
integrate,
if
I
do
I
buy
commercial
tool
to
do
continuous
delivery.
You
know
all
of
these
sorts
of
questions,
really
we
kind
of
left
continuous
delivery
as
this
thing
that
people
wanted,
but
really
it
was,
you
know
squarely
in
the
in
the
field
of
the
experts,
the
realm
of
the
experts
and
so
we're
really
trying
to
with
blue
ocean
which
really
trying
to
make
it
so
easy
and
so
approachable
to
to
start
working
with
continuous
delivery.
B
That
there's
no
reason
you
shouldn't
be
doing
that
so
I
want
to
talk
to
you
today
about
the
blue
ocean,
1.0
release
and
sort
of
what
we're
what
we've
been
working
on
there,
but
before
I
dive
into
blue
ocean
itself,
I
really
want
to
show
you
a
little
bit
more
about
just
sort
of
how
our
launch
went
in
the
answer.
What
people
are
saying
about
about
the
release
we
when
we,
when
we
launched
like
he
was
two
weeks
ago,
the
blueish
from
1.0.
We
just
had
like
an
amazing
amazing
sort
of
you
know
grassroots
surprise.
B
I!
Guess
you
know
like
comments
like
you
know
like
a
Phoenix,
Jenkins
CI
as
rising
again,
this
fellow
was
able
to
configure
his
pipeline
in
less
than
a
minute
and
that
he
had
never
had
you
know.
No,
you
see,
I
was
never
easy.
Was
never
this
easy.
Before
we
got
onto
the
we
had
great
discussion
on
hacking
news
we
had.
You
know
tens
of
thousands
of
vehicle
yeah
tens
of
thousands
of
views
on
on
YouTube.
B
For
our
you
know,
video
introducing
bluish
and
great
publications
like
info
girl,
world
writing
about
you
know
how
who
blue
ocean
is.
You
know
putting
it
friendly,
more
friendly
face
on
on
continuous
will
agree
with
Jenkins
or
even
continuous
delivery
in
general.
So
it's
just
really
amazing
that
you
know
all
over
the
world.
There
are
all
of
these
people
out
there
who
are
building
their
businesses
and
livelihoods
on
top
of
Jenkins,
and
so
it's
a
real
testament
to
the
the
Jenkins
community.
B
Just
how
you
know
how
much,
how
big
that
community
is
and
and
how
much
they
really
love
Jenkins
and
they
see
it.
As
you
know,
one
of
these
one
of
these
tools
that
they
keep
in
their
toolbox,
so
it's
fantastic
and
over
the
course
of
the
beta
we
launched
the
beta
in
September
2016
at
Jenkins
world
and
since
the
beader
in
Jenkins
fall
I
think
we're
now
up
to
7400
installations
of
blue
ocean.
So
that
is
not
counting
the
installations
since
we've
launched
blue
ocean
wall
point.
B
So
this
is
amazing
so
that
that
effectively
means
that,
if
you
know
each,
let's
just
say
hypothetically
that
you
know
each
installation,
each
Jenkins
installation
is
roughly
you
know
one
team
of
developers
who
are
using
Jenkins.
That
means
that
there's
7400
teams
using
blue
ocean
to
that
that
is
phenomenal,
and
so
we
get
the
statistics
numbers
so
we've
at
the
end
of
the
month.
So
we're
just
going
to
be
waiting
for
a
couple
of
days
now,
another
10
days,
at
least
after
those
new
numbers
that
come
through
from
the
blower's
and
1.0
launch
time.
B
B
B
First
up
really
will
ask
me:
where
do
I
store
my
cabin,
so
I
can
store
it
in
gear
or
in
github
I'm
gonna
pick
github,
so
github
we've
made
this
very,
very
easy
for
github
and
we're
gonna
do
a
similar
thing
for
gear,
so
I'll
click
on
github,
our
widget
organization.
Does
my
repository
belong
to
old,
pic
386?
That's
like
my
github
account
and
then
I'll
go
ahead
and
click
new
pipeline,
so
we
wanna
create
a
pipeline
from
a
repository
and
then
we're
good
demo
and
here's
my
online
gem
demo
repository.
B
So
I'll
click
create
pipeline
and
what
Jenkins
will
do
now
is
have
a
quick
scan
for
a
Jenkins
file
if
you're
not
familiar
with
a
Jenkins
file,
it's
the
it's
a
file
like
in
a
config
file
that
you
drop
into
your
github
repository
that
defines
how
your
pipeline
is
executed
and
the
common
practice
here
is
to
version
that
Jenkins
file.
Alongside
your
application,
connect
don't
get
to
that
in
a
moment,
so
I'll
click
create
five
point
and
we
get
pushed
out
to
our
new
visual
pipeline
editor.
B
B
A
B
B
B
B
B
B
Well,
at
this
more
test
stage,
and
maybe
what
I'll
do
in
this
incense
is
that
I
want
to
test.
These
are
making
a
modification
to
my
nail.
Production
pipeline.
I'll
probably
want
to
make
that
modification
on
a
branch
in
a
sure
that,
like
it
actually
works
before
using
it
on
my
stop,
so
I
can
say,
add
or
tests
stage.
B
B
We
defined
three
stages,
build
test,
deploy.
We
had
different
steps
in
between
them,
so
these
could
be
anything
so
but
typically
like.
If
you
were
invoking
Michael
all
maven
come
you
could
do
that
with
a
shell
skip
us
she'll,
step
script
and
you
can
have
as
many
steps
within
a
state
as
you
like,
commonly.
A
B
So
yeah
within
the
within
each
stage,
you're
gonna
have
as
many
steps
as
you
like.
You
can
run.
You
know
build
tools
like
make
and
they,
then
you
can
call
out
to
different
web
services
if
you
want
Jenkins
plugins
expose
a
whole
bunch
of
different
steps.
So
if
you
install
a
new
plugin,
it
supports
pipeline
and
then
what
you
can
do
is
go,
and
you
know
use
the
editor
as
such
for
that
step
and
define
the
step
and
the
editor
or
you
can
add
the
step
right
here
in
the
Jenkins
file.
B
So
really
one
of
the
super
powerful
things
about
blue
ocean
is
that
if
you,
if
you
do
feel
comfortable,
if,
if,
if
you
don't
feel
comfortable
editing
a
configuration
file
to
define
your
pipeline,
you
can
always
go
and
use
the
editor
and
our
people
on
the
same
team
who
feel
more
comfortable
I'm
editing
in
their
favorite
text.
Editor
like
VI
or
Adam,
or
even
IntelliJ,
IDEA
or
Eclipse.
B
I
can
go
ahead
and
edit
this
file
directly
and
then
it's
possible
to
go
and
see
those
changes
then
reflected
in
the
UI
in
Jenkins,
both
in
the
visualization
and
in
the
editor
itself.
So
you
really
don't
have
to
look
with
blue
ocean
and
declarative.
You
really
don't
have
to
choose
between
well
just
something
like
if
I
edit
the
text
file
that
the
Jenkins
file
I
use.
My
text
editor
and
I
change.
B
A
bunch
of
things
that's
going
to
mean
that
you
know
users
other
other
developers
who
like
to
use
the
editor
now
can't
now
can't.
Actually,
you
know
use
that
editor
anymore.
That's
not
the
case!
So
with
blue
ocean
you
can
choose
both.
Then
you
can
switch
between
the
two
modes
of
working.
Well,
if
you
like,
oh.
A
B
Yes,
oh
and
so
on
our
roadmap,
so
we're
since
we've
just
watched
bluish
on
one
or
we're
doing
a
bit
of
a
bug
fix
in
technical,
dead
sprint
at
the
moment,
so
roughly
about
four
weeks.
I
think
we
have
left
on
it,
and
that
means
that
we're
not
building
any
new
features,
we're
just
kind
of
fixing
bugs
and
and
cleaning
things
up
so
that
we
can
develop.
B
So
if
I
come
in
here,
the
first
time
and
I
picked
github.
It
will
actually
ask
me
like
what
my
access
key
for
github
is
now.
It's
probably
a
good
thing
that
I'm
not
including
that
on
a
jam
recording
for
all
eternity,
so
I
went
and
prefilled
that,
but
when
that
option
does
display
in
this
sort
of
step
in
it's
kind
of
no
wizard
flower,
it
will
ask
you
for
the
you
know
where
your
github
Enterprise
is
actually
located,
so
I.
Believe
it's
technically,
not
a
lot
of
work
for
us
to
do
it.
B
Alrighty,
so
what
I'll
go
and
do
is
I
really
want
to
kind
of
show
you
some
of
the
the
some
of
the
visualizations
that
are
possible
in
the
ocean,
so
what
I've
done?
I've
created
this
new
pipeline
here
called
app
store
demo,
and
so,
if
I
load
this
one
up
in
my
my
visual
pipeline
editor
key,
you
can
see
that
you
know
I've
got
a
build
step
here
that
goes
out
and
calls
maven
and
produces
a
source.
Some
sausage
are
along
the
way.
I
did
some
testing,
and
actually
this
is
kind
of
just
mocked
out.
B
I'm
the
testing
bit
it's
one
of
them
for
demonstration
purposes.
We
want
this
to
be
really
quick,
most
pipelines
run
for
it.
You
know
20
or
30
minutes.
You
know
that's
sort
of
the
the
length
of
this
this
this
gem,
so
I
wanted
to
make
it
nice
and
quick,
so
yeah,
you
can
see
the
app
store
demo.
So
one
of
the
great
things
here
is
about
them.
The
the
pipeline
editor
is
that
it
is
what
you
see
is
what
you
get.
B
B
There
we
go
so
here
it
is
going
off
and
building
my
my
source
jar.
Now
as
as
this
build
as
this
actually
builds
in
the
pipe,
the
pipeline
executes
we're
actually
following
along
that
process
of
execution,
so
it
makes
it
possible
for
me
to
go
back
in
you
know:
I
can
go
click
on
build
and
browse
things.
I
can
click
back
on
static
analysis
and
see
what
it
what's
going
on
there.
So
it's
actually
really
quite
a
browsable
right.
B
B
Here's
one
called
my
deploy
where
I've
removed
the
deployment
phase,
but
you
can
kind
of
see
that
you
know
as
I
click
around
I
can
see
the
previous
all
the
steps
that
I
defined
in
the
editor,
a
Brook
like
the
logs
for
those
steps,
are
like
broken
up
by
step
by
step.
So
it's
really
easy
to
see.
You
know
what
each
step
in
the
pipeline
did
or
what
each
stage
in
the
pipeline
did
now.
However,
say
if
I
have
a
failure,
so
what
I'll
do
I'll
go
ahead
and
I'll
go
and
make
something
fail?
B
Its
let's
just
do
something
like
put
a
little
bit
of
garbage
in
the
shell
step
here,
and
so
what
we
should
see
when
I,
when
I
go
and
run
this
pipeline,
is
that
the
Firefox
parallel
within
the
browsers
test
stage
will
fail.
And
then
hopefully
it's
going
to
show
me
exactly
where
the
failure
is
when
I
click
through.
So,
let's
put
it
create
a
new
branch
with
my
taking
file
changes.
B
A
So
James,
while
you're
waiting
for
that
maybe
hit
refresh
there,
was
a
question
on
the
IRC
about
the
steps
being
shown,
the
the
high
level.
You
know,
labels
for
those
are
the
summaries
and
always
asking
whether
or
not
there's
a
way
to
alias
those
so
that
they're
more
meaningful
to
to
your
pipeline
right.
B
Okay,
yeah,
that's
a
great
question
and
something
that
does
come
up
quite
frequently
so
yeah
we
do.
We
do
realize
that
the
descriptions
of
these
steps
here
are
not
particularly
useful,
so
it
can
be
kind
of
difficult
to
match
the
description
of
this
shell
script.
Up
with
you
know
its
equivalent
the
notional
script
step
here
in
the
editor.
B
So
you
know,
there's
been
another
of
different
suggestions
given
to
us
about,
like
you
know
how
people
kind
of
want
to
name
these
and
I
think
one
of
the
best
ways
that
we
can
make
this
work
is
just
to
make
it
work
transparently.
So
we
actually
have
some
work
in
progress
today
that
will
actually
inspect
the
that
the
running
shell
script
or
the
the
finished.
Well.
Sorry
inspect
every
step
and
figure
out
what
that
step
is
going
to
do
so.
B
So
we
won't
be
doing
any
aliasing
because
it
requires
some
additional
language
features
in
declarative
and
in
scripted
pipeline.
In
order
for
us
did
this
to
provide
that
custom
alias,
but
we
will
be
making
it
very,
very
easy
for
people
to
see
what
those
steps
are
based
on
the
content
of
the
step.
That
makes
sense
so.
A
B
That's
correct,
yeah,
cool
thanks.
Oh
this
is
just
taking
a
little
while
my
apologies,
maybe
I
what
we
can
do.
We
can
just
come
back
to
this
in
a
second
we'll,
let
we'll
let
this
guy
run
and
we'll
come
back.
So
one
of
the
things
that
we
we
also
decided
on
is
you
know
a
part
of
making
Jenkins
Jenkins
more
relevant
by
integrating
with
the
tools
that
you
use.
You
know
integration
like
everybody
uses,
git
and
github,
so
we'll
be
doing
this
for
other
found
get
providers.
B
B
So,
for
example,
if
you
know
fails
all
the
time
fails
all
the
time
and
then
the
health
of
this
pipeline
could
be
stormy.
So
if
it
fails,
some
of
the
time
could
be
cloudy
if
it
fails.
So
if
none
at
the
time,
then
it's
it'll
be
sunny
just
like
the
history
of
optimality
here,
so
you
know
you
want
to
see
a
lot
more
sunny
pipelines
than
you
do
stormy
ones.
B
Now,
if
I
click
over
to
pull
requests.
If
someone
sent
me
a
pull
request
for
the
App
Store
demo,
repository
Jenkins
is
automatically
gonna
go
and
pick
that
PR
up
and
execute
the
pipeline
for
it.
So
you
can
see
here
we
have
this.
One
called
bug:
slash
big
HTTP
processor,
if
I
click
in
there
I
can
see
that
you
know
this
is
the
our
number
8
on
github.
B
So
it's
really
important
if
you're
the
reviewer
of
pull
requests
to
have
this
to
have
this
checking
write
this
reporting
write
in
github
right
because
it
will
allow
you
to
go
well.
You
know
it
looks
like
this
change.
You
know
we
had
some
some
issues
here
so
for
this
particular
branch,
where
you
know
we
update
a
license
file,
and
maybe
there
was
you
know,
maybe
a
lion
length.
It
was
too
long
in
the
license
file
or
something
like
that
so
like
as
a
reviewer
I
know
that
that
can
be.
It
wasn't
really
good
to
go.
B
But
then
you
know,
as
I
you
know
pulled
in
some
new
changes.
I
have
faded
some
some
some
Java
tests
and
I
merged
in
the
contents
of
master
into
this
branch.
To
get
some
updates
that
the
changes
for
this
pull
request
are
actually
now
passing.
So
that's
really
highly
valuable
all
right.
So
what
what
I'm
going
to
do
is
I'm
going
to
go
back
to
our
final
project
and
just
kind
of
show
you
you
know
how
a
blue
ocean
will
just
quickly
hone
in
on
where
that
failure
actually
occurred.
B
B
We
actually
made
this
sorry
Firefox
step
fail,
so
you
can
see
here
that
the
files
failed
and
in
that
this
step
has
actually
failed.
So
we
know
who
that
yeah.
This
all
is
some
junk
in
here
but
say
if
I
was
running,
say
my
test
runner.
It
would
automatically
hone
in
on
the
fact
that
you
know
you
executed
your
test
runner
and
the
test.
Runner
failed
and
maybe
I
need
to
go.
B
Have
a
look
at
my
unit
tests
to
see
what
the
test
failures
on,
though
it's
quite
quick,
I
do
get
a
lot
of
questions
about.
You
know
no
I,
you
know
from
people
who've
been
using
Jenkins
for
a
long
time
and-
and
they
ask
you-
know:
I
have
a
lot
of
freestyle
jobs
on
my
freestyle
jobs
compatible
with
blue
ocean
and
the
short
answer
is
yes.
B
A
more
longer
answer
is
that
you
know
all
of
the
nice
things
that
we
have,
like
you
know
the
pipe
line
visualization
and
the
branching
and
the
poor
requests
those
those
features
can't
work
with
freestyle
jobs,
they're
a
different
job
type.
They
work
in
different
ways
to
pipeline.
But,
however,
just
as
a
sort
of
this
would
be
rest
assured
you
can
see
here.
I
have
this
for
this
freefall.
Job
called
fetal,
and
you
can
see
here
if
I
click
over
to
its
configuration,
it's
very
simple.
B
B
All
right
call
that
finished,
so
you
can
see
here
that
the
big
difference
between
freestyle
jobs
and
pipeline
jobs
in
promotion
is
that
you
know
pipeline
is
able
to
visualize.
There
are
the
steps
that
have
occurred
within
the
job
and
also
the
phases
like
the
stages
of
that
job.
So
we
can't
have
that
visualization
here,
however,
things
like
you
know
giving
those
the
changes
or
the
tests
that
this
job
is
actually
executing
and
reporting
on
them.
B
One
of
my
favorite
features,
one
of
my
favorite
features
in
flourishing,
is
personalization.
What
was
the
personalized
dashboard
so
really,
when
you
come
to
Jenkins,
you
usually
coming
to
Jenkins,
because
something
has
gone
wrong
right,
so
we
really
wanted
to
make
Jenkins
more
relevant
for
developers
when
they
first
when
they
first
inside
the
user
interface,
simple
favoriting
system.
So
we
have
these
little
stars
here.
B
Hopefully
this
is
showing
up
okay
on
the
video
feed.
If
I
go
ahead
and
click,
these
I
can
add
a
favorite
card
to
my
dashboard
for,
say
the
fetal
freestyle
job
info
online
jam
demo
and
even
actual
demo.
So
if
I
favorite
a
from
the
dashboard,
if
I
favorite
a
pipeline,
what
I'm
really
doing
is
favoriting
the
default
branch
of
that
pipeline.
B
B
What
I
can
also
do
is
click
favorite
on
you
know,
topic
fails
all
the
time.
So
if
I
go
back
to
my
dashboard
and
say
say
in
a
scenario,
I've
come
in
in
the
morning
and
I've
noticed
that,
oh
you
know,
I
change
later
made
last
night
to
that
branch.
Doesn't
work.
I
can
just
quickly
click
through
and
see
very,
very,
very
quickly
like
where
that
failure
had
a
curb
I
can
then
exit
out
and
go
back
to
my
dashboard.
B
B
B
B
We
really
want
to
focus
on
making
the
experience
around
that
pipeline
editor
even
better,
so
there's
a
lot
of
work
that
we
need
to
do
to
make
blue
ocean
visual
editor
have
feature
parity
with
declaratives,
so
there's
a
lot
of
great
features
into
clarity
pipeline.
So,
if
I'm
running
post
steps,
there's
stage
level
configurations,
all
sorts
of
really
great
things
in
declarative
that
we
want
to
make
sure
are
reflected
in
the
editor,
but
I
think
a
big
challenge
here
is
that,
as
we
add
more
features
to
the
editor,
the
editor
becomes
less
simple.
B
So
we
need
to
do
some
design
work
here
to
figure
out.
You
know
you
know
we
really
got
to
think
about
that
beginner
user
coming
in
at
trying
to
do
continuous
delivery
for
the
first
time.
So
if
or
if
we
map
in
all
of
those
features,
we
really
want
to
make
sure
that
that
doesn't
really
get
in
the
way
of
that
that
novice
developer
who's,
creating
that
CD
pipeline
for
the
first
time.
But
it
also
means
that
we
don't
want
to
hide
those
features.
B
So
it's
really
difficult
for
the
more
intermediate
advanced
users
to
access
those
features.
So
it's
a
real
sort
of
balancing
act
here
that
we
have
to
we
have
to
perform
in
order
to,
you
know,
make
sure
all
of
the
different
user
types
who
will
be
using
the
editor
are
well
certified
and
that
kind
of
also
leads
into
support
for
other
version
controls
providers
get
providers,
I
should
say
so
today.
We
don't
really
have
any
plans
to
support
it's
a
subversion
or
perforce
with
that
new
pipeline
flow.
B
It's
it's
kind
of
quite
difficult
to
support
it,
even
if,
in
the
get
case
for
you
know
there
was
a
question
earlier,
are
we
gonna
support
your
hub
enterprise?
So,
yes,
we
are
going
to
support
github
enterprise.
That
is,
you
know,
coming
shortly,
and
but
we
also
want
to
go
and
support
that
new
pipeline
flow
for
git
repositories.
So
if
I
actually
go
back.
B
B
B
So
one
of
the
things
that
we're
going
to
be
adding
next
is
the
ability
to
read
and
write
that
Jenkins
file
to
any
git
repository.
So
it
doesn't
matter
if
you're
using
git
lab
bitbucket
dogs
gets
here,
you're
hosting
your
own
git
repository
server.
You
know
using
the
the
open
source,
get
server
daemon
and
all
those
sort
of
things
like
doesn't
matter
what
system
is
hosting
that
git
repository?
We
want
to
talk
to
it
and
allow
that
reading
and
writing
of
the
Jenkins
file.
B
However,
we
want
to
make
sure
that,
because
you
know
the
differences
between
there's,
there
is
a
sort
of
tangible
difference
between
the
requirements
of
github
and
yet,
in
terms
of
you
know,
you
know,
authentication,
mechanism
etc
and
forks
that
we
really
need
to
kind
of
make
focus
in
on
like
how
we
can
make
that
experience
forget
just
as
easy
as
the
github
one
and
that's
really
the
challenge.
So
a
lot
of
the
things
in
blue
ocean
that
we
built
the
challenge
are
actually
hasn't
been
building
the
technology.
B
The
challenge
has
been
in
presenting
it
in
a
clear
and
concise
way
in
it
in
a
usable
way.
Today
you
know
we're
the
ones
that
have
to
you
know,
as
the
authors
of
the
ocean
we're
the
ones
that
have
to
deal
with
the
complexity,
you,
as
the
user,
do
not
have
to
deal
with
it
where
we
are.
We
are
also
looking
at
adding
a
fast
search
to
the
blue
ocean
dashboards.
So
one
of
the
limitations
there
is
and
I'll
just
pop
over
to
our
room
themes
are
in
blue
ocean
server
when
I'll
zoom
in
here.
B
B
But
but
the
point
here
is
that
you
know
you
can
get
quite
tedious
if
you're
searching
for
a
particular
pipeline
in
here,
just
a
click
show
more
show
more
so
there'll
be
an
area
up
the
top
here,
where
you
can,
you
know
activate
with
a
keyboard
shortcut
in
to
start
typing,
the
name
at
pipeline
you're.
Looking
for
and
have
this
whole
dashboard,
including
the
favorites
filtered
down
onto
that
query,
so
it'll
be
really
really
quick
way
to
look
outside
lines
all
right.
B
So
if
you
want
to
learn
more
about
blue
ocean,
you
can
visit
our
site
at
Jenkins,
io
/
project,
slash
blue
ocean.
We
also,
you
know
we
do
you
know
it's
little
erosion
and
Jenkins
a
open
source
project.
So
we
do
all
of
the
you
know
development
out
in
the
open.
So
we
have
there's
a
github
repository
that
contain
all
the
Russian
code.
B
I
mean
if
this
feels
likely,
if
you
feel
like
contributing
anything
to
blue
ocean,
you
can
just
follow
that
link
there
and
we've
got
links
to
all
of
the
details
of
like
where
you
can
find
the
repository.
We
also
use
the
Jenkins
JIRA
issue
tracker
to
track
all
of
our
development
work.
We
even
have
like
one
of
those
cambian
boards
there
for
the
sort
of
paid
members
of
the
team
to
use
throughout
the
day
when
they
as
they're
working
on
features
and
so
you're.
B
More
than
welcome
to
go
and
have
a
look
at
that
as
well.
Links
are
up
on
the
web
page
and
we
also
have
a
team
chat
and
a
community
chat
on
github,
which
is
kind
of
like
you
can
kind
of
think
of
it.
As
like,
IRC
or
slack
or
HipChat
for
forget,
you
can
check
this
out
with
us
head
on
get
up
at
that
bitly
link
on
the
screen
just
like
to
say
thank
you
to
Liam
and
ELISA
for
organizing
the
jam
and
thanks
for
watching
hey.
A
B
It
is
possible
today
to
extend
the
blue
ocean
front-end,
so
we'd
give
we
use
react.js
from
Facebook
for
all
the
UI
components
and
we
do
have
a
sort
of
a
rudimentary
way
of
extending
providing
your
own
react
components
to
the
UI
and
then
you
can
call
out
you
know:
blue
oceans,
rest
API,
stuff,
it's
a
brand
new
REST
API
in
blue
ocean
that
we
built
to
kind
of
power.
The
UI.
However,
we
realize
you
know
we.
B
There
are
some
sort
of
rudiment
I
guess
how
to
sort
of
how
rudimentary
like
that
implementation
of
the
extension
point
system
is
so
there
is
work
at
the
moment
to
go
through
and
we're
going
to
send
a
proposal
to
the
Jenkins
UX
mailing
list,
proposing
a
new
extension
system
and
or
and
at
one
of
the
design
goals
of
this
extension
system,
is
to
have
a
SDK
like
experience
for
building
blue
ocean
plugins.
So
if
you've
used,
you
know
the
HPI
plug-in
the
Maven
hbi
plug-in
to
create
maven
plugins.
B
B
We
want
to
at
least
have
that
kind
of
experience
for
blue
urchin
plugins,
if
not
better,
so
that
that's
we're
actively
working
on
that
like
oh,
we,
we
have
a
we're
in
a
situation
where
we
don't
feel
that
we
are
productive
enough
as
a
team
to
be
able
to
build
blue
ocean
itself
without
solving
this
problem
so
expected
in
the
next
couple.
It's
like
something
usable
in
some
of
the
next
couple
of
months,
but
you
know
we
are
working
really
hard
on
on
making
that
possible.