►
From YouTube: 2020 10 05 Docs Office Hours
Description
Jenkins documentation office hours reviewing Hacktoberfest results and a proposal for a tutorial image that replaces the blueocean image with an extension of the standard Jenkins image
A
A
Been
hacktoberfest
progress
report,
probably
for
me,
jenkins,
docker,
tutorial
fixes.
This
is
one
vlad
where
I
wanted
to
just
ask
you
some
questions
to
clarify
what
you
learned
from
that
and
have
you
share
with
us?
Oh
hey.
I
had
to
make
these
changes
this
way
and
this
way
in
order
to
make
the
tutorial
work
so
you've.
If
I
understand
the
tutorial,
I
haven't
the
fix
I
haven't,
I
haven't
read
it
in
detail
yet,
but
it
replaces
the
blue
ocean
image
with.
A
C
No,
not
this
different.
I
just
sent
some
prs
to
earn
my
to
32
and
right
now
we
have
all
issues
with
registers
on
with
github.
So
now
we
need
to
work
on
it.
C
So
maybe
maybe
not
I'm
sure
in
the
next
weeks
I
will
just
work
on
page
migrations,
great.
A
A
So
the
proposal
is
I'll.
Do
an
introduction,
welcome
everyone
to
oktoberfest.
Oleg
will
do
a
talk
about
how
you
can
contribute
to
jenkins,
including
the
featured
projects,
and
then
we
wanted
to
do
a
and
jonathan.
What
I
was
assuming
here
was.
This
is
three
to
five
minutes.
No
more
just
with
you
describing
hey.
Look.
Here's
here
are
the
metrics
we've
been
using.
A
So
maybe
you
show
the
graph
of
the
of
the
wiki
migration
progress
here.
Is
the
table
we're
using
and
here's?
Why
we're
doing
having
two
people
review
every
issue?
We
create
to
be
sure
that
hacktoberfest
good
first
issues
are
really
good.
First
issues
that
was
sort
of
what
I
was
assuming
so
three
to
five
minutes.
A
Right
right
for
me,
I
think
I
think
people
may
not
understand
that
as
a
first-time
contributor,
we've
done
quite
a
bit
of
work
to
try
to
make
things,
make
them
successful
as
a
first-time
contributor,
yeah,
again,
okay
and
then
vlad
we
were
going
to
have
you
do
building?
Oh
sorry,
jenna
jonathan.
Did
you
have
more.
A
B
Yes,
I
am
a
key
doing
this.
I
just
wanted
to
ask
mark.
Is
it
a
key
if
I
will
use
a
visual
visual
code
id.
A
A
I
think
you
can
assume
familiarity
with
an
ide
and
actually
you
can
assume
familiarity
with
visual
studio
code.
Now,
if
there's
something
where
you've
discovered
an
interesting
or
powerful
technique,
you
use
with
visual
studio
code
by
all
means
highlight
that
to
them,
because
if
they
see
you
do
something
interesting
and
then
you
explain.
Oh
the
reason
this
worked.
This
way
is
because
I
did
this
in
visual
studio
code
that
will
tend
to
keep
them
even
more
interested.
C
C
A
B
A
B
A
No,
no,
no,
that,
because
yours,
yours
is
a
demonstration
oleg
will
not
do
a
demonstration
right.
Oleg
will
just
talk
so
you
usually
the
demonstrations
are
inevitably
longer
and
I
think
you
should
be
perfectly
perfectly
willing
if
you
go
less
than
20
minutes,
that's
okay,
but
but
we'll
take
the
20
we'll
give
you
20
minutes
for
sure.
A
C
Okay
and
each
video,
we
will
be
required
there,
each
video
for
each
oh.
A
No,
we're
not
sure
right,
we
will
do.
We
will
just
do
a
recording
of
the
entire
session
and
you'll
be
presenting
live
and
you
can
share
your
screen
or,
if
you
want
to,
if
you
have
slides
that
you'd
like
me
to
share
I'm
confident.
Oleg
will
use
slides
and
if
you
have
slides
you'd
like
to
share,
we
can
have
you
share
them
or
you
can
send
us
the
google
slides
and
we'll
embed
them
into
a
single
slide
deck
for
the
whole.
C
Yeah
I
asked
because
after
the
meeting
we
can
use
the
videos
as
tutorial
next
next
year
so,
for
example,
the
vlad
video
it's
important
to
good
first
issues
and
your
presentation
too.
For
example
the
next
work
we
work
on.
It's
about
plug-in
migration,
exactly.
A
A
A
I
think
I
just
stole
yours
from
the
the
author,
the
blog
author,
bio,
on
on
jenkins.io,
but
great
all
right.
So
so
that
feels
like
we've
got
a
reasonable
understanding
of
what
we'll
do
there.
So
then,
I
need
to
put
the
action
item
from
mark
to
publish
and
promote
the
jenkins.
B
Online,
just
just
let
me
ask,
do
you
need
any
help
with
promoting
like
on
social
media
kind
of
on
twitter
or.
A
A
I
think
that's
been
our
pattern.
I'll
have
to
double
check
that
one,
but
I
believe
we've
sent
those
in
the
past
to
the
jenkins
user
list,
any
other
locations
where
you,
oh,
oh,
we
should.
We
could
consider
reddit,
that's
a
new,
a
new
channel
that
only
just
recently
arrived
and
getter.
B
A
A
A
C
So
mark
to
event,
we
need
to
put
the
tag
to
each
issue.
A
Right
so
they'll
detect
them
just
fine,
so
the
contributors
get
credit
for
their
contribution
just
by
the
presence
of
this
one
tag,
I
just
for
me,
it's
a
convenience.
If
we
also
label
with
hacktoberfest,
because
then
we
can
do
queries
ourselves,
but
that's
that
is
not
a
requirement
at
all.
It's
just
a
convenience
for
us.
A
So
if
we
look
at
the
closed
closed
issues,
for
instance,
all
these
redirects
are
hacktoberfest
contributions
but
of
course,
they're
pull
requests
to
a
different
repository.
So
congratulations.
The
redirect
pull
request
that
you
created
the
the
redirect
process
started
just
well.
You
see
it
here
five
days
ago,
20
hours
ago,
etc.
It's
great
progress
from
those
redirect
pull
requests.
A
C
A
That
would
be
wonderful
now
now
there's
the
embarrassing
thing
here
that
this
blue
line
on
the
left
shows
where
I,
where
my
triage
my
review
process
stopped
where
I
ran
out
of
time.
So
I've
still
got
a
bunch
of
things
that
I
need
to
review
for
hacktoberfest
and
I
apologize
jonathan.
I
haven't
done
them
yet.
So
there
are
many
many
more
that
I
need
to
review
and
I
believe,
no
problem
mark.
If
you
need
some
help,
just
ask.
A
Yeah
so
it
looks,
it
looks
very
positive,
excellent
progress
on.
A
A
Sva1,
yes,
av1,
no
sda1,
no,
I'm
not
finding
it,
but
there
was.
There
was
another
author
that
submitted-
and
this
was
an
action
item
I
had
from
last
week-
was
to
create
these
terminology.
Pull
requests
like
this
one,
and
this
one
and
this
one
and
one
of
them,
has
already
been
taken
and
resolved
all
the
way
to
done.
A
I
am
simply
amazed
that
we
got
there
because
for
me
this
was
a
very,
very,
very
hard
one
to
imagine
successfully
working
on,
so
it
is
use
jenkins,
official
jenkins,
docker
image
for
tutorials,
and
the
challenge
here
is
that
we
need
to
test
it
locally
before
it
merge
before
we
merge.
But
this
looks
so
promising
tell
us
about
what
you
learned
that
vlad.
What
were
the
things
that
you
had
to
change
in
order
to
make
this
work.
B
Well,
as
as
you
know,
the
goal
kind
of
one
standing
goal
is
to
stop
using
outdated
blood
ocean
image
and
start
using
official
jenkins
jenkins,
docker
image.
I'm
talking
about
joker
image
right
now
and
the
problem
with
the
docker
image.
Well,
several
problems.
First,
there
is
no
blue
ocean
plug-in
inside
it,
and
blue
ocean
is
kind
of
it's,
not
one
plug-in,
but
several
plug-ins
and
very
interesting,
and
one
of
the
latest
projects
of
jenkins
and
calvi's
and
a
lot
of
people.
B
I
guess,
are
using
this
and
another
problem,
which
is
actually
more
interesting
that
in
case
we're
going
to
use,
for
instance,
declarative
pipelines
or
any
pipelines.
One
of
the
powerful
things
about
pipelines
that
we
can
use
are
ephemeral
agents
with
docker,
for
instance,
and
well.
B
Using
this
image
will
allow
us,
of
course,
to
modify
this
pipeline,
but
execution
will
fail
because
we'll
not
be
able
to
access
docker
cli
will
not
be
able
to
use
docker
cli
inside
that
jenkins,
and
there
are
a
lot
of
discussions
going
back
to
I
guess
several
years
ago
how
to
properly
solve
these
issues,
and
people
are
talking
about
docker
and
docker,
and
somebody
saying
and
I
somewhere,
I
guess
on
tithe-
have
summarized
all
these
issues
while
preparing
to
google
season
of
docs
for
this
year
and
people
are
saying
well
docker
in
docker.
B
It
is
not
deemed,
which
is
acronym
for
docker
and
docker,
which
is
used
by
docker
themselves
in
case
if
people
would
like
to
develop
contribute
to
docker
open
source.
B
But
eventually
there
is
some
sequence
of
commands
which
we
can
install
inside
docker
file
and
create
another
image
from
our
official
docker
image,
which
will
allow
us
to
access
docker,
cli-
and
I
tested
this
on
my
mac
and
on
windows,
and
it
was
of
course
not
very
extensive
testing,
but
just
sanity
test,
and
it
worked,
and
I
also
tested
it.
Oh
well,
with
simple
declarative
pipelines.
I
tested
it
with
some
tutorials.
B
One
of
the
meetups
organized
by
cd
foundation.
Well,
I
thought
well,
I
can
just
submit
this
pull
request,
which
I
did
actually
over
this
weekend
and
well.
I
got
some
comments
from
oleg
which.
B
I
trying
to
understand
how
to
approach
to
this.
There
is,
of
course,
different
ways
how
we
can
expand
and
in
which
direction.
We
can
go
after
that,
because
I
specified
only
for
tutorials,
because
our
installation,
as
probably
you
recorded
in
your
discussions
with.
B
B
I
guess
you
mentioned
that.
Well,
this
installation,
jenkins
installation
page
in
our
documentation
is
very
large
and
it
needs
to
be
somehow
modified,
maybe
brought
into
different
chapters
like
dividing
different
chapters,
but
I
noticed
in
one
of
this
discussions
recorded
on
youtube.
You
mentioned
well,
there
are
some
other
people
working
on
this,
and
probably
you
meant
are
jonathan
and
myself.
A
B
There
are
different
files
responsible
for
just
installation,
but
just
target
just
tutorials
for
now
and
like
wait
for
decision
consensus
which
will
be
made,
how
we're
going
to
restructure
installation
page
isn't
going
to
be
like
several
sections
or
somehow,
but
today
I
guess
oleg
made
this
comment
about
this.
B
It
is
a
little
bit
lower.
I
guess
he
made
this
comment
about
great
simple,
quick
start
guide.
He
mentioned
in
his
comment
and
I'm
trying
to
understand
what
exactly
is
meant
by
that
and
where
this
quick
start
guide
should
go,
is
it
going
to
go
in
documentation
or
in?
A
So
so
when,
when
oleg
says
customize
the
the
customize,
the
image
he's
talking
about
this
step
that
you
have
very
first
here
of
create
a
docker
file
and
and
that's
the
step,
and
I
unders.
I
think
I
understand
why
you
did
it
by
creating
the
docker
file.
This
will
let
you
install.
B
Later,
I
assume
right
but
well,
for
this
specific
addressing
pipelines.
This
can
be
done
kind
of
manually,
and
this
I
can
describe
because
after
starting,
for
instance,
jenkins,
we
can
either
manually
install,
for
instance,
blue
ocean
plugin,
or
using
plugin.txt
or
whatever,
whatever
like
approach
we'll
choose,
but
with
automatic
plugin
installation.
Well,
this
is,
I
guess,
we're
discussing
video
under
this,
but
with
automatic
plugin
installation.
B
It
looks
that
we
need
to
know
the
set
of
plugins,
which
is
installed
in
the
base
docker
image
which
we're
using.
So
if
we're
using,
for
instance,
this
lts
241.
B
We
need
to
know
the
set
of
plugins,
which
is
installed,
and
we
can
add
blue
ocean,
for
instance,
to
it,
and
this
is
what
I'm
doing
on
there
is
github
repository
called
ci
cd,
which
I
ordered,
where
I
am
describing
this
entire
process,
which
actually
I
did
on
presentation,
and
so,
but
it
is
kind
of
I
sharing
it
with
community.
But
probably
you
are
not
aware,
and
I
can
of
course
point
and
see
if,
if
you're,
okay,
with
this
approach,
we
can
just
somehow
embed
this
inside
our
quick
start
or
process
like
how
to
proceed.
A
B
And
yeah,
let
me
know
mark
if
you
need
any
help
with
the
references,
because
I
collected
while
preparing
to
google
seasonal
dogs
a
lot
of
different
references
for
research,
articles
about
docker
and
docker,
and
what
it's
really
isn't:
dangerous,
not
dangerous.
And
so
on
and
like.
A
That's
right,
yeah
and
and
the
platform
special
interest
group
is
discussing
how
we,
how
we
shift
off
of
debian,
in
this
case
debian
10
9
and
get
on
to
debian
10..
So
that's
this
is.
This
is
great
excellent.
Thank
you
I'll
I'll,
do
some
experiments
and
certainly
give
you
feedback.
Thank
you.
Thank
you
and.
B
Just
just
some
something
that
I
one
of
the
approach
which
we
can.
I
can
try
to
simplify
things,
but
one
of
the
approach.
We
can
take
docker
file
from
our
docker
plugin
itself
and
there
are
a
lot
of
docker
files
listed
over
there,
which
uses
the
base
image,
not
our
released
version
of
jnk
docker
jenkins,
but
something
like
opengdk
or
whatever
is
based,
and
but
it
will
be
much
longer
joker
file
and
much
more
complicated.
And
I'm
not
sure
that
we
need
to
do
this
in
our
documentation.
A
This
is
something
which
oh,
oh,
versioning,
and
that's
an
interesting
one,
because,
oh
that's
fun.
We
now
have
the
ability
in
in
generating
other
pages,
to
actually
embed
this
number,
where
this
number
is
the
current
jenkins
release,
so
that
we
might
be
able
to
make.
I
I'll
have
to
do
some
investigating
to
see
we
might
be
able
to
make
this
page
automatically
populated.
With
the
current
jenkins
lts
version
number.
A
You're,
looking
at
the
source
code
right
for
the
docker
repository
right
and
and
this
this,
this
has
a
very
distinctive
build
process
that
causes
that
that
distinctive
build
process
causes
the
version
number
that's
embedded
in
the
file
to
so
this
one
says,
for
instance,
it's
jenkins
2.176.2,
but
it's
used
because
this
is
a
parameter.
It's
used
to
generate
every
jenkins
version,
just
by
changing
the
parameter.
B
And
there
is,
there
is
releases,
I
guess
somewhere
correct,
right
yeah.
There
are.
A
2.249.1
lts
centos
7,
2.249.1,
lts,
jdk,
11,
etc,
good
okay,
so
we
are
current.
Oh
that's
and
that's
an
interesting
one
I'll.
We
should
not
do
a
code
review
live
here.
That's
not
the
purpose
of
our
meeting
today.
I'll
do
I'll
review
and
I'll
give
some
feedback,
because
there
are
some
there.
I
think
there
are
things
we
may
be
able
to
change
here,
to
make
this
more
relevant
to
users
and
less
likely
to
have
to
change
good
excellent.
B
Well,
just
fit
his
channel
best
practice
about
docker
file
and
I
guess
you
and
alec
highlighted
several
times
in
your
presentations
and
video
recordings
that,
when
we're
using,
for
instance,
base
image,
it's
better
to
specify
not
just
long-term
support
release
but
specific
version.
So
we
know
from
where
this
way
called
we're
deriving
all
features.
A
B
Good
well
and
in
documentation
itself,
I.
B
Showing
us
the
diffs
right
under
windows,
I'm
using
like
different
for
no.
B
On
windows,
so
here
yeah
on
windows,
all
right,
it
is
I'm
using
this
different
docker
command,
with
different
continuation
for
lines
that
is
using
as
before
terminal
and
my
machine
I'm
using
something
called
github
terminal
which
allows
to
use
or
github
window.
I
guess
it
is
called
which
allows
to
use
game
notation,
the
same
syntax
as
on
linux
machines.
B
So
we
don't
need
to
use
this
little
symbols
instead
of
quotes
forward,
slashes
continuation
on
the
next
slice,
okay,
but
but
it
involves
like
explaining
how
you
need
to
install
github
terminal
and
it
involves
extra
software.
That
is
why
I
just
thought:
well
maybe
in
documentation
to
use
extra
paragraph
but
not
discuss
what
needs
to
be
done
to
install
extra
software.
B
Well,
it
is
not
covered
in
this,
but
as
as
I
mentioned
in
case,
if
we
want
to
add
plugins
in
automatic
way,
we
need
to
learn
this
exact
set
of
plugins
in
the
previous
version
of
jenkins
that
you
are
trying
to
derive
from,
and
so
there
is
specific
script.
I
guess
which
allows
us
to
get
the
current
plugin
list
of
plugins
from
the
current
version.
If
you
do
a
simple
rest
request.
A
There
is,
although
in
in
this
particular
case,
I
think
that
there
is
a
a
relatively
simple
shortcut
that
we'll
be
able
to
use
where
we,
let's
see.
If
I
can
find
the
documentation,
it
will
tell
us
about
installing
the
plugins.
Yes
here
it
is
so
there's
a
new
plugin
installation
manager,
command
line
interface.
That's
been
bundled
as
a
preview,
and
we
can
call
it
like
this
and
by
calling
it
like
that,
it
will
install
all
the
dependencies
for
us
and
the
benefit
of
that
is.
A
If
we
say
this
run,
minus
minus
plugins
and
we
say
blue
ocean,
it
will
install
the
entire
blue
ocean
suite
all
25
plugins
by
us
calling
for
one
plugin.
Oh
it's
interesting
and
likewise
github
branch
source
here
when
it's
called
we'll
install
the
git
plug-in
the
git
client
plug-in
and
several
others,
because
they're
all
dependencies
of
it.
So
if
we,
if
and
there's
one
plug-in
for
the
declarative
pipeline
and
maybe
even
one
for
the
whole
for
all
of
pipeline
plug-ins,
so
we
may
be
able
to
put
in
a
one-liner
into
your
existing
script.
B
So
it
will
okay,
so
it
knows
how
to
get
the
existing
list
of
plugins
and
just
extend
it
by
what
we
already.
I
see,
create.
B
Thank
you
very
much
mark
for
pointing
this
out,
because
last
week
presentation
I
was
like
doing
extra
step
by
doing
rest
requests
to
existing
host.
Oh
that's
great
excellent.
Thank
you.
B
No
just
wanted
to
say
that
I
was
planning
to
expand
it
to
installation
to
keep
in
sync
tutorials
and
installation,
or
I
can
wait
for
your
comments
mark.
Let
me.
B
A
B
A
B
Okay,
I'm
glad
just
just
I
wanted
to,
of
course
remind
that
you
provided
recently
these
five
issues,
recurring
updating
terminology
and
you
label
those
as
newcomer
like
good
newcomer
contributions,
something
like
this.
So
should
we
reserve
it
for
newcomers
or
in
case,
if
there
is
like
spare
time,
should
we.
A
Solve
those
issues
by
I,
I
think,
if
you're,
if
you
are
welcome
to
work
on
a
good
first
issue,
absolutely
so,
if
you
feel
like
working
on
it,
you
should
do
it,
but
those
are.
Those
are
excellent
choices
of
things
that
we
want
to
get
done
and
we
would
love
to
be
able
to
tell
people
that
we're
making
more
progress
on
terminology
updates.
A
So
absolutely
yes,
if
you're,
if
you've
got
a
few
minutes,
I
think
they're
relatively
simple,
particularly
for
the
two
of
you,
where
you
already
have
lots
of
experience
working
with
the
jenkins.io
site,
you'll
you'll
find
them
very
quickly
and
yes
change.
This
not
change
this
yes
change
this
and
then
you
submit
the
pull
request.
C
It's
important
to
do
this
move
because
you
can
earn
a
t-shirt
or
plus
a3
new
3
zone.
Word.