►
From YouTube: 2022 01 20 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
So
today's
agenda
items
I've
got.
We
have
news,
the
weekly
change,
log
and
weekly
release,
which
has
some
special
cases
going
on
for
it
open
prs
the
contribution
next
steps
and
improve
a
plug-in
tutorial
are
all
possible
topics.
Any
other
topics
that
we
want
to
add
to
the
list.
A
So,
in
terms
of
end
of
java
8
end
of
life,
I've
set
the
goal
to
have
the
the
jenkins
enhancement
proposal
drafted
and
ready
to
go
before
the
next
meeting
of
the
platform
sig
group,
which
is
next
friday.
A
A
And
internet
explorer
end
of
life,
we're
not
going
to
use
a
jenkins
enhancement
proposal
for
it.
We'll
just
plan
to
drop
support
from
weekly
in
the
next
two
to
three
weeks,
and
then
it
will
be.
The
removal
of
support
will
be
visible.
A
Now
the
we've
got
a
failing
test
that
is
further
delaying
the
release.
The
release
team
is
working
on.
An
infrastructure
team
is
working
on
it
now
so
jenkins,
2.331.
A
C
C
Good
excellent,
that's
great
yeah,
so
I
just
wanted
to
mention
a
couple
of
things
that
I
noticed
while
setting
it
up.
C
So
this
is
not
compulsory
but
to
be
able
to
get
the
green
git
pod
icon
that
we
saw
while
your
mac
was
presenting.
C
I
had
to
install
a
gitpod
browser
extension
to
be
able
to
do
that.
Sorry.
A
C
A
C
So
it's
not
compulsory.
So
what
the
what
the
extension
does
is
normally
for
you
to
be
able
to
access
your
workspace.
What
keyboard
does
is
that
it
adds
it
prefix
your
normal
github
url
with
a
gitpod
url.
So,
for
instance,
you
have
something
like
https,
I
think
git
sport
dot.
I
use
slash
ash
then
followed
by
the
github
url.
So
what
that
button
dot
does
is
that
it
just
does
that
for
you
and
opens
your
workspace
in
the
new
brow
browser
tab.
That's
what
it
does.
C
So
it's
not
compulsory
that
you
have
that,
but
for
ease
of
use
you
can
add
browser
extension
that
adds
that
button
for
you.
So
it
does
it
automatically.
C
I
think
there
is
another
alternative
to
adding
the
to
adding
the
browser
extension,
but
I
didn't
go
that
route
because
it
looked
much
longer
so
I
haven't
tested
that
then
another
thing
is:
if
you
want
to
run
the
jenkins
project,
you
have
to
ensure
that
your
fork
is
updated,
because
I
think
one
mistake
I
made
before
while
I
when
I
started
using
keyboard,
was
I
didn't,
pull
the
recent
changes
from
jenkins
master.
C
So
when
I
try
to
do
macron,
I
was
having
some
errors,
I
think,
probably
because
the
git
spot
file
that
wasn't
on
my
own
branch
or
my
own
fork.
So
but
after
I
pulled
the
changes
from
upstream
everything
worked
perfectly
then
the
last
thing
is
for
you
to
be
able
to
push
changes
and
pull
changes.
You
need
to
grant
gitpod
the
necessary
permissions
on
the
settings
page
for
you
to
be
able
to
push
or
pull
changes
using
your
workspace
on
github,
so
yeah.
I
think
for
now.
C
Those
are
the
three
things
I've
noticed
up
to
the
point.
I
haven't
yet
done
any
changes
or
done
any
work
or
open
the
pull
request.
So
maybe
I
might
notice
other
things.
A
A
B
A
A
C
A
C
Yeah,
okay,
so
you
have
to
do
this
for
you
to
be
able
to
push
any
changes
or
yeah
to
push
any
changes
to
your
fork.
Otherwise,
you
just
have
read
permissions.
A
A
C
Yeah
but
otherwise
it
it
was
really
great,
because
I
think
I
was
able
to
set
it
up
in
like
less
than
15
minutes.
A
D
Yes,
it
did
actually,
it
fell
faster
for
me
because
I
changed
them.
I
changed
my
internet's
plan
yesterday
after
that
encounter
I
had
during
the
last
call,
so
I
had
to
change
it
to
something
else,
so
it
was
it's
better
now,
it's
better.
A
Very
good
all
right,
so
that's
that's
because
one
of
one
of
the
worries
for
me
for
the
contributon
is
is
not
everyone.
Who's
in
the
contribution
may
have
reliable
internet
all
the
time,
but
but
it
sounds
like
web
browsing
was
comfortable
for
you
and
and
doing
development
over
the
browser
worked
well
enough,
very
good,
all
right
excellent.
Thank
you.
A
A
For
she
code
africa,
contributon
participants,
so
we've
got
a
we've,
got
a
video
series
that
includes
doing
many
operations
even
on
get
plug
on
jenkins
plugins,
not
just
on
the
jenkins
doc
site
using
git
pod,
and
so
it
uses
git
pod
in
many
other
ways
to
do
development
without
requiring
a
local
installation.
C
So
about
prs?
Okay,
this
is
about
issues
anyway
issue.
I
saw
a
good,
so
I
was
trying
to
kind
of
like
test
out.
You
know
working
and
opening
a
pr
using
keypod.
So
I
saw
an
issue
on
jenkins.ioh
that
I
wanted
to
ask
about,
because
I
wasn't
really
sure
the
full
details
of
the
issue
I
wanted
to
work
on.
It.
A
All
right-
and
so
your
question-
probably
this
one-
I'm
I'm
a
little
fearful
that
making
it
a
good
first
issue
may
have
been
misleading,
but
let's,
let's
take
a
look
at
it
together
and
do
some
quick
review
of
what
needs
to
happen
here,
yeah,
okay,
so
so
first,
this
says
that
jenkins
wiki
was
made
read
only
in
october
2019..
That
is
absolutely
correct.
It
should
probably
be
extended
to
say
that
jenkins
wiki
was,
and
I'm
going
to
open
up
the
tab
to
show
the
page.
A
B
A
We
couldn't
be
confident
that
it
was
not
somehow
damaged,
so
we
never
brought
it
back
online.
It's
now
back
as
back
as
a
static
as
static
web
pages,.
A
A
So
so
what's
happened
here
is
the
old
instructions
said
things
like
hey
run
this
wick
jenkins
wiki
exporter,
and
let
it
do
the
translation
for
you.
Well,
this
entire
step
and
its
manual
equivalent
no
longer
are
needed,
because
the
translation
of
every
plugin
wiki
page
has
been
done
and
is
now
stored
on
this.
This
github
repository.
D
A
So
so
we
can
delete
these
two
sections
completely
because
they
they
don't
make
any
sense.
We
just
grab
the
changes
from
from
this
already
translated
file.
So
let's
let's
talk
through
it.
So
then
the
conversion
of
plugin
pages
is
already
started
and
I
say
started
rather
than
finished,
because
there's
inevitably
changes
that
are
needed
in
order
to
make
it
make
it
all
the
way
to
done.
D
A
A
A
C
A
A
A
B
A
Conversion
to
be
done,
as
far
as
I
can
tell
it's,
this
markdown
file
is
ready
to
be
placed
there.
Now
you
may
find,
as
you
read
it,
that
there
are
things
that
should
be
corrected
or
you
may
find
spelling
errors.
You
may
find
places
where,
for
instance,
this
thing
should
probably
be
in
a
source
code
font.
C
Okay,
so
now
the
process
of
the
wiki
migration
would
be
okay
from
the
wiki
exporter
check.
You
know
what,
if
the
documentation
has
been
moved
or
not
right,
so
if
it
has
not,
if
it
has
not
click,
okay,
you
click
on
it.
Go
to
the
github
page
check.
If
there
is
document
there's
a
readme
file
with
the
documentation.
C
If
not,
then
you
go
to
the
repository
we
just
seen.
We
just
saw
now,
what's
what's
the
title
of
the
repository
here,
plug
in
wiki
docs
to
search
for
that
plugin
once
you
find
it,
you
copy
the
documentation
in
the
readme
dots,
a
readme
file
there
and
the
images
and
move
it
to
the
plugin
to
the
plugin
repository.
A
A
B
A
But
more
ui
changes
are
happening
in
in
march
2022
lts
release
so
worrying
too
much
about
this
is
maybe
premature
just
be
aware
if
the,
if
the
images
have
words
like
hudson
in
them.
Okay,
that's
a
really.
B
A
A
A
A
A
B
A
A
B
B
Unmute,
you
can
hear
me
better.
That
way.
Do
we
want
to
do
these,
or
do
we
want
to
move
on
to
chico
africa
or
planning,
while
everybody's
here.
A
A
In
right,
no,
I
think
actually
well,
let's,
let's
test
it,
would
you
be
okay
if
we
spend
a
few
minutes
on
chico
africa
contribute
on
sure,
okay,
so
here's
here's.
We
had
a
session
on
monday
and
talked
about
possible
ideas
for
projects,
so
inclusive
naming
correcting
the
words
master
slave
whitelist
blacklist
that
one
you
had
already
confirmed
and
pipeline
help.
We
tried
last
year
and
not
a
big
deal
test
automation.
I
think
I
had
discussed
that
with
you
and
you
thought
that
would
be
okay,
yeah.
A
C
B
Okay,
do
you
want
one,
that's
a
master.
Do
you
want
one,
that's
cleaner,
oh.
B
Okay,
go
to
open
pr's,
then
you'll.
A
B
You
for
being
here
all
right.
Thank
you.
Bye,
bye,
wonderful,
48
32,
I
believe
clarify
use
of
maven
bomb.
A
A
B
Do
not,
and
it's
sort
of
I'd
like
to
see
what
you
think
of
it,
because
I
didn't
that
wasn't
one
that
was
easy
for
me
to
action
on.
Okay,.
A
A
Okay,
good
all
right,
so
plugins
frequently
have
dependencies
on
specific
versions
of
libraries
and
other
plugins,
each
of
which
is
versioned
independently.
Each
plugin
may
have
dependencies
of
its
own
and
different
versions
of
different
libraries
and
plugins
may
not
be
compatible
with
each
other.
Moreover,
the
dependencies
can
change
with
each
release,
so
managing
these
dependencies
manually
can
be
difficult
and
time
consuming.
A
Okay,
I
think
that's
an
adequate
statement.
Okay,
so
now
here
we
go
jenkins
core
bomb
since
jenkins.
Some,
since
some
version
jenkins
corps,
provides
a
bill
of
materials
that
centrally
okay.
So
so
I
wouldn't
actually
right.
B
On
just
a
minute,
because
what
I
looked
at
before
it
was
dependency
management,
and
then
we
had
a
subsection
that
was
called
the
bomb,
and
that
was
where
you
got
the
error
message.
It
was
you
know,
reading
it.
It
took
me
trying
to
figure
out.
What's
going
on,
so
I
tried
to
restructure
it
a
little
bit
and
added
some
information
and.
A
A
B
A
Well,
and-
and
I
and
and
I
like
so
what
tim
noted
is-
there
are
two
two
forms:
there's
the
plug-in
bill
of
materials
and
the
core
bill
of
materials
and
they're
different
things
right,
and
so
so
we
need
both
of
them
here
so
is.
This
is
what
was
described
as
the
core
bill
of
materials
before
right,
and
we
could.
We
could
expand
the
this
this,
but
rather
than
calling
it
apache
maven.
I
think
I
would
stay
with
jenkins
core
bill
of
materials.
B
A
B
A
A
B
Okay
and
now
does
everybody
just
know
what
that
is?
It's
not.
I
wanted
to
link
to
something
and
I
couldn't
figure
out
what
it
could
link
to.
B
A
Update
it
here,
it
is
so
yes,
we've
got
it
very
good.
All
right
and
we've
got
a
page
in
our
world
that
talks
about
how
to
do
this,
so
this
is.
This
is
really
good,
because
it
also
has
more
explanation
on
what
happens
here
with
with
require
upper
bounds
and
transitive
dependencies,
and
things
like
that.
So
so
this
is
yes,
excellent,
okay,
so
what
we've
got
is.
A
Yes,
yes,
absolutely
let's
go
in
and
do
let's
go
ahead
and
do
some
well
do
you?
Do
you
mind
if
I,
if
I
make
my
life
easier
and
craft
them
in
my
text,
editor
not
at
all
okay,
so
I'm
gonna
make
the
text
bigger,
so
it's
readable,
but
it's
just
easier
for
me
when
we're
doing
these
sort
of
sort
of
larger
edits.
If
I
okay,
is
that
text
readable,
very
readable,
yes,
okay,
great
all
right
so.
A
A
That's
what
I
was
going
to
do
assuming
you're
okay
with
that
absolutely
okay.
So
what
I
do
is
I
check
out
that
branch
get
merge,
master,
okay,
all
right
so
we're
up
to
date
with
master
and
that
noise
tells
me
that
you
need
to
do
a
you
need
to
remember
next
time
you
interact
with
your
fork
on
github.
B
A
A
B
A
B
B
A
B
A
B
Okay,
so
that's
under
maven,
so
then
that
okay,
I've
still
got
the
structure
wrong,
so
this
should
have
I
before
the
bomb.
I
think
to
me.
It
reads
better
if
we
say
if
you
in
maven,
if
you
don't,
do
it
right,
you're
going
to
get
these
errors,
for
example,
here's
your
and
then
in
that
same
section
goes
here
how
you
and
then
say
we
have
this
bomb
that
will
fix
it
and
here's
how
you
use
it.
A
Okay,
so
so,
rather
than
giving
an
intro
first
of
what
are
the
two
forms
of
bill
of
materials?
And
here
are
the
errors
you're
suggesting,
let's
start
with
hey,
if,
if
here's
a
as
the
first
thing
upper
bounds,
dependency,
message
and
then
talk
about-
and
this
is
how
you
resolve
it-
first-
by
using
current
version
of
the
the
core
bomb
and
second
by
using
the
bill
of
materials
from
or
the
the
bomb
from,
the
plug-in
bomb
to
simplify
your
dependency
management.
A
Yeah,
except
that's
a
good
question-
I
mean
you're
thinking.
Should
it
be
maven
dependency
management
that
I
don't
know
because
I
I
think
dependencies
are
managed
in
gradle
and
it
specifies
dependencies.
It
just
doesn't
have
the
same
tooling
available.
If
I
remember
correctly
to
warn
people
about
it
and
in
fact
it's
largely
assumed.
Almost
all
plugins
are
done
with
maven,
rather
than
gradle
gradle's
quite
exceptional
when
it's
used.
B
Right-
and
this
is
only
for
plug-ins,
so
we're
not
going
to
have
plug-ins
done
with
say,
node.js
or
make
or
something
no
we're
right,
definitely
not
good.
My
problem
was
and
then
the
thing
at
the
very
end,
we
have
that
little
section
about
depend
about
which
used
to
be
just
a
link
to
the
discussion
slightly
better,
but
that's
so
the
question
is
what
you
know.
What
do
we
do
with
this
depend
about
piece
of
it.
A
B
A
A
A
Yeah,
okay,
so
now
here
it
is
automate
dependency,
update
checks.
So
here
is
a
video
tutorial
that
we
could
embed
in
this
location.
B
A
A
So
to
upgrade.
B
A
A
A
Include
dependable,
by
default,
that's
what
this
archetype
thing
is
existing
plugins.
A
B
A
A
A
B
How
about
making
this
a
good.
A
A
B
A
And
if
I
click
it,
it
should
start
playing
nope
okay,
so
I
made
a
mistake:
that's
why
we
test
okay,
so
it
may
be
that
it
doesn't
like
the
s.
A
A
A
A
A
A
Yeah
so
well
so,
and
let
me
try
to
describe
that
one,
so
that's
illustrated
by
a
different
video
from
darren,
actually
the
same
series,
but
it's
it's
segment,
one
in
it
update
the
parent
palm
and,
let's
you
know,
what
should
we
have?
This
page
have
two
videos
on
it.
I
mean
I
don't
know
that
that's
too
excessive
is
it.
I.
B
A
A
B
A
And
here
it
is,
we
then
embed,
darren's
video
and
let
me
go
grab
that
again
and
I
think
it
just
has
a
different
start
right.
It
may
actually
even
be
a
different
video,
but
that
one
starts
much
earlier,
because
the
very
first
task
that
we
did
that
darren
and
I
did
in
the
video
series-
was
to
update
the
parent
palm
update
the,
which
is,
what
does
the
update
to
the
jenkins
core
bill
of
materials
by
using
the
most
recent
project
object
model
palm
version.
You
get
the
jenkins
core
bill
of
materials.
B
Right
what
what
I
would
like
here-
oh
god,
writers-
are
such
a
pain
in
the
butt
at
the
beginning
of
the
the
very
beginning
of
this
thing,
where
we
tell
them
the
problem
manual,
you're,
going
to
screw
yourself
right.
B
All
right
a
bullet-
and
it
said,
there's
the
the
jenkins
core
bill
of
materials
and
which
you
just
get,
and
this
solves
this
and
then
there's
the
plug-in,
build
of
materials,
and
you
will
need
to
man.
You'll
need
to
go
in
and
modify
your
code
to
pull
that
in
or
some
I
only
happen
to.
But
you
know
what
I'm.
A
A
B
B
And
then
the
section
on
the
plug-in
bill
of
materials
I'd
make
it.
However,
I
put
it
up
on
the
second
level.
B
A
B
A
B
A
B
Mighty
and
might
even
put
the
bomb
in
there
now
what
I'd
love
to
have
is,
if
I'm
coming
to
this
cold,
give
me
while
you
stand
on
one
leg,
what
each
of
them
do
for
me.
A
Okay
right,
so
let's
do
so!
Okay,
so
now
to
centrally
define.
B
A
A
And
depend
about
proposes,
pull
requests.
B
A
A
A
A
A
A
See
and
and
that's
the
piece
that
that
I
don't
want
to
state
that
because
I
think
that's
inaccurate,
because
if
we
look
at
at
parent
palm
version
numbers,
they
are
not
tied
to
jenkins
versions.
B
B
A
So
wording
wise,
I
wasn't.
I
wasn't
comfortable
putting
jenkins
core
here,
I'm
actually
maybe
core
identified
by
the
maven
property.
B
Okay,
yeah,
because,
without
that,
what
this
it
almost
sounded
like
this
is
how
I
build
this
is
defining
the
library
versions
to
you.
It's
we're
saying
for
this
release.
This
is
you
know
a
curated
set
of
some
yeah
we'll
play
with
it.
The
sometimes
when
you
step
away
you'll,
come
back
and
you'll
know
exactly
what
to
do
with
it.
A
B
A
B
B
But
but
okay,
so
are
these?
Am
I,
if
I'm
building
for
this
release,
I
can
only
use
the
library
versions
that
are
in
the
bomb.
A
Correct
okay,
at
least
that's
my
understanding.
The
core
bill
of
materials
only
says
jenkins
core
at
this
version.
Has
this
this
ver,
this
num
version
of?
Let's
pick
a
library
like?
Oh,
what's
a
good
one,
jni,
that's
a
relatively
obscure
one,
but
it's
still
bundled.
If
I
remember
correctly
and-
and
you
can't
get
another
version
because
it's
built
into
core.
B
B
A
B
B
A
B
A
A
A
Yes,
the
plug-in,
and
now
there
may
be
some
precision
com
comments
from
from
daniel,
for
instance,
I
could
see
him
saying
hey.
There
are
still
some
jenkins
plug-ins
that
are
bundled
in
core
and
he
might
then
say-
and
those
plug-ins
are
here,
but
for
me
I'm
treating
that
as
such
an
exceptional
case
that
plug-ins
bundled
in
core
I'm
treating
differently.
B
A
B
A
A
B
A
Oh,
oh,
that
and
and
that
yeah
that
I'll
I'll
try
to
put
some
words
around
it
just
to
just
because
it's
that
one
really
is
well
illustrated
by
the
video
and
it's
more
an
exercise
of
trying
to
find
a
way
to
phrase
in
the
in
simple
bullet
form.
Some
of
the
conversations
that
darren
and
I
had
in
the
video.