►
From YouTube: 2022 05 12 Pipeline Help
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
A
B
Yes,
please
I'll
how
to
kickstart
documentation
for
a
chosen
plugin.
B
After
you
probably
discovered
a
plugin
that
actually
needs
documentation
from
the
listed
one
in
your
document,
let's
say,
for
instance,
the
http
request.
Do
you
just
go
ahead
and
start
documenting
or.
A
B
So
during
the
gates
right,
the
git
documentation.
You
actually
created
like
a
separate
branch
where
we
are
working
with
that's
what
working
with
so
for
all
that
plugins.
Are
we
going
to
do
the
same
for
the
same
pattern
we
use
in
the
git
plugin
we
just
create
like
our
own.
A
separate
branch
then
starts
working
with
a
branch.
A
A
A
A
Okay,
then,
let's
go
ahead
with
those
and
we'll
so
we'll
we'll
look
first
at
progress
here.
It's
what
we
can
see
is
thank
you
sophia
for
yours
that
you've
submitted
I've
made
a
request
for
some
changes.
Oh
and
it
looks
like
you've
applied
those
changes
good
and
you
did
that
after
I
had
gone
to
bed
or
after
I
had
disconnected
yesterday
excellent
okay,
so
you
applied
the
changes
and
they
should
be
changes.
A
Excellent
and
that's
that's
the
process
we
like,
and
my
apologies
afi-
that
your
pr
came
in
just
a
little
bit
after
sophia's
and
I
didn't
get
to
your
review
yet
so
I
am
behind
schedule
there.
I
need
to
review
this
one,
and
I
haven't
done
the
reviews,
yet,
thankfully,
the
ci
job
did
pass.
So
that
gives
me
the
confidence.
Okay,
it's
not
see.
Continuous
integration
did
not
find
any
problems
with
it.
A
Needs
review
likely
needs
changes
and
then
so
offi.
What
we'll
do
is,
I
will
mark,
will
review
late
today
so
by
by
late
today.
Well
after
the
time
when
you
should
be
asleep
and
long
asleep,
so
afi,
if
you
check
tomorrow
morning
for
comments.
B
A
B
Oh,
you
go
ahead,
go
ahead.
We
kind
of
had
a
discussion
yesterday.
So
I
guess
that's
what
sophia
asked
about
say.
No,
I
was
actually
going
to
ask
how
to
resolve
pull
requests.
In
case
like
when
you
request
for
a
change
up.
Do
I
actually
like
reserve
it,
because
I
noticed
that
some
of
the
comments
were
not
outdated
and
I
had
to
probably
manually
go
resolve
every
requested
change,
yeah.
A
Okay,
so
so
let
me
see
if
I
got
your
question
correctly
when
a
a
change
is
requested,
should
I
resolve
the
comment
if
github
did
not
resolve
it
automatically.
A
Good,
okay
and
that's
a
that's,
a
question
that
so
to
to
highlight
in
case
others
may
not
be
aware
what
that
means.
What
you
see
here,
if
oh
whoops,
if
we
look
at
sophia's
with
that,
had
changes
requested
what
you'll
see
is
it
shows
this?
I
offered
several
suggestions,
there's
my
comment
and
then
hidden
behind
these
gray
bars
are
a
series
of
let's
make
that
bigger.
So
it's
readable
of
things
that
are
listed
as
outdated
changes
and
it
says,
show
resolve
so
if
I
click
show
resolved,
it
shows
hey.
This
was
mark's
suggestion.
A
A
So
so,
usually,
if
your
action
that
you're
taking
does
what
you
feel
would
be
resolves
completely
the
conversation,
then
you
absolutely
should
do
exactly
what
you
did
and
market
resolved,
because
it
helps
me
as
a
reader
later
to
know
oh
she's
processed
each
of
these
things
she
thought
about
them
and
decided.
Yes,
this
one
is
solved
and,
and
she,
whether
whether
you
accepted
my
change
or
not
by
your
showing
it
as
resolved,
that
tells
me
you've
thought
about
it
and
you've
made
that
conscious
thought
that,
yes,
this
should
be
marked
as
resolved.
A
No,
no
to
give
you
that
there's
a
subtlety
hiding
here.
There
are
some
places
where
a
a
comment
is
made-
and
someone
may
say:
oh,
I
think
it's
resolved.
They
mark
it
as
resolved
and
others
find
it
that
oh
no,
it's
not
really
resolved
and
they
may
correctly
say
I'm
going
to
unresolve
this
conversation,
because
we
need
to
need
to
talk
more
about
need
to
chat
more
about
this.
A
So
if
we
need
to
chat
more
about
this,
I
may
unresolve
it
and
some
in
some
projects
people
will
say
hey.
Please
don't
resolve
my
conversations
because
it
makes
it
hard
to
find
my
comments
so
be
aware
of
the
place
where
you're
at,
but
for
me,
on
the
git
plug-in
and
for
most
people
they
will
find
it
helpful
if
you
resolve
the
conversation,
when
you
think
it's
done.
A
A
A
A
That
was
a
help
helper
to
get
you
started,
but
ultimately
I'll
have
to
merge
this
from
the
add
checkout
scm
examples,
branch
to
the
master
branch
and
most
maintainers
will
want
you
to
submit
your
pull
request
to
the
master
branch
rather
than
to
the
to
to
any
other
branch.
They
want
you
to
be
proposing
changes
that
they
will
put
into
production.
A
So
so
yeah,
so
what
it
was
is,
why
did
we
use
a
separate
branch
for
the
git
plug-in
mark
wanted
to
provide
a
framework
where
sophia
and
afi
could
write
and-
and
that
was
that
was
the
whole
purpose
there
right.
I,
the
outline
was
not
ready
for
the
master
branch,
because
I
didn't
want
to
publish
it
to
everybody.
So
the
outline
was
placed
on
a
separate
branch.
A
A
A
B
A
A
B
Yeah
that
that
really
makes
sense,
okay,
so
the
next
thing
I
was
going
to
ask,
I
think
so
far
today
about
the
documentation.
That's
one
of
the
questions
we
had
when
we
spoke
yesterday
so
and
how
to
add
documentation
to
the
plugin.
We
want
software
guides
that
we
know
exactly
or
the
parts
that
are
very
relevant
or
where
to
put
more
information
and
also
whatever
you
choose
one
plug-in,
let's
say
so
over
the
weekend.
B
If
we
get
time
mode
like
work
on
one
particular
plug-in
and
on
different
areas,
but
for
one
plug-in
or
you
want
us
to
take
like
different
ones
and
work
on
different
places,
we
wanted
to
like
know
your
thoughts
on
that.
A
Good
good
question
very
good
and
that's
that's
an
excellent
question.
So
so
what
I'd
propose
is,
let's
talk
about
the
different
locations
that
you
could
improve
and
the
levels
you
can
improve
because
because
there
are
different
ways
that
people
learn
about
and
experience
jenkins,
plugins
right,
there
are
different,
different
layers
that
they
see
things
at
so
so
what
I'd
propose
is,
let's
start
with
a
discussion
of
plug-in
documentation
from
plugins.jenkins.io
as
the
first
level.
So
let's
call
this.
A
A
So
so
what
I'd
say
is:
let's
first
do
those
as
as
talking
points
as
to
how
each
of
the
how
you
might
do
each
of
those
levels
and
how
you
might
help
at
each
of
those
levels.
B
A
B
A
So
sorry,
I
really
try
to
mute
quickly
and
I
didn't
get
it
done
in
time
all
right.
So
so.
The
by
submitting
a
pull
request
to
the
readme
you've
submitted
a
request
to
improve
the
documentation
on
plugins.jenkins.io
and,
and
we
hope,
that's
the
first
or
that's
a
common
experience.
It
may
not
be
the
first,
but
it's
the
common
experience
for
people
to
read
the
plugin
documentation
and
if
we
look
at
a
typical
plugin
on
jenkins,
so
the
git
plug-in
has
an
awful
lot
of
documentation
because
I've
tried
to
work
hard
on
making
its
documentation.
A
A
B
A
B
A
A
A
A
A
A
A
A
A
Plug-In
online
help
for
individual
pipeline
tasks
and
what
we
did
was
find
it
there
and
you
could
add
to
it.
That's
a
good
way
to
add
value
of
hey,
I'm
going
to
provide
some
more
examples,
or
I'm
going
to
provide
more
details
about
this
thing
now.
The
bigger
challenge
is
when
we
have
missing
plug-in
online
help
from
parameters
of
individual
pipeline
tasks
and
again
this
is
why
are
we
caring,
because
many
many
users
complain
that
the
existing
documentation
is
incomplete?
A
Let's
go
back
to
our
http
request,
plug-in
and
see
if
we
can
find
an
example
of
something
that's
incomplete,
like
yeah
here
you
go,
custom
headers
has
no
description,
telling
us
what
what
is
custom
headers?
How
is
it
used?
What
does
it
mean?
Form
data
has
no
description.
What
is
it,
what
does
it
mean?
A
A
Okay,
all
right
so
so
what
we
saw
then
is
here:
we've
got
custom
headers
that
has
no
help
text,
but
http
mode
does
have
help
text.
So
what
we
would
guess
is
help
for
custom.
Headers
probably
needs
to
go
into
the
source
code
somewhere
near
the
help
for
http
mode.
This
is
just
me
guessing,
but
that's
we've
got
to
insert
something.
So
we
need
to
find
the
location
find
the
location
where
that
help
should
be
inserted.
A
In
the
source
code
insert
some
help,
compile
the
plugin
run
it
in
jenkins
and
confirm
that
the
help
we
added
is
visible
and
that's
not
as
not
as
friendly
as
I'd
like
it
to
be
right,
but
I
have
to
openly
admit
that's
the
reality
for
right
now
that,
because
this
help
is
done,
it's
placed
in
specific
locations
by
convention.
A
A
A
A
A
A
A
C
A
We
get
very
lucky
very
good,
so
we
know
which
one
it
is.
Thank
you
bruno,
that's
great
all
right,
so
we
got
very
lucky
that
this
is
the
one
that
is
really
being
displayed
in
that
page,
excellent.
Okay,
given
that
we
could
guess
now,
let's
look
for
http,
so
it's
the
the
path
here
tells
us
something
about
it.
So
a
source
main
resources.
Okay,
it's
text
files
or
it's
not
source
code;
it's
related
to
source
code,
so
text
files,
html,
etc
in
this
class
path
and
for
the
class
http
request
step.
A
A
A
So
somehow
I'm
hoping
that
custom
headers
is
in
this
file
and
is
mentioned
there,
which
it
is
there's
custom
headers
and
it's
got
this
thing
called
the
data
bound
setter,
which
makes
it
that's
that's
jenkins,
jenkins,
stuff,
to
tell
us.
Yes,
we
can
use
that,
so
I
wanted
to
add
something
for
for
custom
headers.
So
what
I
do
is
just
as
there
was
a
content
type
I'm
going
to
cheat
and
copy
that
to
custom
custom
headers,
where
that
is
this
thing
right
here.
A
A
A
A
And
what
this
is
going
to
do
is
compile
the
plugin
start,
a
jenkins
version
2.347
with
that
plug-in
loaded,
so
that
I
can
experiment
with
it,
explore
it
and
see
if
I
can
view
the
online
help
for
it
now,
while
it's
doing
that
because
of
the
way
I'm
developing,
I
have
to
turn
on
the
tunnel.
Sorry
about
this,
but
my
because
I'm
not
developing
on
my
own
local
machine,
I
have
to
okay.
I
think
the
tunnel
I
want.
A
And
if
we
look
at
the
installed
plugins,
we
should
see
http
request
right
here
and
it's
private
something
something
m
wait.
So
we
were
successful
and
if
we're
lucky,
it's
got
enough
of
pipeline
loaded
that
when
I
do
slash
pipeline
dash,
syntax
I'll
be
able
to
see
the
online
help
it
does.
We
got
lucky
so
http
request
here.
Are
the
here's
the
online
help
that
it
already
had
under
advanced
we're
going
to
look
for
custom
headers.