►
From YouTube: 2020 06 22 Jenkins Docs Office Hours
Description
Jenkins documentation office hours for 22 June 2020, including topics on the history of the site generator used for www.jenkins.io, the alternatives for site generation, and access to infrastructure for documentation projects.
A
B
Okay,
so
recording
has
started
welcome
to
the
jenkins
documentation
office
hours.
As
a
reminder,
we
honor
the
jenkins
contributor
covenant,
so
we,
the
fundamental
principles,
be
nice
specific
exceptions
or
concerns
are
handled
through
the
jenkins
governance
committee.
So
we
we
want
to
be
treat
each
other
well
and
with
respect
and
dignity,
so
welcome
to
office
hours.
What
topics
would
you
like
to
address?
Let
me
bring
up
the
notes
and
I
can
share
the
notes
and
then
we
will
talk
through
and
prioritize
some.
B
B
B
B
All
right,
okay,
so
two
weeks
ago
we
talked
about
the
season
of
doc
site
and
various
pieces
of
the
google
season
of
docs
process.
Are
there
topics
that
you
would
like
to
propose
for
today
and
let's
put
them
here
and
then
we'll
prioritize
them
and
decide
which
ones
we
approach?
First.
B
A
I
would
like
to
propose
to
we
speak
about
the
history
of
the
io.
For
example.
What's
important
things,
do
you
consider
to
pick
that
technology?
It's
a
huge
one,
not
modern
one.
A
I
was
studying
the
the
github
files
and
I
guess
you
are
using.
We
are
using
a
our
awesome
website
that
website
it's
correct.
A
A
A
C
Accounts
in
jenkins
infrastructure,
but
also
I
would
like
to
address
the
issue
of
getting
credentials
to
host
jenkins
instance
on
the
cloud.
B
C
C
B
D
I
was
I'm
still
looking
at
the
the
features
we
have
on
the
proposed
features
we
have
available
for
students
to
pick
us
and
I'm
still
going
through
the
jackets
codebase
be
to
understand
a
bit
of
it.
I
think
I
joined
yesterday,
so
I'm
still
not
comfortable,
I'm
still
trying
to
adjust
myself
a
bit,
so
I
I'm
ready
to
go
on
with
anything
we
are
saying.
Maybe
I
can
learn
better
before
I
start
contributing.
B
B
B
Okay,
then,
let's
go
ahead,
take
them
on
first.
One
then
was
I'd,
propose
that
we
just
go
ahead
in
the
order
that
the
questions
were
asked.
History
of
the
jenkins
I
o
site,
we'll
then
give
some
time
to
jonathan
to
review
the
feedback
analysis
site
that
he's
created
and
then
vlad
will
address
the
relationship
between
season
of
docs
and
jenkins
infrastructure
and
we'll
close
the
meeting
within
an
hour
with
a
one
minute
reminder
about
timeline.
B
So,
let's
take
on
the
history
of
the
jenkins
site.
First,
so
maybe
a
simple
a
brief
overview
of
what's
what's
behind
the
jenkins
site,
jenkins.io
is
a
static
website
right.
It's.
B
B
There
we
go.
Okay,
excuse
the
interruption,
it's
nice
of
angel
to
say
thank
you,
but
you
didn't
need
to
see
it
all
right,
so
jenkins,
dot
io
is
a
static
website.
It
is
assembled
from
multiple
sources
right
and
so
it's
its
sources
include
ascii
doc,
source
files.
B
That's
a
good
clarification
for
core
releases,
including
lts,
and.
B
Weekly,
there
are
other
data
sources
involved,
so
it
it
includes
content,
ascii,
doc,
blog
posts.
B
B
I
can
tell
you
some
of
the
stories
around
ascii
doc
versus
markdown,
so
but
awestruck
was
selected
since
then
there
have
been
other
site
generators
that
come
have
come
into
existence
like
antora
or
others,
and
those
would
would
be
potentials
for
a
consideration.
B
I
I
have
friends
that
I
consider
very,
very
smart,
who
are
deeply
deeply
impressed
by
antora
as
an
example,
so
now
awestruck
then
chosen
as
the
as
the
orchestration
framework,
etc.
Why
asciidoc
is
the
markup
language
rather
than
markdown,
and
the
fundamental
reason
is
because
markdown
is
not
a
single.
B
Specification
markdown,
is
you
choose
your
variant
and
the
variant?
The
variants
have
important
differences
between
them
and
those
important
variants
get
in
the
way
of
many
things.
So
there's
the
github
variant
years
ago,
when
github
was
not
the
sole
and
dominant
provider
of
of
git
repository
hosting.
B
B
A
A
A
B
A
B
B
B
B
A
Okay,
okay,
so
here
we
are
speaking
about
the
viewpress
style
generation
sites,
so
here
it
it's
show
it
to
you.
You
are
seeing
the.
A
A
So
we
can
see
it's
possible
use
the
search
to
find
any
content.
So,
for
example,
he
is
we
can.
We
have
the
same
features
about
permalinks
as
previous
page
next
page,
and
we
can
see
the
left
update
info
to
our
pages
and
you
can
choose
it
on
github,
too.
Okay,
it's
the
the
most
common
useful
features
to
our
dogs.
A
A
And
here
you
can
see,
for
example,
the
sidebar
with
our
page
links
and
it's
a
the
improvements.
Are
we
have
a
better
structure
of
about
our
fonts?
So
it's
nicer
to
read
about
okay,
we
have
links
so
we
can
use
these
tips
are
here.
We
can
see
anyways,
it's
almost
the
same,
but
the
principal
feature
is
about
our
search
bar.
So
here
we
can,
for
example,
look
for
style
installations.
A
A
A
C
A
Yeah,
so
so,
for
example,
we
can
build
as
a
plugin
for
well
we
structure
platform.
We
maybe
we
need
to
program
a
new
plugin
to
improve
to
offer
a
search
button
for
our
users.
So
here
we
we
have
the
price
it's
free
for
50
000
requests
per
month.
Okay,
a
lot
of
websites
used
just
by
I
I
don't
know,
tell
you
if
it's
only
free
or
not-
maybe
not!
A
I,
I
guess,
because
it's
for
example,
vue
perez
is
a
big
website,
so
maybe
they
have
a
great
paid
plan,
but
in
our
case
we
can,
for
example,
use
the
default
solutions.
That
is
only
work
with
the
topic.
So,
for
example,
here
I
will
see
my
my
resource
studio.
You
can
see
it.
A
Yeah
yeah
exactly
so
yeah,
it's
a
h2,
hbl
h2
tag,
a
2nh
ht
3,
so
we
can
work
with
search.
A
Here
it's
a
tip
that
built
in
search
only
works,
it's
a
free
feature,
but
only
maps,
the
a2
and
8g
tracks
from
headers.
So
we
cannot
have
a
so
rich
research
like
this
one,
because
this
research
is
provided
by
algolia
okay,
but
we
have
a
simple
research
that
gives
us
text
medications
in
our
mark
dao
file
or
our,
for
example.
I
can
hear,
for
example,
jenkins,
where
is
the
agendas
dashboard?
A
B
A
B
A
Okay,
yeah,
you
you
believe
it's
sidelined
with
google
season
of
docs
or
no.
I
I
think.
B
I
think
that
would
be
just
fine
within
context
of
google
season
of
docs.
It
could
also
work
well
as
a
separate
standalone
project,
but
it's
my
initial
assessment
is
it's
a
large
enough
project
that
there's
a
lot
of
work,
hiding
behind
that
transition
from
one
site
generator
to
another,
because
the
the
the
code
that
I
believe
the
customizations
we're
using
for
awestruct
are
coded
in
ruby,
so
you'd
probably
have
to
develop
plugins
in
whatever
languages
is
used
by
the
new
generator
and
before
before
you
can
get
sign
off
that
hey!
B
Yes,
we're
going
to
do
that.
We
would
want
to
be
sure
that
we
reviewed
with
a
number
of
key
players
to
be
sure
that
they
they
said
yes,
a
transition
to
this
other
site
generator
would
need
to
have
these
capabilities
and
they
would
likely
tell
us
hey:
we've
got
to.
We
can't
lose
change
logs.
We
can't
lose
pipeline
documentation.
We
can't
lose
various
features
of
the
of
the
existing
site,
the
blogs
and
we
have
to.
We
have
to
retain
the
anchor
tags.
We
have
to
retain
the
anchor
identifiers
and
the
page
locations.
B
A
B
A
Just
a
moment
so,
for
example,
it's
about
the
complexity
of
our
dots.
So
here
we
can
see
our
original
started
guide
tour,
and
here
I
I
teaching
our
users
how
to
use
jinx
at
the
first
time.
Okay,
you
you
are,
you
are
seeing
my
my
screen,
yes,
okay!
So,
for
example,
here
it's
a
feedback
request
from
our
users
to
get
more
images
or
more
samples
about
the
things
that
are
telling
to
them.
A
So
it's
a
very
generic
thing
just
to
say,
follow
the
instructions
to
complete
installations,
and
it's
a
point
to
thinking
about
and
the
next
page
we
have
a
a
storytelling
here
about
the
pipeline.
Here
we
can
see
some
samples
and
steps
about
how
to
do
and
the
quick
start
samples
we
give
to
them
some
complex
samples.
So,
for
example,
I
I
I
like
to
imagine
the
first
time
in
contact
when
I
I
write
some
about
something.
So,
for
example,
it's
the
fifth
time.
A
First
time
the
users
are
seeing
jenkins
and
try
it
so
in
the
first
sample
we
give
to
them
a
dependence
about
docker
docker
is
a
a
hyper
technology.
It's
a
good
one.
It's
amazing!
I
love
it,
but
for
the
beginners,
it's
not
so
simple
use
docker
in
our
first
sample.
We
ask
them
to
use
it.
So
it's
not
a
good
thing
now.
I
guess,
because
we
put
more
complexity
in
the
the
learning
way.
So,
for
example,
here
at
migration,
I
have
a
local
sample.
Let's
find
them.
A
No,
I
get
up
here
so,
for
example,
I
chant
that
so
this
way
just
a
small
page,
not
so
long
ones,
so
you
can
break
it
at
the
middle
of
our
sections,
put
some
screenshots
and
put
more
tips
and,
for
example,
at
beginner
I
asked
to
so
then
I
put
a
preheat
here
and
I,
for
example,
direct
our
users
for
another
page
to
learn
how
get
started
with
docker.
I
not
mix
the
samples
all
together
right,
just
a
a
test,
a
simple
path
and
like.
B
A
A
I
put
the
steps
segmented
by
one
by
one,
with
sample
images
and
with
highlight
sections
to
to
user,
can
find
where,
where
to
click,
what
to
see,
and
in
here
in
our
samples,
we
put
the
most
generic
way
just
for
offer
to
users
a
winner
path.
So
just
follow
this
get
this
simple.
If
you
want
to
make
more,
for
example,
you
use
the
simple
you
can
hello
world
samples
in
our
pipeline
might
not,
but
we
not
are
showing
to
users.
B
This
okay,
now
now
this
this
all
this
example
already
highlights
one
of
the
interesting
challenges
that
that
step-by-step
tutorials
confront,
particularly
in
the
jenkins
project,
so
if
you'll
scroll
that
scroll
down
just
a
little
bit
further
a
little
bit
further,
still
so
almost
right
there
in
the
source
code
in
the
in
the
source
code
picture
that
you've
got
okay,
that
that
is
a
nice
simple
pipeline.
That's
saying
report
the
java
version
from
any
agent
yeah.
B
B
So
if
you
were
to
look
at
the
at
the
right
below
the
guided
tours,
you'll
find
a
different
approach
on
the
on
the
jenkins
site,
where
it
has
a
series
of
four
or
five
tutorials
that
use
docker
images
as
a
way
to
allow
you
to
run
the
same
demonstration
on
windows
or
on
linux.
A
B
A
Point,
but
it's
just
because
docker
is
a
a
another
technologies
technology
site
by
jenkins,
just
for,
for
example,
it's
maybe
it's
better
and
as
offered
to
them
a
windows
by
platform,
not
for
only
for
docker
samples.
It's
because
we
are,
you
see
we
are
offered
docker.
We
are
saying
first,
learn
about
docker
and
then
go
and
learn
about
jenkins.
B
And-
and
it
is
not
that's
a
good
point-
and
it's
it's
not
intended
to
be
so
agree
wholeheartedly.
So
your
suggestion
there
was
on
this
next
steps.
We
might
put
an
additional
tab
which
is
windows
and
then
in
that
they
would.
They
would
click
that
when
they
click
the
windows
tab,
it
would
say,
steps,
bat
and
echo
hello.
A
World
yeah
just
forgot
that
the
become
the
first
experience
more
frustrating.
B
B
A
B
B
Okay,
then,
let's
take
on
our
next
topic.
So
let's
go
to
one
more,
I'm
going
to
share
my
screen
and
let's
talk
through
the
topic
that
vlad
had
asked
about.
So
what's
the
relationship
between
google
season
of
docs
and
the
jenkins
infrastructure,
so
vlad
you
asked
one
of
the
questions
was
how
to
get
accounts
in
the
jenkins
infra.
C
Well,
there
is
a
wonderful
documentation
on
jenkins
dot,
io
related
to
jenkins
infrastructure,
and
it
tells
how
to
get
accounts,
but
it
doesn't
help
to
get
credentials
to
host
jenkins
instance
on
the
cloud.
So.
B
Right
and
and
in
fact,
the
jenkins
project
jenkins
project
right
now
does
not
have
separate
instances
for
developers.
B
B
B
Computers
or
their
employer
accounts
to
provide
infrastructure.
Now,
we've
got
a
good
example
of
a
case
where
that's
not
the
case
that
we
may
be
able
to
use
as
a
model.
The
jenkins
x,
google
season
of
co
of
google
summer
of
code
student
has
been
allocated
an
account
for
kubernetes
work
somehow,
and
we
could
just
give
me
the
action
and
mark
wait
to
check
with
cara
de
la.
C
Can
we
add
the
item
or
sub
item
to
this
mark
in
case?
If
we
will
follow
this,
we'll
follow
character
mark?
Should
we
use
jenkins
x
as
a
native.
B
No
yeah,
I
only
I
only
reference
jenkins
x
because
it
means
I
know
somebody
who's
figured
out
a
way
to
solve
this
class
of
problem.
We
wouldn't
use
jenkins
x
in
any
way.
In
this
case,
jenkins,
x
and
jenkins,
are
are
well.
The
simple
parallel
is:
they
are
roughly
as
related
to
one
another
as
javascript
is
related
to
java.
B
B
B
B
B
C
Well,
this
was
in
relation
to
the
next
question
because
there
is
documentation
already
on
jenkins,
but
I
or
how
to
get
accounts
in
jenkins
infra,
but
I
was
not
sure
how
it
may
help
answering
the
next
question:
how
to
get
credentials.
B
Okay,
yeah
all
right
so,
and
so
they
are,
they
are
an
account
in
jenkins,
infra
you,
it's
usually
used
for
people
who
will
maintain
jenkins
infra,
and
if
your
intention
is
not
to
maintain
jenkins
infrastructure,
then
then
all
you
would
do
is
use
your
you
know.
In
any
case,
you
use
your
your
jira
account.
B
B
B
Now,
one
idea,
if,
if
what
you
needed
was
a
jenkins
instance
on
the
cloud
and
all
you
need-
is
a
small
place
to
run
a
current
image,
I
might
be
able
to
persuade
meg
who's
with
us
to
see
if
we
could
get
a
training
instance
instance
from
cloudbees.
B
It's
one
of
the
things
is
that
cloudbees
as
a
company
provides
training
to
its
customers
and
sometimes
they've
been
willing
to
lend
us
lend
the
community
or
one
or
two
users
access
to
a
training
instance
that
they
could
then
use
to
work
through
course,
materials.
However,
the
problem
with
the
training
instances
is
they
are
locked
to
a
specific
version
and
they
are
of
jenkins
and
they
are
locked.
B
They
are
limited
in
terms
of
in
your
access
to
them
right,
meaning
you
may
not
be
able
to
log
into
the
shell.
You
may
not
be
able
to
do
all
sorts
of
things
that
an
administrator
of
a
genuine
jenkins
server
may
have
to
do.
B
B
B
E
B
All
right,
so
forgive
forgive
my
side
trip
on
that
question.
I
think
the
answer
there
is
this
would
probably
for
the
purposes
that
people
who
are
here
not
be
workable,
unlikely
to
be
workable.
B
B
Now
I
guess
there
there
is.
There
is
a
possible
if
you
haven't
already
used
promotional
credits
from
one
of
the
one
or
more
of
the
the
vendors
that
are
out
there,
but
promotional
credits
are
sometimes
available
cloud
vendors,
so,
for
example,
aws
google,
microsoft.
B
B
B
I
I
suspect
they
may
also
demand
something
like
a
credit
card
number
for
purposes
of
authentication,
not
for
charging
and
as
soon
as
you
start
using
the
same
credit
card
number
over
and
over
again
from
a
different
account,
they
will,
I
suspect,
reject
you.
I
I
haven't
tried
that
I've
not
not
gone
that
way.
It.
E
B
And-
and
we
do
not
want
to
encourage
anyone
to
cheat
in
any
way-
that's
that's
actually,
quite
the
opposite.
We
are
very
grateful
to
aws
as
an
example,
because
they
have
provide
a
significant
donation
to
the
jenkins
project
to
allow
us
to
use
infrastructure
from
them.
No
way
would
we
ever
suggest
anyone
cheat
any
of
these
cloud.
Vendors.
E
B
Okay,
we're
we've
got
about
10
minutes
left
any
other
questions.
Before
my
concluding
comments
on
the
google
season
of
doc's
timeline.
B
All
right,
well
so
by
ray
of
reminder:
google
season
of
docs
is
we're
in
the
we're
in
the
prepare
your
application
phase.
Now,
let's
see
the
specific
title
proposal
phase
right
now
and
that's
your
opportunity
as
candidates
to
prepare
and
discuss.
We
have
several
several
ideas
already
proposed
and
we
encourage
all
of
you
any
of
you
to
propose
further
ideas.
I
apologize.
I
have
not
yet
reviewed
the
pending
pending
proposals.
B
So
don't
forget
july
9th.
It
would
be
sad
to
have
spent
a
lot
of
work
to
prepare
a
proposal
and
then
miss
the
due
date.
As
far
as
I
understand
they
do
not
offer
any
leniency
on
when
those
proposals
must
be
in.
If
you
don't
get
them
in
by
july.
9Th
you
don't
get
them
in
you'll
have
to
wait
for
another
year.
E
E
A
B
Right
so
that
right
right
so
during
this
week
I
will
review
proposals
that
are
already
online.
I
will
make
comments
on
the
on
the
the
google
docs
so
that
you'll
have
the
comments
there.
We
intentionally
want
those
docs
to
be
public
so
that
everybody
can
see
and
learn
together
and
and
then
we
can
discuss
them
further
next
week.
If
you
want
to
ask
questions
about
feedback,
you
can
also
ask
questions
right
inside
the
doc.
You
don't
have
to
wait
until
this
meeting.
B
A
Okay,
so
to
our
next
meeting,
for
example,
if
you
need
some
clarifications
about
some
talkers
topics
about
our
proposal,
you
are
asking
to
us
at
the
meeting
or
you
use
the
docs.
B
I'll
use
the
docs,
if
I,
if,
if
there
is
something
that
needs
clarification
in
one
of
your
proposals,
I
will
ask
right
inside
that
document.
That
way,
I'm
not
delaying
you
making
you
wait
for
this
meeting
or
anything
like
that.
We,
like
we
like
very
much
to
use
google
docs
as
a
way
to
allow
us
to
do
reviews.
Ask
each
other
questions.
Improve
things,
make
them
better.