►
From YouTube: 2020 07 13 Jenkins Docs Office Hours
Description
Jenkins documentation office hours July 13, 2020 with topics including Google Season of Docs, Docker images, and issue tracking in the Jenkins project.
B
Okay,
you
know,
I
have
just
a
I
need
some
clarification
for.
You.
I
would
like
to
have
your
opinion
about
a
PR
that
I
create
seven
days
ago,
and
it's
possible.
I
would
like
to
have
more
information
about
the
community
bridge
to
but
I
I
read
all
the
those
links
and
that
you
provide
to
us,
but
there
is
no
viable
information
to
to
members
to
proposal.
Send
their
proposal
I,
maybe
I,
think
I
didn't
find
it
no.
A
A
A
A
A
A
So
right
now
that
would
mean
we
would
draft
proposals.
They
would
go
to
probably
the
Jenkins
governing
board
for
for
review
or
to
the
mentor
team
from
google
season
of
Docs,
and
then
a
project
would
be
selected
that
person
would
be
funded
and
off
we
would
go
now.
Is
that
what
you
were
asking
Jonathan
or
as
there's
some
other
questions.
B
A
B
A
It
will
be,
it
will
be
made
very
publicly
right
so
of
a
community
bridge
project,
so
the
the
last
one
we
did
we
did
with
a
blog
post.
We
did
with
a
mailing
list
announcement.
I,
don't
I,
don't
think
that
we
would
do
a
webinar
for
this
one,
but
we
might
even
do
a
webinar.
That's
that's
a
possible
for
sure.
In
the
past,
we've
used
blog
posts
and
mailing
list
announcements.
A
D
A
So
that's
a
that's
a
very
good
question.
Let
me
show
one
example.
This
is
when
you
might
mention
to
two
others
with
whom
you
work
or
to
employers.
So
if
we
look
at
the
Jenkins
community
bridge
page,
it
is
accepting
donations
and
let's
see
where
is
it
so
you
could
pass,
for
instance,
to
an
employer.
Then
you
say
hey.
We
would
like
you
to
contribute
to
Jenkins
community
bridge
and
now
I
may
have
to
go,
find
the
correct
location
just
a
minute
while
I
go
looking,
it
is
not
there,
but
there
okay.
A
D
A
A
No,
that's
not
it
okay,
so
it
may
be
that
it's
still
in
progress.
So
let's
use
Vlad's
suggestion
and
go
to
github
and
github
and
I.
Think.
If
we
look
at
core
I
believe
it's
been
enabled
on
core:
has
it
no
I
don't
over
sponsor
there's
a
little?
Oh,
that
worked
yeah
there
we
go!
Thank
you
excellent
okay.
A
So
this
page
shows
us
that
we
could,
and
so
individuals
and
organizations
can
contribute
the
I
believe
this
three
thousand
dollar
expense
that
you
see
here
was
what
we
used
last
year
to
fund
the
Jenkins
community
pride
bridge
project
that
we
ran
last
year.
So
we
would
be
delighted
to
have
more
contributions
and
big
green
donate
button.
Thank.
A
A
D
Actually
added
this,
and
this
is
full
up
to
our
submission
of
proposals,
which
I
guess
happened
last
week
and
I
would
like
to
address
my
well
my
proposals.
I
just
wanted
to
keep
them
somewhere.
I
posted
today,
a
question
on
docker
discussion
group
and
got
response
from
Alex
that
nothing
is
developed
regarding
to
my
proposal,
and
it
was
basic
proposal-
was
about
creating
something
very
simple
which
will
allow
to
generate
set
of
docker
images
with
Jenkins
inside.
D
Something
similar
to
Mullen
archetype,
for
instance,
archetype
generated.
You
can
create
different
archetypes
up
to
15
different
solutions
predefined,
and
we
can
just
my
idea
do
something
very
similar
to
this.
The
main
goal,
from
my
point
of
view,
is
simplicity
of
this
kind
of
tool
or
plugin.
I
have
no
experience
developing
Jenkins
plugins,
so
users
can
very
easily
are
built
and
instantiate
run
docker
image,
which
will
do
something
very
specific,
and
this
Pacific's
will
be
defined
by
Jenkins
project
or
by
by
Jenkins.
D
Basically,
community
reach
and
the
user
and
user
will
need
to
choose
between
solutions
which
are
more
appropriate
to
his
goals
and
again,
there
is
like
wide
range
of
different
possible
solutions,
and
I
would
start
in
case
if
I
will
be
allowed
to
implement
this
from
simple
one
and
go
up
by
increment
complain.
Complexity,
not
vice
versa,
so
kind
of
bottom
to
up
approach
versus
top-down.
A
That,
for
instance,
run
run
an
agent
Cerreta
Jenkins,
plus
an
agent
to
build
a
maven
project,
and
we
have
a
Jenkins
plus
an
agent
know
a
node
nodejs
project
and
Jenkins
plus
agent
to
build
let's
see,
what's
the
old
Python
project,
and
so
so
you've
got
some
good
working
base
to
think
about
it
now
to
go,
were
you
considering?
I
am
assuming
you
are
not
considering
other
components
in
in
this
docker
image.
So,
for
example,
not
considering
placing
a
source
control
system
inside
this
image.
D
Probably
not
well,
it
depends
how
we
run
this
I
guess
so,
if
there
is
like
volume
will
be
mapped
to
the
source
to
them
during
instantiation
plays,
it
will
be.
This
image
will
have
access
to
the
sources,
but
yeah
you
are
just
my
main
goal
is
to
attract
new
users,
so
they
will
become
adopters
or
Jenkins,
so
we
can
increase
their
user
base.
D
D
Oh
like
rest
restful
approach,
is
better
than
simpler
than
soap.
That
is
why
it
was
adopted
by
industry.
This
kind
of
idea,
so
simplicity,
is
the
key
for
adoption
because,
like
Jenkins
is
already
complex
enough,
so
will
really
have
good
base
of
professionals
like
programmers,
computer
scientists
and
so
on
working
on
this,
but
something
like
to
popularize
it
and
make
sure
that,
like
my
ex
a
virtual
grandmother,
the
racial
granddaughter
will
be
able
fix
he
old
virtual
him.
D
D
A
It's
it's
not
only.
It
has
very
specific
problems
that
we
would
like
to
get
away
from
it.
Absolutely
yes,
so
those
tutorials
are
are
flawed
in
the
sense
that
they're
using
an
image
that
then,
if
users,
if
users
say
oh
I'll,
base
my
work
on
that
tutorial.
We
think
they've
made
a
mistake
right
rather
than
basing
themselves
on
the
blue
ocean
image.
They
should
face
themselves
on
the
production
Jenkins
image,
but
that's
that's
disconcerting
for
them.
A
D
A
The
plugins
yes
and
you
make
an
excellent
clarification,
absolutely
wholehearted
agreement
that
we
don't
want
to.
We
want
to,
in
fact
encourage
them
to
use
the
blue
ocean
plug-in
to
visualize
pipelines.
It's
an
elegant
way
to
do
it
to
do
pipeline,
editing
and
visualization
it's
very,
very
powerful,
but
using
the
blue
ocean
docker
image
is
an
anti-pattern.
It's
a
negative
because
of
the
problems
that
are
in
there
built
into
the
blue
ocean
docker
image,
yeah
good,
good
clarification.
D
D
A
A
that
one
is
a
relatively
exotic
thing:
I
hesitate
to
I
would
not
envision
us
being
able
to
tell
a
new
user
of
Jenkins.
Oh
just
use,
custom
or
packager
to
define
your
own
completely
custom.
Jenkins
instance.
That's
that's
to
me
just
too
complicated
for
them
it's.
It
is
certainly
an
excellent
technique
for
experts.
Oleg
makes
very
good
use
of
it
and
others
make
very,
very
good
use
of
it.
A
But
the
custom
build
service,
Jenkins,
custom,
Jenkins
distribution,
build
service
is
working
towards
what
could
be
an
end
user,
acceptable
and
then
user
usable
ready
to
go.
You
define
the
configuration
you
want
or
pick
from
a
menu
and
conceivably.
We
could
have
have
something
it
says.
Oh
you
want
to
run
this
tutorial.
Fine,
go
to
the
custom,
build
this
Jenkins
distribution,
build
service
and
choose
this
distribution
and.
D
A
C
B
Okay,
now,
okay,
so
some
days
ago
or
like
Rick,
recommended
not
to
use
raw
HB,
h,
PL
and
right
documentation.
But
let's
pick
this
PR
in
the
death
one
other
I
I
use
the
red
imported
booth
track
to
create
this
effect
of
todo.
Visualization
are
your
scene
on
the
gift
and
you
hit
the
bottle
that
show
you
the
help
or
not.
You
choose
fear,
not
the
image
so
ask
doc
does
not
offer
to
us
for
a
feature
to
do
this,
so
you
you
will
prefer
to
keep
this
button
withdrawal
each
meals
or
you
recommend
to.
A
C
A
Would
tend
to
advise
removing
it,
but,
let's
let
me
look
at
something
different.
Let
me
show
you
a
different
one,
because
there
is
a
thing
that
does:
we've
got
something
already
that
does
a
hide
and
unhide
in
a
different
context
that
we
might
be
able
to
use
or
might
be
able
to
use
to
justify
the
technique
you're
showing
us.
So
let
me
see
if
I
can
find
it
here.
It
is
in
the
plug
in
the
pipeline
documentation.
A
A
Okay,
there's
declarative
make.
Maybe
you
know
where
it
is
I.
There
is
definitely
a
segment
where
I
can
see,
let's
see
using
doc.
Maybe
this
is
okay.
Let's
see
oh
yes,
there.
It
is
good
okay!
So
let's
the
first
question:
can
everyone
see
my
screen?
Okay?
Yes,
all
right
so
here
is
here
is
a
segment
of
the
document
that
describes
using
docker
with
pipeline,
and
we
give
the
preferred
solution.
First
in
declarative,
pipeline
declarative
has
the
benefit
that
it.
It
is
immediately
parsed
in
its
entirety.
A
So
if
there's
a
syntax
error
or
late
in
the
in
the
pipeline,
it's
detected
immediately.
Scripted
doesn't
do
that,
but
some
people
have
found
that
they
they
have
to
have
scripted,
and
so
we
have
this
here
which
says
toggle
scripted
pipeline,
and
it
presents
this
other
thing
now.
I
I
haven't
looked
in
detail
Jonathan
to
see
how
it
does
this,
but
I'm
pretty
sure
it
does
it
without
without
doing
too
much
JavaScript
without
doing
I
suspect
any
JavaScript
magic,
because
the
people
who
worked
on
this
particular
thing
I,
don't
think
we're
JavaScript
programmers,
yeah.
B
A
A
At
least
compare
it
I'm,
not
sure
I'm,
it
I'm
not
I'm,
not
confident
yet
to
say
who
you
should
replace
it.
But
if
you
compare
what
this
technique
is
for
me,
this
technique
is
helpful
because
yet,
in
this
case,
does
I
think
what
you
were
trying
to
do,
which
is
initially
the
user
benefits
more
by
seeing
the
list
of
steps
without
seeing
any
tails
for
each
step.
Right.
B
More
yeah,
it's
the
same
idea
that
Vlad
tells
to
us
it's
to
keep
sync.
Oh
it's
not
so
we're
not
is
visualization
with
su
in
the
first
contact
that
you
have
a
lot
of
information,
you
get
lost.
Why?
We
are
you
reading
on
study,
so
I
will
study
this
link
that
you
show
to
us
and
if
you
work
where
I
will
replace
you
great.
A
B
B
A
A
I
know
that
Daniel
Beck
has
done
it.
I
know
that
I
will
be
using
some
Ruby
code
to
do
a
thing
that
I
need
to
do
for
the
Jenkins
infrastructure
page,
so
I'm
going
to
be
getting
into
it.
But
if
you're
asking
somebody
who
has
Ruby
skills,
that
is
definitely
not.
We
I
am
willing
to
experiment
and
learn,
but
I
certainly
know
people
who
have
written
code
in
the
in
the
Ruby
here,
like
Daniel
back
Oleg
has
as
well
as
your
benek
connection.
He
has
based
in
I
believe
he's
in.
B
A
B
B
A
B
B
D
D
A
A
B
B
A
A
He
did
have
a
surprise.
We
were
surprised
when
google
season
of
docs
sent
the
proposals
to
the
jenkins
docs
mailing
list.
That
was
not
where
we
expected
them
to
be
sent.
We
spent
expected
them
to
be
sent
to
the
organization
administrators,
but
we
saw
them
Oleg
detected
them
and
has
has
been
able
to
get
what
he
needed
out
of
them.
So
we
think
we
have
all
the
right
information
so.
A
D
D
Is
there
kind
of
standard
approach
to
doing
this,
or
maybe
there
is
some
tool
to
generate
these
plugins
cortex
the
file?
All
we
need
to
base
from
the
previous
configuration
of
running
Jenkins
application
export
this
file,
something
like
this.
What
is
the
best
approach
for
doing
this,
because
general
idea
is
very
attractive,
very
interesting
to
include
this,
and
this
docker
image
will
be
configured
with
all
these
plugins,
but
how
we
generate
or
how
we
create
this.
This
text
file,
which
is
very
simple
kind
of
in
format,
main
value
pairs,
but
but
about
the
contents,
how?
A
A
A
A
D
A
D
A
I've
used
another
technique,
but
this
one
is
not
not
viewed
highly
favorably
by
others,
so
I
wouldn't
claim
that
anyone
else
should
do
it.
I
have
a
git
repository
that
has
large
file
support,
enabled
and
I
just
checked
the
plugins
into
that
get
large
that
get
LFS
repository,
but
that
requires
that
you
paid
github
extra
money
each
month
in
order
to
be
allowed
to
use
LFS.
It's
just
so
so
convenient
for
me
that
it
was.
It
was
easily
worth
a
few
dollars
a
month
that
github
charges
to
use
large
files.
A
D
A
D
D
A
A
And
if
the
issues
issues
tab
is
enabled,
then
it's
tracking
issues
in
github.
So
the
example-
let's
see,
let's,
let's
take
two
different
examples:
there's
the
first,
which
is
the
Jenkins,
get
plugin
so
plug-in.
I
maintain
you'll,
look
here
and
it
does
looks
it
does
not
have
getting
used
to
my
new
Mouse
so
across
the
top
here
code,
pull
requests,
actions,
projects,
but
no
issues
tab.
A
D
A
Now
now
you
back
to
your
question
Vlad.
How
can
I
tell
and
the
answer
is
check
the
github
source
code
repository
if
it
doesn't
have
an
issues.
Tab
they're,
certainly
not
using
github
issues
to
track
if
it
does
have
an
issues
tab,
it's
still
safe
to
check.
Is
there
a
JIRA
project
where
they
are
tracking
those
issues
and,
let's
see
I'm,
not
sure
I'll
bother
opening
JIRA
for
you,
but
it's
the
JIRA
issues
are
definitely
there.
A
We
have,
we
have
I
would
say
we
have
components
which
are
in
transition
and
components
in
transition
typically
are
going
from
JIRA
towards
github
issues.
One
of
those
components
in
transitions
is
the
Jenkins
dot
IO
site.
We
initially
tracked
its
issues
in
JIRA
and
we
found
it
was
much
easier
for
users
and
much
easier
for
contributors
if
we
switch
to
that
site
to
use
github
issues.
But
that
means
there
are
still
some
some
old
issues
in
JIRA
that
we
are
slowly
closing
out.
B
A
A
So
here
is
there's
a
if
we
look
at
here's
my
example.
This
is
the
subversion
plugin.
So
if
you
were
a
subversion
user,
you
might
see
that
you
would
see
this.
This
indicator,
which
says
hey
this
plug-in,
is
up
for
adoption
and
on
the
adopter
plugin
site.
It
tells
us
what
that
means,
to
adopt
a
plug-in
and
plug-in
maintainer.
X'
can
say:
hey,
I'm,
not
planning
to
maintain
this
plugin.
Therefore
they
mark
it
for
adoption
and
other
plug-in,
maintainer
x'
may
say
hey.
I
would
like
to
adopt
that
plugin.
A
So
you
follow
this
set
of
steps
right
here,
send
an
email
to
the
Jenkins
developers.
Mailing
list
say:
I
would
like
to
be
made
a
maintainer
and
in
that
in
mail
you
tell
them
which
plugin
you
want
to
adopt,
pull
requests
that
show
that
you're
credible
your
github
user
ID
and
your
Jenkins
user
ID,
and
then
you
go
to
work
on
it
now.
B
A
The
assumption
is
that
you
will,
you
will
make
some
positive
impact.
Usually
the
reason
someone
adopts
a
plug-in
is
they
would
like
to
release
a
new
version
of
it
and
in
order
and
in
releasing
the
new
version
of
it,
they
want
to
make
some
changes
either.
They
want
to
update
it
to
use
the
latest
Jenkins
versions
or
they
have
some
feature
they
want
or
some
pull
request.
They
want.
There's
usually
some
motivation
that
says
I
would
like
this
and
therefore
they
adopt
the
plug-in.
So
they
can
do
it.
A
C
A
Right,
oh
yeah.
What
a
second
but
I!
Don't
gather
it's
this
right
here
right.
So
what
the
concept
of
an
abandoned
plug-in
is
not
labeled
on
the
plug-in.
It's
not
it's,
not
a
label!
You
will
see.
It
is
merely
an
observation
made
by
looking
at
the
commit
and
maintenance
history
of
the
plug-in.
So,
for
example,
actually,
let's,
let's
take
a
very
specific
example,
I
think
we
can
find
one
that
Oleg
originally
wrote
that
he
no
longer
maintains
called
the
remote
loader
plug-in.
Let's
go
look
at
it
and
it
was
released.
A
A
Planned
remote
loader
here
we
go
so
oh
no.
This
was
last
released
only
a
year
ago,
so
it's
relatively
recent,
but
there
are
other
plugins
that
I've
looked
at
very
recently
where
the
plug-in
was
last
released
a
very
long
time
ago,
and
that's
that's
where
we
would
apply
the
rules
and
say:
oh,
this
is
probably
an
abandoned,
and
so
we
need
to
follow
the
abandoned,
plug-in
adoption
rules.
B
A
All
right,
then
I'm
going
to
propose
that
we
end
our
session
four
day
today.
Thank
you.
Next
milestone
on
Google
season
of
Docs
is
July
30th
I
believe
when
the
organization
proposals
will
be
submitted
to
Google
and
then
I
believe
it's
two
weeks
after
that,
but
Google
will
announce
who's
been
accepted.