►
From YouTube: 2023 07 07 Docs Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
it's
the
7th
of
July
2023.
This
is
documentation
office
hours
for
the
Jenkins
project,
today's
topics,
Google
summer
of
code,
open
pull,
requests
and
a
forewarning
that
I'm
not
going
to
be.
This
meeting
won't
happen
next
week
or
the
following
week.
Any
other
topics
you
want
to
put
on
the
list:
osrutosh.
B
A
A
A
A
A
All
right,
so,
let's
shall
we
spend
some
time
focused,
then,
on
on
that
Docker
quick,
start
work
that
you
were
doing
I
had
thought
you
were
out,
so
Bruno
had
done.
Two
pull
requests
that
he
mentioned
and
I
had
done.
Some
experimenting
you
want
to
do
you
want
to
do
you
have
some
any
questions
about
my
experiments
or
any
things
that
you
would
like
to
do
specifically.
C
So,
for
the
past
two
three
days,
I
was
mostly
focused
on
the
midterm,
so
I
didn't
read:
read
all
the
issues
in
detail
that
Bruno
opened,
but
I
did
drag
a
video
here
right
now.
So
for
the
updating
plugins,
we
were
thinking
of
updating
them
eventually
with
update.cli
or
something
like
that,
so
the
pr
you
shared
does
this
script.
Does
all
that
places
that
update.cla.
A
So
know
what
that
screw,
that
script
is
how
I
manage
them
personally,
so
update
CLI
would
also
be
fine.
Update
CLI
for
me
is
more
complicated
because,
when
I
run
that
script,
when
the
script
does
the
all
the
work
of
update
CLI
for
me
without
without
having
to
try
to
teach
update
CLI
how
to
understand
Jenkins
versions,
so
I
would
I
would
guide
you
probably
for
plug-in
updates
at
least
away
from
update
CLI,
because
update
CLI
never
will
never
understand.
A
Let's
see
how
do
I
describe
it.
The
Jenkins
plug-in
installation
manager
understands
Jenkins
versions
and
dependencies,
whereas
update
CLI
does
not.
A
So
that's
when
I
can
discuss
it
with
Bruno
separately.
To
be
sure,
he
understands
why
I
think
update
CLI
is
probably
not
a
not
a
good
choice
in
this
case.
A
A
A
A
So
what
I'd
suggest
is
you
could
take
that
pull
request
as
is
and
just
merge
it
because
it
won't
do
any
harm
to
you,
the
to
the
environment
and
then
later
you
can
decide
what
you
want
to
do
with
in
terms
of
plug-in
updates.
All
this
is
doing
is
updating
the
versions
of
the
plug-in.
Oh
whoops.
Now
what
okay
sorry
I
made
a
mistake:
I
thought
I
was
current
and
obviously
I've
done
damage
to
a
file.
So
this
this
pull
request
needs
to
be
corrected.
Let's
make
a
note
on
that
request.
A
A
B
C
I
I,
don't
I,
haven't
used
a
GitHub
CLI
that
much
so
I'm
also
learning.
A
D
A
D
A
C
C
A
Okay
and
my
mistake
is
repaired
now
ashutosh
one
of
the
things
when
you
merge
this,
you
would
do
me
a
favor
if,
instead,
if,
if
you're
willing
to
merge
it,
you
do
me
a
favor
if
you
would
squash,
merge
it
so
on
your
user
interface,
what
you'll
see
in
this
section
here
is
an
option
to
do.
Let's
see,
let's
open
up
an
example
and
show
you
one:
let's
look
at
jenkins.io.
A
A
A
It
should
just
be
the
plugins
text
file
which
it
is
good.
Okay,
very
good,
so
now
go
back
to
the
conversation
and
there
at
the
bottom,
in
on
the
green,
merge,
pull
request
button,
there's
a
drop
down
list;
yeah
click
that
and
click
squash
and
merge.
Because
what
that
does?
Is
that
hides
my
embarrassment
and
it
keeps
your
your
commit
history
clean.
B
A
A
A
A
A
B
C
A
A
Interesting,
okay,
now
I've
got
to
think
about
why
it
didn't
detect
that
so
when
I
run
it,
when
we
look
at
this,
we'll
see
okay
I'm
going
to
bring
it
up
and
we'll
look
at
it
on
on
a
shared
screen.
So
here's
that
computer
and
I'm
going
to
open
the
Jenkins
controller
on
it
here.
It
is
so
now
I
log
in
as
the
user
admin
with
the
password
admin.
A
Okay,
so
I
I
just
misread
it.
Let's,
let's
fix
my
we.
It
is
correctly
configured
to
not
have
to
not
have
any
executors
on
the
controller
and
let's
prove
that
just
a
moment
yeah.
So
it
does
have
zero.
My
mistake:
what
I
saw
there
was
the
pipeline
doing
its
checkout
of
the
of
the
Jenkins
file,
and
that
has
to
happen
on
the
controller,
but
that's
not
actually
execution
of
the
job
so
you're
correct
this
is
this
did
run.
A
C
A
A
So
I'm,
not
it's
not
obvious
to
me
how
to
solve
that
now
from
Jenkins,
init.sh
I
think
you
could
solve
it
because
there
you
know
the
hostname,
but
the
problem
is.
We
want
to
eventually
get
away
from
jenkins.sh,
I,
think
and
shift
towards
just
using
Docker
compose
directly,
so
I
still
don't
know
quite
how
to
solve
it.
But
you
say:
you've
got
an
issue
already
tracking
it.
A
A
A
A
Oh
well,
let's,
let's
take
a
look
and
see
so
so,
let's
see
what
we
when
I,
when
I
ran
Jenkins
in
it,
let's
read
what
it
did
and
let's
see
if
we
can
make
some
guesses
okay,
so
it
ran
it
runs.
A
series
of
steps,
creates
the
SSH
keys
and
then
does
start
tutorial
right
and
start
tutorial,
says
Docker
compose.
A
C
And
we
didn't,
there
didn't,
have
permissions
to
access
the
rebuilt
jobs
without
the
root.
A
Oh
interesting,
okay,
that
may
need
some
further
further
exploring
because
in
general
we
shouldn't
have
to
do
that
because
it
should
already
be
set
that
way.
Interesting.
Okay,
so
let's
letters,
but
the
thing
that's
happening
is
right
here,
but
because
of
the
way
Docker
thinks
about
changes,
it
only
perceives
a
change
if
the
docker
file
script
changes,
not
if
the
one
of
the
files
that
the
script
is
tracking
changes.
So
this
copy
of
Jenkins
of
plugins.txt.
A
A
A
C
C
One
does
the
default
Default
job
that
is
on
the
root
directory,
so
we
didn't
change
that
one
okay,.
A
A
A
A
C
C
C
A
A
A
Now
the
security
folks
are
going
to
fret
I
suspect
about
us
using
default,
username
and
password,
but
I
assume
that's
something
we
may
have
to
work
on
later,
to
figure
out.
How
do
we?
How
do
we
show
the
the
login
password
to
the
user
when
we
started
it
with
Docker
compose
right,
because
that
that
user,
the
the
generated
password
if
we
didn't
create
the
admin
user,
would
be
in
the
docker
log?
That's
here.
C
A
So
what
what
I
hope
we
will
do
is
actually
have
you
or
I
would
prefer
you
be
the
one
who
submits
the
pull
request,
but
what
you'll
do
is
submit
a
pull
request
to
jenkins.io,
proposing
to
simplify
the
documentation
and
if,
if
that's
a
challenge
for
you
or
it
gets
in
your
way,
let
us
know
and
we'll
help
you
here
and
be
very
happy
to
help
you
do
it.
So
what
you
do
is
you
would
go
into
first
place
we
would
go,
is
to
the
docker
install
guide.
A
So,
let's,
let's
look
at
the
page
this
way,
so,
let's
go
to
the
Jenkins
documentation.
Documentation
installing
Jenkins
in
docker
and
here
at
the
bottom
of
this
page,
is
an
improve
this
page
link
and
when
you
click
the
improve
this
page
link,
it
should
take
you
to
this
file
that
gives
the
docker
installation
instructions
out.
Unfortunately,
it's
using
an
include
so
we'll
have
to
go
to
another
page
that
actually
has
the
real
instructions.
A
A
A
Now
the:
where
do
we
host
that
Repository
put
it
in
your
repository
for
now
and
ultimately,
I
suspect?
We
will
want
to
have
it
in
the
Jenkins
Dash
Docs
repositories,
because
that's
where
we
have
the
other
examples.
So
here's
where
we've
got
the
simple
Maven
app
and
we
would
just
put
one
more
here
on
the
popular
repositories
list
and
it
would
be
I,
don't
know,
Docker
compose
or
something
like
that
or
Jenkins
install
you.
You
will
will
have
to
negotiate
what
name
we
give
the
Repository.
C
We
had
Bruno
opener
issue
like
two
three
weeks
ago
about
the
plugins,
and
so
it
was
open
for
a
long
time.
That's
why.
A
C
A
C
Goodpord
also
uses
custom
URL
right.
A
A
Yeah
and
it
builds
successfully
now
so
that's
good,
but
I've
also
updated,
and
this
is
one
where
I
wanted
to
review
with
you
and
I.
Think.
If
you
and
I
review
it
here
and
we're
okay
with
it,
I
may
just
go
ahead
and
merge
it
wow.
So
the
the
best
practices
page
after
Jeffrey
Chan's
work
I've
done
some
further
revisions.
Let's
look
at
it
together
and
see
what
we
think
of
it
sounds
good.
Okay,
so
here
under
the
I
think
it's
under
using
Jenkins,
which
is
not
in
the
top
level
using
Jenkins
best
practices.
A
Okay,
so
the
way
it's
laid
out
right
now
is
first
recommendation
use
organization,
folders
and
that's
a
that's
a
used
Pipeline
with
the
maximum
optim
maximum
automation,
so
it
will
read
GitHub
or
it
will
read,
gitlab
or
bitbucket
or
Giddy
and
generate
multi-branch
jobs
for
every
repository
it
finds
that
has
a
Jenkins
file
in
it,
so
maximum
automation.
If,
if
you
can't
do
that
and
and
then
it's
got
links,
it's
got
embedded
videos
from
Darren
for
four
of
the
of
those
top
level
things
right:
GitHub,
bitbuck,
gitlab,
bitbucket
and
giddy.
A
A
Let's
see,
how
would
we
do
that?
Darren,
Pope,
multi-branch,
Pipelines,
video.
A
A
A
Oh,
oh,
this
is
cloud
BCI!
No,
no!
Don't
do
that!
Okay!
Okay!
That's!
Why
that's
why?
This
is
the
same
thing,
but
here
we've
got
three
videos:
one
on
GitHub
Ranch
source,
one
on
gitlab
multi-branch
and
one
on
bitbucket
cloud,
yep,
all
right
good,
so
so
you're,
okay,
if
I
embed
each
of
those
three
into
that
best
practices,
page
very.
C
A
And
this
one
is
a
I
only
realized
this
today,
while
thinking
about
it
that
the
maven
job
type
we've
been
recommending
for
a
very
long
time
since
ever
since
20,
what
was
it?
Well,
let's
go.
Read
it
I
think
the
original
blog
post
was
from
Stephen
Conley
in
2013,
so
10
years
ago
he
said
that
job
type
is
evil.
A
A
D
A
A
D
A
But
but
let's
let's
test
it:
let's
get
it
running
and
we'll
look
at
it
and
see:
okay,
so
PR
checkout,
okay,
just
that
one
all
right!
So
now.
D
B
D
D
Structure
of
whatever
ever
determines
the
level
of
automation
you
achieve
and
something
to
that
I.
A
Like
this,
so
it's
something
about
Jenkins
can
automatically
create,
update
and
delete
jobs
based
on.
A
Use
that
automation
structure,
your
pro
okay,
let's
structure,
your
job,
definitions,.
A
A
A
B
A
A
D
D
A
D
D
A
B
A
I
think
it
would
be
fun
to
say
you
should
reconsider
your
life
choices,
but
that's
that's
not
appropriate
right
right.
If.
A
D
D
A
D
A
D
A
A
D
D
A
A
D
A
A
A
Aspirational
that
you're
saying
oh
here,
here's
a
great
guideline,
and
but
there
are
lots
of
those
kinds
of
great
guidelines,
I'm
taking
it
out.
Yeah
yeah
get
over
it
I'm,
taking
it
out.
Okay,
now,
okay,
let's
see,
but
it
was
this
one
was
show
failures
to
the
right.
People
really
belongs
under
report,
build
results.
It.
A
A
Prevent
okay
prevent
resource
Collision
in
parallel
jobs,
for
me
is
maybe
this
one
is:
oh,
oh
what
about
this?
What
if
we
had
a
section
that
was
dedicated
to
controller
management?
So,
let's
put
it
this
way:
controller
management,
right,
uh-huh
or
no
I
I've
been
phrasing
them
as
verbs
start
with
manage
your
controller
yeah
or
manage
the
controller.
A
A
D
D
A
Yeah
well,
the
Okay
so
well,
I
I'm,
not
sure
I'm,
I'm
entirely
sold
yet,
but
I
think
I
think
this
is.
This
is
getting
better
and
I
really
do
have
to
stop.
A
Well,
and
and
well
enough
that
I
think
I
can
make
more
progress
on
it.
Remember
no
meeting
next
week
no
meeting
the
following.