►
From YouTube: GSoC 2021 Git credentials binding 2021 06 17
Description
Git credentials binding project in Google Summer of Code 2021. Discussion topics included the first pull request, more project documentation, handling multiple git tool installations, adding online help for the plugin, and adding documentation to the README
A
A
That
would
that
would
be
great
with
me.
I
was
just
attempting
to
show
a
test
failure
with
by
experimenting
with
the
code.
I
was
expecting
it
to
fail
because
I
think
it
had
failed
for
me
locally,
but
I
don't
see
the
failure
when
I
run
it
now,
and
so
I
am,
I
am
at
the
moment
a
little
bit
perplexed.
I
was
expecting
to
see
failures
and
didn't,
and
so
I
would
love
to
have
a
discussion
of
the
code.
A
B
A
A
A
Then,
if
you
go
down
five
or
ten
lines,
you'll
see,
there's
an
assertion
that
the
the
very
last
line
on
178
is
that
it
expects
to
find
exactly
that
text
username
the
literal
colon
and
a
password
in
the
file
off.text,
and
it
succeeds
at
least
in
my
case
it
does.
And
now
I
need
to
check
the
ci
job.
Maybe
the
ci
job
failed
and,
and
would
tell
me
something
just
a
minute.
A
Test
tests
test
result:
okay,
yeah,
okay.
So
the
test
result.
Oh,
oh,
maybe
that's
the
reason.
Okay,
all
right!
First,
for
whatever
reason
on
the
on
the
continuous
integration
server,
it's
showing
the
failures
only
on
windows,
and
that's
where
I
was
running
the
last
time.
I
was
seeing
test
failures,
so
I
I
can't
explain
why
read
and
execute
permissions
to
be
set.
A
A
B
B
B
A
C
B
D
A
A
A
A
B
A
A
B
B
B
A
A
A
B
A
A
A
A
B
So
these
are
the
changes
I
have
made
till
yesterday.
I
was
working
on
the
test
cases
and
I
have
to
work
on
this
area.
The
git
get
tool.
Instance,
I
mean
we,
I
I
am
testing
using
different
different
different
instance
for
git
tool
instances,
so
I'm
using
j
git
to
get
apache
to
test
that
it
does
not
work
on
the
authentication
process
does
not
work
on
all
of
these
git
implementations,
and
only
this
good
cli
implementation,
but
the
variable
binding
will
require
will
be
provided
to
all
the
git
implementations.
A
E
B
B
B
Also,
I
mean
if
even
if
that
I
mean
I've
investigated
that
and
that
works
fine,
this
test
will
pass
because
this
is
not
performing
any
authentication
operation
like
git
command.
This
is
only
echoing
the
bindings
that
is
provided
by
all
required
to
all
the
implementations,
so
this
is
not
restricted.
This
is
the
the
you
know,
the
expected
behavior,
the.
What
we
are
expecting
to
fail
is
the
git
command
that
should
fail,
because
that
is
the
authentication
process
process
that
is
being
performed.
A
Okay,
so
it's
it's
not
that
we
would.
We
would
consider
putting
a
safeguard
in
there.
That
says,
if
you're
attempting
to
use
a
credential
binding
with
jgit,
we
tell
you
it
just
can't
be
done
rather
we're
relying
on
even
if
they
use
jgit
to
do
the
to
do
the
clone.
We
will
still
pass
down
username
and
password
and
assume
that
they've
got
a
command
line,
get
implementation
available
there.
Okay,.
B
A
B
A
B
B
Because
if
you
can
see
like
on
line
54
the
set
key
bindings,
so
it
is
not
checking
that
if
the
implementation
is
get
cli
get
j
get
on
jk
patches,
so
these
will
be
available
to
all
the
implementations.
If
we
include
this
under
under
the
stay
56
statement,
then
it
won't
be
available.
So
it's
upon
us
if
we
want
it
or
not,.
A
C
E
B
B
C
B
C
B
A
But
it's
do
okay,
so
it
isn't
isn't
line
33,
though
doing
okay,
I'm
gonna
have
to
go.
Do
some
research
separately,
but
I
thought
that
line
33
said
return
me
the
get
tool
for
the
jenkins
controller,
the
jenkins
dot
get
there
says,
give
me
the
node.
That
is
the
jenkins
controller.
So
that's
not
the
agent
that
will
be
running
the
job.
That's
truly
the
jenkins
controller.
Isn't
it.
A
Yeah,
so
so,
and
now
we
we,
I
think
we
correctly
can
assume
that
there
is
a
command
line.
Get
on
the
jenkins
controller.
That's
that's
to
me
seems
like
a
safe
assumption,
but
I
thought
that
rashab's
question
was
what
happens
if
the
to
get
tool
on
the
controller
is
named
git
and
the
get
tool
on
the
agent?
Let's
say
it's
a
centos
8
machine
that
I
had
to
install
a
brand
new
version
of
git
because
of
the
ancient
thing
that's
there
and
it's
called
git
dash,
2.2
2.32.
A
A
C
I
was
iterating
through
all
the
possible
get
installations
for
a
particular
agent,
and
then
I
I
checked
each
of
them,
which
one
is
valid
for
the
agent,
and
I
just
I
assumed
that
there
would
be
one
if
there's
more
than
one.
Then
I
choose
the
first
one.
There
are
like
more
than
one
options
to
run
for
a
particular
agent.
I
choose
the
first
one
and
then
I
proceed
forward.
I
did
something
like
that.
A
Controller
because
I
I
apologize
harsh
it,
but
I'm
not
sure
how
to
tell
you,
I
I
can
tell
you
what
things
I
would
think
to
check.
I
would
check
if
I
define
a
get
tool
on
my
controller
named
git
the
default
and
then
on
an
agent.
I
define
a
an
installation,
say
a
windows
agent
and
call
it
git
dash
2.2
2.32.
A
A
B
B
A
I
think
so
yeah
and
I'm
not
even
sure
what
compatible
means
in
this
case
right
because
harshit
help
me
remember
is
there:
is
there
any
difference
between
command
line,
get
versions
in
terms
of
how
we
pass
username
and
password?
I
don't
think
there
is,
I
think,
the
place
we
had
differences
was
in
ssh,
not
in
not
in
username
password.
A
So
for
at
least
for
now,
it
may
be
good
enough
just
to
say
let's,
let's
just
go
with
it
and
not
worry
about
the
complexity
of
of
not
worry
about
anything
further
on
the
complexity
of
git
tool
use
this
test.
It
get
to
the
point
where
we
think
it's
ready
to
ready
to
ship
or
ready
to
ask
for
code
review
from
jesse
glickenship.
D
A
D
D
A
A
A
C
E
B
C
Because
the
git
utils
resolve
git
tool
should,
I
think,
be
sufficient
for
us
to
decide
which
tool
we
need,
and
maybe,
after
that,
we
can
look
for
our
specific
case.
But
then
you're
saying
that
we
don't
we
from
gender.get.
But
mark
pointed
out
that
jenkins.
would
give
us
the
controller
instant,
not
instance,
not
the.
C
F
C
A
B
E
A
A
A
A
A
The
way
we
add
this
help
is
we
place
a
specifically
named
file
at
a
certain
location
in
the
in
the
in
the
source
code
repository
so
I'll
I'll
see.
If
I
can
find
that
we
learned
about
this
as
part
of
a
project,
we
did
with
chico
africa
about
how
to
add
this.
This
help.
So
I
can.
I
think
I
can
find
that
and
point
you
to
the
file
name.
C
A
A
D
A
D
A
A
Yeah,
okay,
so
share
this
one
and
here's
what
so?
If
we
look
at
how
it's
presented
to
the
user,
they
might
look
on
the
plug-in
site
for
get
client
and
what
they
see
is
this
page
of
of
documentation
that
describes
parameters
and
various
things
like
okay,
how
to
how
to
use
what
are
the
properties
that
are
defined
in
the
plug-in
and
how
do
you
install
portable
git
automatically
these
these
kind
of
things?
A
After
the
change
logs
thing
put
an
entry
here
for
pipelines
or
for
credential
mapping,
and
maybe
it's
just
credential
mapping
and
then
in
there
you
insert
several
examples:
oh
here's,
how
you
use
with
credentials
to
to
do
this
operation
and
that
operation?
So
now
what
we're
seeing
here
is
what's
presented
to
the
user.
If
we
now
open
the
github
repository,
you
can
see
where
the
doc,
where
that
documentation
actually
lives,
and
it's
right
here
in
the
readme
oops.
Sorry,
we
want
to
get
client
readme.
D
D
D
D
So
if
you
remember
that
help,
this
is
all
like
jelly
stuff
and
some
of
those
help
files
are
standards
based.
So
you
typically
put
the
help
in
the
same
path
as
the
plugin
class
under
source
main
resources.
So
you
see
source
main
resources,
org
check
and
ci
plugins
credential,
binding
impul,
ssh
user,
private
key
binding
and
there's
a
high
level
help.html.
D
And
if
you
remember
there
was
a
lot
of
text
about
like
hey
this
copies
ssh
key,
given
the
blah
blah
blah
blah
blah.
So
that's
kind
of
a
convention
based
way
of
configuring.
The
help
at
this
higher
level
you'll
see
there's
a
few
other
things,
and
so
there's
a
help
for
the
key
file
variable
and
that
you'll
see
that
corresponds
to
that
field.
D
A
A
A
So
now
we
would
not
find
this
kind
of
a
page
yet
for
the
get
client
plugin,
because
it
hasn't
published
anything.
Yet
that
has
a
credential.
But
when,
when
the
get
client
plugin
publishes,
it
will
be
added
to
the
same
list.
If
I
understand
correctly,
because,
for
instance,
here
we
see
vault,
ssh
user
private
key
binding
that
thing
and
that
one,
I
think,
is
provided
by
something,
isn't
the
credentials
binding
plug-in
it's
from
the
hashicorp
vault
plugin.
A
By
it
so
harshit
are
you
have?
Will
I'll
publish,
publish
the
recording
of
this
so
that
you
can
refer
to
it
later
if
you
need
to,
but
justin's
just
shown
us
how
you
put
the
help
in
there
that
was
justin.
That
was
absolutely
great.
Thank
you
so
much
sure,
absolutely
anything
else.
I
should
show
here
or
hand
it
back.
B
F
D
B
C
A
Correct
we
don't,
I
know
it's,
it's
like
black
dark,
evil,
terrible
magic,
but
it
is.
It
is
exactly
that
kind
of
magic,
it's
fantastical
magic.
So
so
what
happens
is
there
is
a
tool
that
runs
periodically
that
surveys
all
jenkins,
plug-ins
and
looks
for
all
implementations
of
those
extension
points
and
extracts
the
documentation
from
those
plugins
and
publishes
it
to
that
steps
reference.
A
A
Yeah
and
because
all
right
harshit's
pull
request
will
add
one
little
file,
a
help.html
or
maybe
three
files,
help.html
and
two
more
for
some
variable
or
something
like
that
and
magically.
It
will
appear
in
that
pipeline
steps
reference.
It
is
visible
in
the
jenkins
ui,
with
the
snippet
generator
yeah.
It
really
is
quite
elegant.
E
A
Now
harshit
there
was
one
item
I
had.
You
had
submitted
a
pull
request,
so
we've
only
got
a
few
minutes
left,
but
maybe
it
would
be
enough
for
us
to
get
that
pull
request.
Merged
you'd
submitted
a
pull
request
to
jenkins.io
just
a
minute.
Let
me
see
if
I
can
find
it
and
I
was
gonna
offer
if
you're,
okay,
I
can
just
apply
the
changes
and
merge
the
the
pull
requests,
but
if
you
would
prefer
to
to
make
the
changes
yourself
you're
welcome
to
do
that.
A
A
Yes,
okay,
so
this
is.
This
is
the
change
in
some
of
the
changes
I
propose.
The
mandatory
change
is
this?
Oh,
let's
make
it
big
enough
to
read
okay,
the
mandatory
change
is
this
one
it
needs
to.
I
know
is
that
right,
which
one
is
the
no?
No.
Where
was
that
there
was
one
change
that
had
to
be
made
in
order?
No,
maybe
not.
A
A
B
A
A
A
A
That
are
you
comfortable
with
the
change
you
need
to.
Well.
Do
you
have
time
to
make
the
change,
because,
given
that
I've
got
permission,
I
had
permission
to
do
that?
I
should.
I
could
actually
make
this
change
as
well
and
get
that
image
placed
into
the
images
directory
so
that
you
can
stay
focused
on
the
code
rather
than
on
documentation.