►
From YouTube: Docs SIG 2020 11 02
Description
Jenkins documentation special interest group with demo of Jenkins 2.264 transition from table based page layout to div based page layout
A
A
A
A
A
A
A
C
A
A
Yeah
so
excellent
excellent
result.
We
do
need
a
blog
post.
That
was
an
item
here
on
hacktoberfest
results,
but
in
order
to
get
that
we
need
the
data
to
highlight
it.
I
like
it
done
a
bunch
of
work
on
the
data
to
assure
that
it's
accurate
just
need
some
time
to
go,
collect
it
and
highlight.
A
B
There
is
some
kind
of
evidence,
for
example,
to
retrospective
just
to
map
the
learning
things
during
the
event
to
use
the
next
one
like
the,
for
example,
the
the
guy
with
help
us
with
another
way
to
use
v
host
file,
how
to
handle
it
to
issues
pr
or
something
like
that
to
make
some
records
to
the
next
members.
B
In
next
events,
too,
all
the
blog,
the
blog
post,
will
embrace
everything.
A
C
A
C
A
C
B
Well,
in
this
case,
we
can
decide,
for
example,
just
close
every
10
issues
with
just
to
api
or
give
or
let
them
to
their
next
members.
What
do
you
need
to
do.
A
Solve
open
redirect
resolve
open,
redirect
issues,
a
number
of
them
won't
be
resolved
trivially,
but
redirect
the
open
redirect
issues
if
we
chose
to
say
hey,
we're
going
to
look
at
these
and
each
one
that
says
redirect
so
this
one
this
one,
this
one
we
could
choose
to
do
a
single
pr
that
would
resolve
all
those
redirect
issues
in
one
one
exercise
yeah.
I
like
that.
I
think
that
actually
would
have
a
positive
of
resolving
the
easy
ones
we
we
did.
B
Let's
say
option
because
the
the
main
objective
was
the
event.
So
it's
a
good
point.
A
B
A
A
A
B
Do
you
know
how
to
use
the
new
rules?
I
I
didn't
see.
A
B
B
A
A
Now,
in
addition,
during
the
hacktoberfest
period,
I'm
actually
kind
of
proud
of
this
one
gavin
mogan
and
I
created
an
automated
test
script
that
checks
that
vhost.com
file
for
correct
contents
for
a
number
of
mistakes
that
we've
been
making
in
the
past.
C
A
A
A
A
B
A
Do
not
I've
not
seen
anything
like
that,
so
so
I'm
not
I'm
not
aware
of
anything
that
digitalocean
shares,
but
would
be
nice,
so
let
me
put
it
this
way:
better
tracking
would
be
nice,
something
like
our
access
site
from
may.
This.
A
D
Yes,
well,
first
of
all,
thank
you
very
much
mark
for
your
contribution,
because
I
noticed
that
you're.
In
the
last
week,
for
example,
you
made
several
pull
requests
very
important
requests,
but
overall,
what
I
guess
is
achieved
on
positive
side.
D
Is
that
we're
using
right
now
image
which
is
derived
from
official
docker
image,
so
we
can
trace
the
versions
that
downloads
docker
images,
which
are
mentioned,
our
jenkins
dot,
io
documentation
on
download
side,
and
we
introduced
this
contents
of
docker
file,
which
allows
basically
everybody
to
use
it
and
actually
well
also
contribute
to
different
different
images
and
well.
D
I
wanted
also
to
mention
that,
right
now
we
achieved
this
kind
of
using
of
official
jenkins
docker
image,
both
on
installation
part
of
our
documentation
and
in
the
tutorial
part
of
our
documentation
and
tutorial
part
right
now
is
kind
of
also
expanding.
There
are
four
chapters
of
tutorial
part
and
well.
I
checked,
for
instance,
last
friday
and
during
the
weekend
tutorial
part
on
our
documentation,
not
only
simple
java,
but
something
else
and
it
works,
but
today
we
modify
it
a
little
bit.
D
Well,
I
noticed
that
we
made
some
modifications
and
I
can
test
it.
I'm
pretty
sure
tutorial
part
will
work,
but
in
installation,
but
we
removed
well
some
of
the
volume
mapping
parameters
from
installing,
for
instance
before
I'm
mentioning
this,
because
my
intention,
for
today
at
least,
was
to
think
tutorial
part
and
installation
part,
but
right
now
they
are
different.
I,
if
you
go
a
little
bit
further
lower
on
your
screen.
D
Yes,
you
can
see
that
it
is
in
install
part
before
we're
using
my
jenkins
blue
ocean
dot,
one
one
we
removed
our
mapping
for
the
home
directory,
which
is
present
in
tutorial
part
and
the
presence
in
internal
part
explained
by
the
necessity
of
using
home
in
sum
of
tutorials,
because
in
some
tutorials
we
are
not
using
github
url.
We
are
using
local
directory
in
the
image
and
we
mentioned
home
in
installation
part
home
mapping,
but
it
was
removed
over
this
weekend.
A
So
well,
and
that
was
for
me
at
least
that
was
intentional,
so
so
I
didn't,
I
thought
we
shouldn't
mention
it
are
you
thinking
we
should
mention,
use
the
home
home
mapping
even
for
install
see.
For
me,
I
thought
this
is
this?
No,
let's
go
get
all
the
way
down
this.
Where
is
it
the
one
that
maps?
Oh?
This
is
installing
sorry
installing
we
need
tutorial,
sorry
more
tutorials,
so
this
is,
let's
use
the
node.js
example.
It's
a
good
choice
and.
A
D
Exactly
and
well,
it
is
needed
for
tutorials,
because
this
is
how
summer
tutorials
are
written
right
now
and
well.
There
is
kind
of
plus
and
minuses
for
using
this.
I
guess
well,
we
can
rewrite,
of
course
tutorials,
but
well
one
of
the
minuses.
I
can
see
that
we're
exposing
our,
for
instance
our
home
directory
of
client
machine,
but
I'm
not
sure
is
it
3d,
minus
or
not.
It
is
kind
of
security
concerns.
My
question,
though,
is
well.
Maybe
people
have
different
opinions
on
that.
D
Should
we
make
tutorial
section,
at
least
this
is
why
my
intention
are
synchronized
with
installation
part
of
the
toy
related
to
docker,
because
right
now,
since
you
mentioned,
this
line-
is
missing
from
installation
part
and
it
forces
us
in
the
current
implementation
to
use
almost
identical
files
are
in
our
documentation,
so
we're
not
really
compliant
to
dry,
don't
repeat
yourself
principle,
which
is
kind
of
best
practice
for
implementation,
so
we
can
still
use
this
almost
identical
files
or
we
can
put
this
home
mapping
again
in
installation
part,
but
I'm
not
sure
if
there
are
maybe
some
objections
from
different
team
members.
D
Maybe
it
will
be
well.
Some
security
concerns
they
may
have
or
not,
yeah
it's,
I
guess
up
to
our
team
members
to
decide,
but
this
is
what
I
noticed.
Basically
all
this
today,
while
exploring
this,
but.
D
Yeah
but
overall,
I
think
it
is
well
pretty
good
achievement
that
we
are
first
of
all
using
official
docker
image.
We
introduce
the
content
of
very
simple
docker
file,
which
allows
well
contributors
new
contributors
to
utilize
this
and
like
build
their
own
images,
the
only
thing
which
maybe
further
improvement,
we're
not
showing
how
to
contribute
to
architectural
docker
images
and
releases,
but
it
is
absolutely
different
topic
separate
topic
and
I'm
not
really
sure
if
we
need
to
do
this
if
it
is
worth
doing
and
so
on
yeah.
D
D
Also,
maybe
there
will
be
some
feedback
from
that
communication
as
well,
but,
overall,
I
think
it
is
like
positive
thing,
I'm
not
sure
what
what
everybody
thinks
about
this,
but
this
is
my
question.
C
I
have
a
dumb
question
here,
so
this
gets
me
if
I'm
a
first
time,
jenkins
user
and
I'm
just
fooling
around
on
my
own.
What?
If
then
I
want
to
go
in
on
monday
after
my
successful
weekend-
and
I
want
to
set
this
up
for
my
company-
I
don't
want
this
to
be
under
my
home
directory.
Probably
right
it
needs
to
be
under
is.
C
A
Was
that
that
installing
is
there
ready
for
production
and
tutorial
is
disposable,
and
so
I
thought
that
that
was
why
we
would
justify
having
this
difference.
But
I
still
think
that
the
principle
that
vlad's,
alluding
to
the
don't
repeat
yourself
principle,
is
a
good
one
and
we
ought
to
see
if
we
could
find
a
way
to
have
a
single
source
file.
A
That
conditionally
has
this
volume
magic
in
it
when
it's
in
tutorial
context
and
doesn't
have
that
that
volume
magic
when
it's
in
the
install
context
right-
and
I
think,
we've
done
it
before
with
ascii
with
with
ascii
doc.
I
believe
I
think,
there's
a
way
to
do
that,
with
with
variable
definitions
that
we
put
at
the
top
of
files
to
say
hey
when
we
in
import
this
file
in
this
location
define
the
variable
to
be
the
empty
string
when
we
do
import
it
in
this
location.
Define
it
to
be
this
non-empty
string.
D
I
would
be
glad
to
look
into
this
like
with
like
more
details
and
figure
out
how
to
do
this,
but
yeah
my
straightforward
attempts
to
synchronize,
I
even
created
like
branch
trying
to
like
make
it
more
maintainable,
the
entire
declination
content
and
so
eliminate
this
repeating
files.
And
after
that,
I
I
found
out
well
they're,
not
identical
exactly
because
like
during
the
before
this
weekend,
they
were
almost
identical
like
well.
Some
minor
changes,
not
in
the
code,
but
in
just
the
wording,
which
of
course
is
not
very
well.
B
There
is
a
point
we
need
to
consider
about
the
dry,
it's
a
common
problem,
so
it
could
really
happens
with
us.
For
example,
if
we
point
to
another
part
of
our
documentations,
we
have
no
control
with
the
origins
chains.
B
B
A
A
I
think
in
the
case
that
vlad's
describing
here
I'm
going
to
I'm
going
to
bring
up
a
terminal
window
and
and
look
at
this
with
my
favorite
text-
editor
just
a
minute,
because
I
thought
that
they
were
pretty
close
to
each
other
already
so
vlad.
I
think
these
are
the
two
files.
You
were
alluding
to
underscore
docker
and
underscore
docker
for
tutorials
right
and
if
we
do
our
friendly
local
edif,
it
will
compare
the
two
okay.
A
So
so
your
your
desire
to
not
repeat
ourselves
echoed
with
my
desire
that
I
I
wanted
the
same
thing
and
right
now
they
are
quite
close
to
each
other
as
copies
and
the
differences
in
headed
level
heading
levels.
Can
it
be
adjusted
by
a
setting
in
the
entry
block
of
the
file
where
we
import
this,
so
that
that
difference
we
can
get
rid
of.
I
think
so.
The
only
difference
we
really
have
right
now
between
those
two
files.
Is
that
exactly
the
thing
that
you
observe
this
mount
of
the
home
directory
for
tutorials
yeah.
D
D
There
is
comment
that,
if
you
change
something
in
one
file,
just
make
sure
that
it
is
mirrored
in
the
other
file
which
is
kind
of
for
any
editor
is
kind
of
extra
effort.
A
Yes,
absolutely
wholehearted
agreement,
so,
if
you're
willing
to
investigate
the
how
you
use
variables
inside
a
doc
files,
that
would
be,
that
would
be
a
marvelous
next
step,
because
then
we
could
get
rid
of.
We
could
get
just
throw
one
of
the
files
away
and
just
use
the
single
file.
With
this,
this
conditionally
defined
variable
at
the
top
of
some
files
and
not
at
the
top
of
others.
I
like
that
that
would
be
great.
D
D
C
A
A
Certainly,
we
certainly
could
there
is
a
there
this.
This
is
not
it's
not
so
much
dangerous
from
a
security
perspective
because
they
still
have
to
authenticate
to
get
into
the
jenkins
right.
The
authentication
is
this:
they
created
the
account.
It
is
still
every
bit
as
secure
the
the
reason
that
this
is
actually
for
me
anyway.
The
reason
this
is
not
a
good
idea
in
production
is:
it
will
only
work
on
agents
that
have
access
to
that
file
system.
A
C
C
B
C
B
C
A
It
certainly
could
be
added
to
this
description
of
that
of
that
argument.
Right,
it
says
hey.
This
is
why
we're
doing
this-
and
this
number
10
here
gives
the
description.
It
says
this
is
what's
happening
and
we
could
say
in
production:
don't
do
this
put
it
in
nice,
bold
text
and
and
the
install
guide
already
doesn't
do
it
in
production.
So
that's
that
seems
healthy
as
well.
D
There
is,
there
is
another
well
approach:
we
can
change
tutorials
the
content
of
tutorials
and
use
not
local
directory,
but
github
url,
so
it
will
grab
everything
from
github
url
but
yeah.
It
depends
what
what
people
think
what
is
changing,
and
I
just
looked
at
one
tutorial-
I'm
not
sure
how
about
every
tutorial
needs
this
or
not,
but.
C
D
Yeah
and
like
since
we're
talking
about
this
specific
piece
about
docker
installation
and
tutorials,
I
noticed
that
our
windows
before
it
was
mentioned,
windows
and
linux.
The
content,
for
instance,
of
our
ram
command
right
now
it
is
different
little
bit.
So
I
will
also
look
in
this
and
just.
A
Well,
that's
another
place
where
I
don't
know
how
we
would
do
don't
repeat
yourself,
because
there
are,
there
are
mandatory
variations,
but
it's
a
good
thing
to
check
thanks
for
doing
it,
because,
for
instance,
this
character
on
the
end
of
the
line,
that's
different
on
windows
than
it
is
on,
but
the
rest
of
it
should
be
the
same
shouldn't.
It.
D
Right-
and
I
think
it
was
part
of
installation
guide
where
we
have
like
a
little
bit
different
content
for
windows,
not
specifically
on
this
on
this,
like
special
symbol
but
yeah.
I
think
it
is
yeah.
C
There
is
it's
also
nice
to
have
something
simple:
docker
itself
is
complicated
enough
and
you
don't
want
to
put
up
too
many
mental
blockades
to
somebody
just
trying
to
get
started.
So
that's
always
the
thing
too,
but
then
you
also
don't
want
to
set
them
up
to
shoot
themselves
in
the
foot
when
they
try
to
translate
this.
So
there's
the
challenge.
D
Yeah
and
well,
there
are
many
different
ways
of
to
motivate
new
contributors
to
contribute
to
the
jenkins
project
and
one
of
the
ways
I
explored
during
last
week,
for
instance,
as
I
mentioned,
is
using
something
like
category
tutorials,
where
they
can
press
buttons
and
everything
will
happen,
and
I
like
put
together
some
simplest
way,
how
to
run
jenkins
and
put
it
on
cataconda.com
and
well.
It
worked
so
it
can
be
gently
started,
they
can
deploy
and
they
can
easily
late
in
two
steps
see
their
universal
jenkins,
which
is
running
not
on
their
local
computer.
C
D
And
we
can
like
later
explore
this
if
needed,
of
course,
but
there
are
so
many
different
ways
where
we
can
go.
A
D
No,
I
think,
just
many
issues
I
mentioned.
Maybe
there
will
be
more
issues
later
here.
A
So
there
is
still
one
open
issue
with
the
node.js
tutorial
and
if
you've
got,
if
you're
looking
at
it
and
have
time,
I
would
love
love
for
you
to
investigate.
I
could
not
decode
myself
while
I
was
working
on
it
last
week
how
to
make
this
one
work.
I
know
it's
worked
before.
I
know
it's
broken
now
and
I
don't
know
what
port
mapping
we
need
or
what
other
thing
we
need
to
allow
us
to
to
use
that
tutorial
it.
It's
unique
in
that
it.
The
tutorial,
has
a
running
process
that
the
user
should
connect.
A
A
A
Okay,
so
let's
vlad
is
that,
okay
with
you
meg,
okay
with
you,
if
we
do
demo-
yes,
yes,
okay,
so
so
here's
what
we've
got-
and
this
is
let's
drag
this
one
in
and
we're
going
to
go
to.
A
And
one
of
the
the
nice
changes
here
is
that,
instead
of
using
tables
to
do
system
configuration
we're
using
html
divs,
they
say
well.
Why
would
that
matter
to
anybody?
Well
watch
what
happens
so,
I'm
going
to
click
configure
system
and
as
always,
this
is
a
large
system.
It'll
take
a
little
bit
of
time
to
open,
while
it's
opening
I'm
going
to
open
this
in
a
new
tab
and
we'll
look
at
some
other
examples.
A
Prior
so
notice
the
layout
the
number
of
executors
line
here
spans
the
full
width
and
they
are
vertically
aligned
with
each
other.
A
No
and
now,
if,
if
something
indentation
wise
happens,
it
does
it
in
with
these
dashed
lines
down
the
edge
to
hint
to
you,
what's
what's
being
placed
below
that,
so,
let's,
let's
compare
it
with
the
the
old
system
notice
that
restrict
project
naming.
Has
this
large
step
over
to
the
right
now?
If
I,
if
I
make
this
window
narrow,
the
user
interface
becomes
fundamentally
unusable
with
the
old
code,
I
have
to
scroll
left
and
right
to
do
anything
with
the
new
code.
A
I
think
I
think
that
is
a
lovely.
That
is
a
lovely
thought.
You
are
way
ahead
of
what
I
was
thinking,
but
that's
a
great
thought.
Yes,
android
app,
yes,
the
ui
has
been
adapted
now
so
that
I
can
actually
do
work
in
a
narrower
screen
without
having
to
do
enormous
screen
adjustments
and-
and
it's
it's
quite
a
treat
now.
The
challenge
is:
this
is
a
major
major
change.
A
If
I
remember
correctly,
this
one
needs:
no,
maybe
that
one
still
that
there
are
some
of
the
github
plugins,
for
instance,
that
don't
yet
have
all
the
fixes
that
they
need
for
this,
and
so
there's
more
to
be
done.
Oh
yeah,
here
we
go.
We
see
this
one
right
here.
That
shows
us
hey,
that's
not
quite
showing
me
what
I
need
to
see
so.
D
A
So
what
you
see
this
cloud
62
that
says
lots
of
people
have
found
issues
related
to
tables
to
divs
and
we're
seeing
those
as
bug
reports
here
that
come
in.
We
knew
this
was
going
to
happen.
It's
intentional
that
we
would
do
it
at
this
release,
because
the
next
lts
is
that
will
include
these
changes
is
almost
six
months
away,
and
we
like
that.
That
gives
us
lots
of
time
to
test
and
verify
this
in
the
weeklies
before
it
becomes
visible
to
users
of
the
long-term
support
release.
A
D
A
It's
it's
certainly
most
visible
in
configuration,
but
it
it
touches
anywhere
that
uses
uses
tables
as
a
way
to
do
layout
of
a
page.
So,
for
example,
I
can
show
you
one.
That
is
an
example
I
think
of
something:
that's
not
that's
in
a
job
and
still
oh
wait,
except
not
this
one.
Sorry,
I've
got
to
have
some
job
actually
run.
So
let's
cancel
the
shutdown
and
we'll
let
some
jobs
actually
run.
A
A
A
And
what's
going
to
happen,
is
it
will
after
the
first
run,
is
complete?
When
I
look
in
the
history
here
in
the
job
history,
there
will
be
a
a
check
box
or
a
pic
that
would
let
me
tag
the
build
and
that
tagging
of
the
build
used
used
to
use
tables
to
do
its
ui
layout
and
because
it
used
tables
to
do
its
ui
layout.
A
So
let's
look
at
that
now
it
would
have
been
broken.
So
this
see
this
thing
over
here
that
says
no
tags
notice.
The
look
of
this
thing
with
that
ick,
that's
a
that's
a
table,
that's
a
table
layout
problem
and
it's
those
kinds
of
things
that
will
be
visible.
D
A
You
so
yeah
now
I
think
I
think
the
the
challenge
there
is.
This
does
also
touch
our
screenshots
if
we
use
this
an
image
to
show
someone
how
the
jenkins
ui
looks
that
this
will
change
that
image
and
by
changing
that
image,
we've
got
to
eventually
get
to
the
point
of
updating
those
pictures.
A
C
B
It's
not
so
catastrophic,
because
the
name
of
field
is
keep
the
same,
so
the
people
just
realize
that
oh,
it's
split
that
on
the
middle
and
now
it's
line
by
line
right.
Maybe
in
fact
it's
not
so
high.
A
Well,
and-
and
that's
that's
a
good
observation,
so
there
are
still
there's
still
ui
work
to
do,
adapt
plug-ins
to
the
change
and
it's
lower
impact
than
a
complete
ui
rewrite.
So,
for
instance,
it's
not
nearly
as
dramatic
as
blue
ocean
was
when
blue
ocean
basically
abandoned
all
plug-ins
and
you
you
couldn't
figure
out
how
to
hook
yourself
in
so
it's
much
much
closer
to
the
jenkins
plug-in
model.
C
A
Right
yeah,
so
so
I
guess
you're
correct
in
observing
that
there
are
certainly
many
other
ui
changes
I
for
me
this
was
a
nice
improvement,
not
so
much
a
major
rewrite.
It's
a
it's
really
a
very
attractive
improvement
that
we
switched
to
having
tiled
tiled
entries
here,
instead
of
one
long
list
down
vertically
down
the
screen.
Oh
absolutely,
but
if
you've
got
screenshots
right,
you're,
correct
yep,.
C
C
A
C
A
A
A
So
I
showed
you
table
to
divs
and
that
one
is
already
done
now:
we've
got
jquery
that
will
be
updated,
probably
within
the
next
three
or
four
weekly
releases.
Extreme
unfork
is
an
internal
compatibility.
Ish
risk
that
most
users
should
not
see
should
not
see
any
threat
from
it,
but
it's
it's
widespread,
and
likewise
this
a
cg
to
spring
boot
is
an
internal
compatibility
thing
and
so
for
the
next.
Probably
four
to
six
weeks,
I'm
expecting
weekly
releases
of
jenkins
will
be
less
stable
to
users
than
they've
been
in
the
past.
C
Besides,
what
about
the
jks
documentation?
The
last
time
I
looked,
the
only
thing
useful
was
in
the
readme
file
for
the
source
code
is,
but
I
assume
that
we
plan
to
it
eventually
have
actual
documentation
on
that.
C
A
C
A
C
C
A
C
A
D
A
A
Many
people
use
master
before
you
could
choose
main
or
trunk
or,
and
they
offer
several
suggestions
now
that
just
barely
arrived
in.
I
think
it
was
get
for
windows
2.29
within
the
last
month,
but
but
it
is,
it
is
arriving
so
right,
github
making
that
change
is,
I
suspect,
even
bigger,
right,
because
they've
got
a
lot
of
places.
They'll
have
to
worry
about.
C
A
And
not
even
been
discussed
yet
yeah,
I
I
don't
know,
and
I
think
it's
a
good
question
I
I
have
no
idea
right
now.
I
think
we've
got
enough
issues
with
this
one
and
this
one
master,
the
controller
enslaved
agent
that
we
are
we've
got
years
of
work
potentially
there
before
we
ever
consider
renaming
our
branches
right.