►
From YouTube: 2022 05 05 Pipeline Help Project
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
5th
of
may
2022.
This
is
the
pipeline
help.
She
called
africa
contributon
project
and
we're
limited
on
our
time
today.
So
we're
going
to
focus
on
one
specific
item
unless
offi
or
sofia
are
there
questions
that
you
have
other
than
other
than
questions
we
had
from
the
previous
session.
So
how
to
find
the
locations
that
need
more
pipeline
help
seem
to
be
the
biggest
challenge,
and
I
think
I've
got
an
answer
for
that.
So
I
wanted
to
give
that
answer.
A
Into
the
so
it
will
be
visible
right.
So
that's
that
I
think,
is
the
bigger
problem.
We,
I
was
showing
all
sorts
of
challenges.
Last
time
we
met
is
hey.
How
do
we
do
this?
And-
and
let's
let's
do
that
in
a
way
that
I
can
show
immediately
with
a
plug-in-
that's
very
familiar
to
me,
I'm
I'm
a
maintainer
of
the
git
plug-in,
and
so
I
can
show
that
one
pretty
readily
and
talk
about
why?
Why
it's
inadequate
and
specifically
how
to
how
you
the
two
of
you,
can
help
us
with
it.
A
So,
let's,
let's
start
with
the
the
story,
the
story
goes
like
this.
A
user
asked
the
question.
A
So
here's
the
bug
report,
the
user,
says
I
embedded
the
username
and
password
into
the
url
of
my
of
my
repository
in
jenkins
and
now
it's
visible
to
everybody
in
the
log
files
and
that's
that's
a
correct
statement.
The
the
user
is
absolutely
correct.
If
you
do
that,
where
you
put
the
username
and
password
right
into
the
url,
it
becomes
visible
to
anyone
who
reads
the
log
files
or
any
a
number
of
other
places
where
it
gets
gets
in
the
way
and-
and
my
response
was
hey-
that's
a
a
really
bad
choice.
Don't
do
that.
A
You
should
use
the
jenkins
credential
system,
but
then
the
embarrassment
thing
came
in
that
I
sh
we
should
have
in
the
git
plugin
documentation,
examples
that
show
how
to
use
this.
How
to
do
this?
This
is
not
an
exotic
operation
right.
This
is
not
something
infrequent
people
do
this
all
the
time
and
yet,
shamefully,
the
jenkins
get
plug-in
documentation.
If
we
look
at
the
documentation
on
the
plugin
site,
so
we're
going
to
look
at
git.
A
A
There
are
only
three
places
where
that
that
occurs
in
you
notice
the
size
of
this
scroll
bar
on
this
documentation.
There's
a
lot
of
documentation
on
the
git
plugin
in
this
page
really
really
a
lot,
and
yet
this
crucial
use
case.
How
do
you
use
credentials
with
git
is
not
covered,
and
if
we
look
for
checkout
scm-
oh
it's
even
worse,
there
is
not
a
single
reference
in
the
plug-in
in
the
get
plug-ins
documentation.
A
A
A
A
A
There's
actually
lots
of
help
available,
and
this
help
this
kind
of
help
where
it
gives
examples
of
oh
here's,
the
get
step
with
defaults,
here's
the
get
step
with
a
private
key
credential,
here's
the
get
step
with
get
protocol
and
polling
disabled.
Each
of
these
examples
is
in
here,
if
you'd,
be
willing
to
copy
or
create
something
similar
for
these,
like
these
things,
but
put
them
in
the
readme
file
for
the
git
plugin.
That
will
give
people
a
way
to
find
these
examples.
So
here
we've
got
this
little
tiny
section
on
pipelines.
A
Okay,
so
what
I'm
going
to
do
is
I'm
going
to
do
the
the
start?
The
example
thing
from
from
inside
this
repository
and
I'm
going
to
put
it
on
a
separate
branch
for
now,
and
you
can
submit
your
additional
proposals
even
to
that
separate
branch.
If
you'd
like
or
do
it
from
your
own
fork,
either
is
fine.
A
A
And
now
I'm
going
to
go
grab
some
examples
from
from
other
places
in
the
source
code
and
we'll
paste
those
in
just
as
a
convenient
way
to
get
started.
So,
let's
find
where
would
I
look
for
this?
It
would
be
in
sorry.
I
have
to
get
out
my
better
search
tool
because
I
don't
I'm
not
as
comfortable
using
github
search.
A
A
A
A
A
A
A
A
And
let's
use
a
and
a
different
branch,
non-default
branch,
so
in
this
case
we
go
back
to
the
syntax
snippet
generator
we
insert
get
client
plugin
and
we
need
to
go
find
a
branch
name
that
we
want
to
use.
So
I
have
to
look
at
the
repository
and
choose
another
branch.
There
will
be
several
branches
here.
Let's
pick
stable
dash,
2.x.
A
B
Yeah-
okay,
it's
just
that
bit
because
you
are
very
familiar
with
the
plugin,
so
you
know
what
examples
you
will
be
using.
But
for
me
I
really
can't
come
up
with
the
examples,
except
maybe
I
kind
of
like
studying
a
lot.
A
How
about
how
about,
as
part
of
this,
let
me
put
in
headlines
for
the
different
examples
that
you
could
use.
Would
that
be
okay,
that
then,
then
you
then
you
can
highlight
those
and
we
we
can
talk
about
which
ones,
I
think
are
most
interesting
and
you
could
you
could
use
the
syntax
generator
to
create
those.
Would
that
would
that
help
with
that
question,
I
think
it's
a
valid
point.
B
A
So
and
this
one,
what
you
would
do
is
you
go:
go
to
the
snippet
syntax
generator
and
you
click.
Where
is
the
add,
oh,
add
additional
behaviors.
So
it
should,
as
you
add,
additional
behaviors
you
scroll
down
here
and
find
git
lfs
pull
after
checkout
and
let's
use
exactly
those
words
with
git
large
file,
support.
A
A
A
Okay,
add
a
repository
browser
for
my
add
a
actually
yes
repository
browser
for
bitbucket,
something
less
common
than
get
than
github,
and
then
what
you
would
do
is
you
would
go
here
and
in
the
snippet
generator
it
says
up.
Where
is
this?
It
says
repository
browser,
you
click
bitbucketweb
and
it
will
ask
hey:
what's
the
url
for
the
bitbucket
repository
you
put
it
in
something.bitbucket.com.
A
A
Continuing
this
exercise,
we
could
look
at
clean
before
well
that
one
I
don't
want
people
using
in
pipeline
they'll
continue
here.
We
go
how
about.
A
A
Okay,
see
also,
if
you
want
to
do
a
5,
a
10
or
15
minute
see
also
the.
A
Let
me
get
the
url
for
them,
because
I've
got
some
some
videos
that
I
created
a
while
ago
that
are
5
or
ten
minute
videos
on
improving
improving
jenkins
performance
on
large
repositories
that
you
might
want
to
look
at
just
as
a
way
to
see
some
other
things
that
might
be
con
included
just
a
moment.
So.
A
C
Okay,
so
that
means
that
initially
because
we
were
going
to
continue
like
picking
something
right
according
to
the
document,
I
already
cloned
the
http
ref,
so
I
it
so
I'll
go
and
and
this
and
improve
from
this
branch,
and
then
so.
Should
I
push
to
this
branch
or
I
should
just
create
and.
A
You
you
just
create
your
own
copy
of
the
same
branch
and
you
could
push
to
your
own
to
your
own
repository
that
way,
you
don't
have
to
have
push
permission
to
the
central
repository,
okay,
all
right
and
let's
check
in
with
each
other
by
slack,
because
this
may
still
be
too
unclear
and
over
the
next
day
or
two
we'll
check
in
to
see
if
it
is,
we
could
schedule
another
session
to
meet
again
to
to
be
sure
that
we
get
it
clarified.
I
am,
I
am
sincerely
sorry
for
having
to
do
this
so
quickly.