►
From YouTube: 2022 07 22 Docs Office Hours
Description
Documentation office hours 22 July 2022 with topics including
* Google Summer of Code results and review
* Look and feel improvements for the jenkins.io site
* Blue ocean admonition for inclusion on the Blue Ocean tutorials and other Blue Ocean documentation pages
A
A
A
C
So
this
is
the
we
have
reached
the
midpoint
of
the
of
google
summer
of
code
we're
halfway
through
the
summer
already
the
kids.
Sometimes,
I
can't
believe
we're
already
here,
but
earlier
or
yesterday
or
depending
earlier
today,
depending
where
you
are
in
the
world,
there
was
a
online
meetup
where
all
the
different
students
who
worked
on
projects
kind
of
give
a
midpoint
presentation
about
their
stuff
and
if
you're
interested
in
watching
the
vihans
is
near
the
end.
C
Actually,
I
think
this
is
the
last
presentation,
so
you
can
skip
forward
through
a
lot
of
the
video
and
take
a
look
at
the
amazing
work.
He's
done
a
lot
of.
Like
summary,
a
lot
of
it
has
been
improving
some
of
the
docs
website
stuff
in
general,
doing
some
massive
upgrades
to
the
generator
oh
yeah,
so
they
wanna
upgrades
to
the
generator
the
website
improvements
I'll,
go
back.
C
C
And
the
next
phase
is
going
to
be
improving
some
of
the
incredibly
large
pieces
of
documentation
that
we
have,
for
example,
the
step
step
or
the
checkout
step,
where
there's
just
a
lot
of
information
going
on
so
beyond.
Like
did
a
great
job
like
running
to
the
fit
like
getting
this
stuff
out
for
the
end
of
coding
phase
one
so
he's
gonna
regroup
and
come
up
with
some
preliminary
designs
that
will
probably
be
shared
in
future
docs
office
hours
and
on
the
docs
channel.
C
A
C
C
A
A
Well,
thanks
thanks
very
much
to
him
and
to
your
work.
It's
that's
really
impressive,
all
right!
So
one
new
and
then
different
topic,
we've
got
a
pull
request
out
for
look
and
feel
improvements
to
the
jenkins
page
to
the
to
the
whole
site,
and
so
let's
take
a
look
at
it
just
to
give
hints
as
to
what's
being
proposed.
It
looks
for
me
it
looks
really
good
there.
There
are
a
couple
of
weaknesses
that
I
found
just
today
in
exploring
so
here's
the
proposed
new
layout
and
let's
compare
it
to
the
existing
layout.
A
Right
right,
so
the
jumbotron
is
above
the
above
the
fold
at
least
on
my
screen
like
it
was
before
now
there
is,
there
is
the
the
hiccup
I
found
was
this
one
if
I
shrink
to
a
particular
size
like
4x3
1024,
there's
an
overlap
thing
here
that
doesn't
happen
here
with
the
image,
though
it
does
happen
with
the
scr
the
bar.
So
if
I
go
there,
image
is
still
pushing
it.
So
somehow
the
image
is
not
resizing
downwards,
even
though
it's
svg,
and
so
that's
what
I
need
to
ask
him
about
to
see.
A
B
A
Yeah,
okay,
so,
as
it
turns
out,
I
don't
have
to
coordinate
with
gavin.
Gavin
has
has
adopt
adapted
plugins.jenkins.io
already
to
the
new
layout.
So
as
soon
as
we
are
ready
to
merge
it
ready
to
merge
anytime,
cool,
yeah
and
and
again,
this
is
this
is
just
a
contributor
who
sort
of
came
out
of
nowhere
and
said
I'd
like
to
help
and
has
been
through
several
iterations
to
get
it
to
this
point.
A
A
A
A
A
A
B
A
A
A
C
A
A
A
Well,
in
this
case,
it's
not
because
we
don't
want,
we
don't
want
to
shut
down
the
the
tutorial
pages
they
still
work
and
and
as
part
of
this
development
work,
kevin
actually
went
through
and
did
the
tutorials
and
he
confirmed
yes
in
fact,
they
do
still
work
okay.
So
it's
it's
not
a
matter
of
we're.
We're
telling
someone
to
do
something.
That's
broken.
Okay,.
A
But
what
kevin's
created
is
this
reference?
This
insertable
snippet
that
we'll
put
into
multiple
pages,
so
blue
ocean
will
not
receive
further
functionality.
Updates
blue
ocean
will
continue
to
provide
easy
to
use
pipeline
visualization,
but
will
not
be
enhanced
further.
It
will
only
receive
selective
updates
for
significant
serious
security
issues
or
functional
defects.
C
B
A
B
B
B
A
A
A
B
And
did
he
find
it
I'm
going
through
the
the
tutorial
or
whatever
that,
because
I
you
know
at
one
time
it
was
all
blue
ocean
all
the
way,
but
fairly
early
now
at
least
when
I
last
saw
the
tutorial
fairly
early
in
it.
It
says:
okay,
now
here's
how
you
work
with
pipelines
outside
blue
ocean
and
from
here
on
you
can
do
it
either
way.
A
And,
and
that
I
don't
know
so,
I
think
that
depends
on
the
tutorial
right,
because
some
of
the
tutorials
are
are
completely
free
of
blue
ocean.
They
use
no
blue
ocean
at
all,
or
they
barely
use
any.
So,
for
example,
the
maven
tutorial
is:
let's:
let's
go
there
just
for
a
minute,
so
the
maven,
the
python
node
and
the
python
tutorials.
All
three
of
these
tutorials
make
very
little
use
of
blue
ocean
because
they
really
don't
need
it
right.
A
See
this
one
just
shows
you
copy
and
paste
these
pipelines.
Steps
in
it
doesn't
even
show
you
blue
ocean,
it
just
says:
hey
look,
this
is
this
is
how
you
do
it
and
copy
and
paste,
and
that
for
a
tutorial,
that's
actually
a
fine
thing
right,
there's
no
harm
in
doing
it.
It's
it's
intentional!
You
can.
You
can
just
copy
and
paste
this
thing.
A
C
A
A
Now
I
gotta
look
and
see
nope
nope.
Even
this
one
is
not.
This
one
is,
is
guiding
you
in
doing
something
very,
very,
very
simple:
you're,
not
designing
the
pipeline
with
the
blue
ocean
editor.
So
it's
not
using
the
editor.
I
thought
we
did
have
one
that
did
did
the
editor,
but
I
obviously
I'm
not
oh
yeah
here
it
is.
A
A
So
so
one
of
the
things
that
I
wanted
your
feedback
on,
though,
is,
and
I'm
going
to
show
you
the
prototype
site
to
get
that
feedback
is
the.
Where
do
we
put
these
in
each
page
so
hold
on
just
a
minute
while
I,
while
we
look
at
that
together
and
let's
view
the
deployment
here,
oh
is
this
it?
No,
that's
the
that's
the
current
one
so
view
deployment.
A
A
B
A
C
C
C
B
B
A
A
A
C
A
C
B
A
B
If,
if
somebody
was
really
new
to
this
and
really
befuddled
and
needed
to
set
up
their
first
pipeline,
I
might
tell
them
to
go
to
blue
ocean
and
set
up
just
their
stages.
Just
get
the
basics
there,
it's
right
a
world
of
hurt
and
and
then,
if
you're
worthy
of
doing
pipelines,
you're
going
to
want
out
of
it
so
except
for
visualization
stuff.
A
See-
and
that
was
my
worry-
is
that
if
we
don't
put
it
on
every
single
page,
well
as
an
example,
there
are
some
pages
where
it
just
makes
sense
to
put
it
in
this
one
right
here,
for
instance,
I
don't
that's
an
awful
screenshot,
it
clearly
needs
a
repair.
Oh
no,
this
is
this
is
I'm
sorry.
This
is
this.
Is
this
is
leah
marking
it
up?
C
B
I
want
that,
if
they're
going
to
do
much
with
pipeline
they're
going
to
have
to
look
at
more
than
one
page
right
correct,
you
know,
so
I
don't
know
just
to
to
me,
but
that
it
will
not
receive
further
functionality,
updates,
continue
practice
use
like
if,
at
the
beginning
of
blue
ocean,
you
have
the
whole
thing
and
then
just
have
like.
What's
those
three
lines,
which
will
probably
be
two
lines
of
text,
the.
A
C
Right
then
that's
this
is
not.
I
mean
this
is
more
of
an
existential
jenkins
question:
that's
not
a
good
sign.
If
we
have
a
ui,
that's
supposed
to
be
about
pipeline
visualization,
we
decide
not
to
continue
working
on
it
and
then
don't
have
a
good
alternative
that
will
potentially
receive
updates
security
patches
et
cetera.
A
A
Because
because
I
think
you're
right,
we've
got
to
have
pipeline
visualization
and
today
we've
got
blue
ocean
and
today
it
works
and
it
visualizes
pipelines.
This
graph
view
thing
is
actually
pretty
close
to
a
blue
ocean
replacement
for
the
visualization
piece.
It
just
doesn't
render
every
pipeline
as
accurately
as
blue
ocean
does.
B
A
A
B
A
Oh,
oh,
I
see
your
point.
There
is
alternative
options
for
pipeline
creation
might
be
another
way
of
phrasing.
It
interesting
yeah.
So
maybe
maybe
that
further
argues
for
your
your
idea
that
first
first
three
sentences
everywhere
these
two
on
pages
that
are
are
related
to
visualization
and
maybe
additional
some
additional
texts
on
pages
that
are
related
to
pipeline
creation,
like
this
create
a
pipeline
in.