►
From YouTube: GSoC 2021 Git credentials binding 2021 05 26
Description
Git credentials binding project meeting during Google Summer of Code 2021. Community bonding to investigate and understand issues and prepare for the coding phase that begins June 7, 2021
A
Welcome
to
get
plug-in
no
the
get
credentials
binding,
google
summer
of
code
project
hour
project
for
jenkins.
This
is
office
hours
and
mentoring.
So
remember
we
abide
by
the
google
summer
the
jenkins
project
code
of
conduct,
it's
the
25th
of
may
harshly.
Do
you
have
questions
that
you
wanted
to
open
with
or
any
progress
you
wanted
to
share.
A
C
A
Right
and
I
didn't
do
that-
let
me
get
that
doc
ready
well
harshith.
You
can
start
sharing
your
your
screen
and
I'll
get
the
doc
ready
to
be
sure.
We've
got
a
copy
of
the.
A
A
B
B
B
B
D
E
B
Okay,
so
in
this
step
I
am
adding
the
I'm
first
removing
the
tags,
because
if
the
tag
already
exists,
it
shows
an
error.
So
I
have
to
first
remove
the
tag.
If
it
already
exists,
then
I
have
to
add
and
then
I
will
clone
any
changes
or
fetch
them.
Then
I
will
push
the
push,
push
the
changes
or
you
can
suppose
the
tag
in
the
repo
and
then
I'm
creating
us
like
a
temporary
file
so
that
you
know
that
it's
working
and
then
I'm
pushing
all
the
changes.
B
A
A
B
A
B
I
also
wanted
to
know
that
is
j
git
j
get
in
the
scope
of
the
project,
or
we
will
be
using
only
git.
A
Only
using
yet
so
good
question,
so
let
me
put
a
note
on
that.
So
what
about
j
git
and
I'm
going
to
share
my
screen
now
so
that
we
can
see
what's
being
typed?
A
A
A
Command
line
git
is
the
definitive
implementation.
It's
the
reference
implementation,
it's
the
one
that
has
support
for
large
files.
It's
the
one
that
has
support
for
the
most
options,
has
support
best
support
for
sub
modules.
All
those
things
are
are
reasons
to
stay
away
from
jet.
Now
we
could
ask
rishabh
on
his
experiences
with
jgit
last
year,.
C
And
so,
and
so
my
my
experience
with
jj
was
particularly
my
interest
with
jk
was
particularly
in
perspective
of
its
performance
as
compared
to
command
line
gate
and
yes,.
C
And
do
we
want
to
share
what
we
yeah
okay,
so
we
saw
that
yeah
jacob
is
faster
for
smaller
repositories
and
and
and
we
put
that
estimate
around
for
repositories,
less
than
50
mb
j
gate
was
performing
better
than
command
line
get,
but
after
that,
command
line
get
wins
big
time
right.
A
B
I
just
wanted
to
know
the
project
structure
is
like
we
will
be
implementing
the
git
credential
binding
in
the
git
client
plugin
only,
and
I
don't
want
to
implement
it
in
the
git
plugin
now,
because
I
think
it
client
plugin
could
provide
some
features
or
features
of
functionality.
That
will
be
benefit
for
this
implementation.
A
B
I
mean
like
we
cannot
reuse
the
code.
I
know
like
the
the
I
pointed
in
that
the
chat
we
cannot
reuse
the
code.
We
can
use
the
functionality
only
like
the
functions
like
there
is
an
author
is
I
mean
there
is
a
function
in
that
which
shows
which
version
of
git
we
are
using,
that
we
can
use,
but
we
cannot
use
the
code
directly
because
the
code
has
to
be
modified
between
them.
A
B
I
have
to
I
have
to
set
up
the
house
file
like
I
wanted
to
set
up
in
like
a
proper
development
environment
like
I
don't
want
to
install
too
many
vms
or
dual
boot,
my
pc,
so
I
was
like
in
scope
like
so
like
you
can
guide
me
on
that.
A
If
you'd
like
you,
want
access
to
a
wider
range
of
operating
systems
and
versions,.
D
Okay-
and
I
think
that
would
generally
be
available
if
we
did
if
he
did
want
to
use
that,
I
also
would
want
to
make
sure
that
we're
being
kind
to
mark
and
his
his
time
off.
A
Yeah
yeah
that'll
be
that'll,
continue
to
be
available
even
when
I'm
off,
unless
it,
if
it
shuts
itself
down,
I
won't
be
there
to
restart
it,
but
if
it's
still
running
I
could
certainly
give
give
access
the
for
me.
The
the
first
target
ci
jenkins
owe
is
available
now
and
a
pull
request
will
will
let
you
use
that
infrastructure
and
if.
A
D
D
Okay
cool,
I
figured
those
were
all
linux,
but
I
figured
I'd
ask
I
was
not
very
yeah.
A
A
A
Yeah,
so
so,
if
certainly
before,
before
the
project's
done,
assuming
I'm
back,
I
will
run
your
code
on
in
my
environment
to
be
sure
that
that
it,
it
doesn't
surprise
us,
but
I
don't
think
you
need
to
worry
about
that.
Initially,
harsha
just
be
aware
that,
yes,
there
are
interesting
variants
of
command
line,
git
that
we
have
to
test
like
the
ancient
command
line,
get
1.8
on.
A
A
B
A
B
I
don't
I
just
missed
it
so,
in
the
previous
meeting
we
were
just
one
were
curious
about
how
this
will
work
in
the
freestyle
job,
how
the
credentials
could
potential
binding,
plugin
is
used
in
freestyle
job
and
how
the
functionality
that
I'm
providing
could
be
used
in
that.
B
B
A
Well,
except
that,
inevitably,
when
I've
told
myself
oh,
I
don't
need
that
some
jenkins
user
has
proven
me
catastrophically
and
completely
wrong,
and
but
I
don't
know
what
this
means
still,
I'm
not
sure
how
this
will
work,
because
what,
if
you
choose
to
add
a
build
step
now,
that
is
a
is
a
a
batch
file.
How
does
this
binding
know
that
it's
contributing
to
a
batch
file?
A
B
A
B
F
A
A
A
B
A
A
A
A
D
A
Unmasked
value,
so
we
could.
We
could
turn
off
screen
sharing
so
that
so
that
harshit's
password
is
not
displayed,
and
then
you
could
do
a
right
after
right
before
the
env,
you
could
do
an
echo
dollar
sign,
open
square
bracket
or
open
curly,
brace
ssh
under
get
what
was
it
get
ssh
ass,
pass
close
so
that
you
could
see
have
it
output
the
name
of
that
file?
A
D
B
B
D
And
mark
since
this
wasn't
sorry
while
you're
testing
this
hardship,
I
thought
I'd
ask
mark
a
question,
but
please
interrupt
if
you'd
like.
I
would
assume
that
this
would
be
probably
lower
on
the
priority
list,
since
it
wasn't
necessarily
initially
in
scope.
Is
that
a
fair
assessment.
A
Yes,
absolutely,
I
think
if
we,
if
we,
if
we,
if
harshit's,
able
to
implement
username,
password
and
private
key
for
bat,
powershell
and
cli
and
sh
that's
in
pipeline,
that's
already
that's
already
achieved
what
I
had
envisioned
as
the
objectives,
particularly
then
the
challenge
of
testing
it
in
all
the
configurations
assuring
it
works
automation
of
the
tests.
A
A
I
don't
know
if
it's
actually
something
you
want
to
consider
using
that
thing,
because
it
was
sort
of
an
ugly
dirty
trick
that
I
used
that
only
worked
on
my
local
environment
and
I
accepted
it
was
a
dirty
trick.
There
I'm
sure
there
are
much
better
ways
to
test
credentials
than
what
the
technique
I
used.
A
Jenkins.O
right,
what
it
did
is
it
relied
on
a
specific
file
in
a
specific
location
and
if
it
found
the
contents
of
credentials
in
that
specific
location,
it
would
iterate
over
them
and
use
them
for
tests
gotcha.
So
it
was
a.
It
was
a
a
very
dirty
technique.
Knowing
that
hey
mark
keeps
sensitive
files
in
his
dot
ssh.
A
B
A
A
Then
I
guess
a
question
from
from
me
to
you
is
as
part
of
your
design
document.
Do
you
want
to
give
some
thought
to?
How
will
you
test
this
in
in
an
environment
that
is
that
is
as
public
as
ci.jenkins.io
is,
where
you
can't
put
your
credentials
into
it?
You
have
to
find
some
other
way
to
do.
F
C
C
A
I
would
think
so
either
that
or
okay
we
could
take
the
the
classic
approach
that
was
used
in
the
get
get
git
plug-in
originally,
where
for
the
first
18
months
of
the
life
of
the
git
plug-in,
there
were
zero
automated
tests.
But
that's
that
would
make
me
very
uncomfortable
having
no
automated
tests
for
this
new
capability.
C
And
if,
if
that's
the
case,
then
could
we
drop
your
motor
skills?
I'm
not
sure
if
you
would
like
that.
C
So
I
one
more
question
I
had
with
this:
was
that
so
currently
is
exploring
disney
password
credentials,
he's
built
a
prototype
and
he's
investigating
further.
So
do
we
want
him
to
explore
both
of
the
bindings
and
how
they
could
potentially
work
and
have
a
working
prototype
during
the
community
bonding
phase
only
so
that
he
has
a
good
sense
of
what
challenges
he's
going
to
face
for
the
two
months
for
the
coding
phases,
and-
and
apart
from
that
also,
if
it's
possible,
he
could
look
at
the
testing
framework.
C
Maybe
he
could
look
at
the
existing
way.
You've
tried
to
automate
the
credentials
test
cases
where
you
have
to
consider
contentions
as
well,
and
then
he
could
give
us
an
estimate
on
how
things
could
go
further.
C
C
A
F
D
And
they
may,
they
may
actually
have
opinions
on
design
too.
You
know
if
we
once
we
have
a
design
document,
so
right.
C
Also,
I
I
had
one
more
question
when
we,
when
we
were
talking
about
releasing
get
credentials
binding
when
we
is
it
necessary
for
us
to
release
both
of
the
bindings
at
the
same
time
or
are
we?
Are
we
willing
to
first
release
username
password
and
then
go
iteratively
work
on
ssh
privacy.
A
D
And
I
have
an
administrative
question:
that's
a
follow-up
to
that
one!
Mr
mark,
do
you
have
backup
maintainers
who
you
would
want
to
kind
of
usher,
something
like
that
through
or
is
that
something
that
would
be
better
to
like
you
know
if
you're
out
for
surgery
during
this
time,
then
we
try
and
get
this
ready
for
you
for
when
you're
back.
A
A
A
Okay,
so
primarily
go
with
those
folks
and
and
if
either
of
them
cannot,
then
there.
I
think
there
are
even
several
others.
Those
two
are
designated
maintainers
that
I
got
agreement
from
there
they're
that
they're
willing
to
be
maintainers.
A
A
A
A
A
A
B
A
A
Ramon
and
olivier
are
backups
for
security
as
well.
That's
perfect,
so
so
that's
part
of
their
responsibility
is
backup.
So
if
there
were
a
security
issue,
for
instance,
something
found
in
some
time
ago,
we
somebody
found
an
issue
in
jgit.
We
had
to
roll
because
there
was
a
jet
security
issue
and
we
rolled
and
and
if
that
kind
of
thing
happens,
the
maintainers
will
be
contacted
and
usually
they'll
want
to
deliver
the
security
fix
with
nothing
else
in
it,
except
the
security
fix.
A
D
A
We
are
the
automated
tests
probably
need
to
sh
to
assert
that
the
sensitive
information
only
exists
on
the
disk
for
as
long
as
it
is
expected
to
exist,
in
other
words,
after
the
with
credentials
block
exits,
the
the
sensitive,
either
username,
password
or
private
keys
should
no
longer
be
on
disk,
and
so
again
that
makes
an
interesting
test
case
for
you,
harshit
on.
How
do
I
check
that
you
could
look
at
the
see
the
get
plug-in
tests
of
pipeline
code
for
another
example
for
different
examples
of
testing
pipeline.
B
I
mean
like
in
credential
binding
plugin,
there
is
a
class
name
unbinder,
which
is
a
callback.
So
when
the
pipeline
execution
is
complete,
I
mean
the
script.
The
code
in
the
with
credential
block
is
completed.
The
callback
is
called
so
I
am
pushing
yeah.
I
am
pushing
the
the
unbinder
function
into
that
and
it
will
automatically
delete
the
the
file
that
has
been
created.
A
C
A
C
I
have
a
question
actually
when
I
just
yeah,
so
my
question
is
that,
from
my
experience
last
time
during
the
community
economy,
I
never
thought
about
giving
an
estimate
on
how
much
time
I
would
take,
or
it
would
take
for
us
to
release
a
particular
feature.
So
I'm
not
sure
if
it's
a
right
exercise,
but
if,
if
harshit
is
going
to
focus
on
developing
a
prototype
and
then
looking
at
how
the
test
testing
framework
needs
to
be
modified,
but
then
do
we
need
to
also
answer.
C
After
doing
both
of
those
exercises
that
how
long
can
we
take
to
push
one
of
the
features?
Let's
suggest
the
username
and
password
binding
to
production
or
a
do?
We
want
to
give
an
estimate
so
that
we
know
for
ourselves
that
how
we're
progressing
throughout
those
places?
A
D
C
But
then,
what
I'm
afraid
of
with
this
approach-
maybe
a
drawback,
I'm
not
sure,
is
that
if
we're
focusing
on
this
particular
binding
and
it's
testing
and
then
ultimately.
C
Is
it
safe
for
us
to
leave
the
planning,
or
maybe
the
research
part
of
prototyping,
of
ssh
type
authentication
pathways
of
private
key
at
a
later
stage
of
the
project,
or
should
we
is
it
something
that
needs
to
be
explored
within
this
phase
so
that
we
don't
hit
a
roadblock
during
the
coding
phases
or
maybe
when
you're
gone
during
that
time?.
A
And
I
thought
that
that
harsher
to
describe
that
he
wanted
to
do
private
key
explorations
during
community
bonding
as
well.
We
are
we're
what
we
are.
Where
are
we
in
terms
of
time
we're
a
week
and
a
half
in
so
we've
got
another
week
and
a
half
before,
let's
see
google
summer,
let
me
look
at
the
timeline
just
to
be
sure.
B
So
I
have
so
right
now.
I've
decided
that
I
will
first
focus
on
the
testing
part
of
the
user
of
the
user
and
password
binding,
and
then
I
will
go
to
the
ssh
binding
and
for
now
and
I
will
focus
on
the
testing
one.
So
major
focus
is
on
testing
for
me,
then
I
will
shift
on
the
message
binding.
A
Okay
and
so-
and
I
think
I
think,
rishabh
had
a
good
question,
should
we
rather
focus
have
you
have
shift
invert
that
so
we
have
you
focus
on
the
private
key
first
to
explore
it
and
then
come
back
to
testing,
because
for
at
least
my
experience
with
finding
ways
to
automated
tests
is
it,
it
was
quite
often,
it
took
me
a
lot
longer
to
find
a
way
to
do
the
test
automation,
whereas
if,
if
a
rapid
exploration
of
private
keys
shows
a
problem
that
that's
probably
much
more
important
to
us,
rishabh
was
that
that
was
what
I
thought
you
were
suggesting
as.
C
B
A
A
A
B
A
Okay
and
justin
for
you
and
me
thursday
evening,
is.
D
That,
okay
for
you,
oh
no,
I
actually
have
something
going
on
on
thursday
evening,
but
I
do
want
to
make
sure
that
you
guys
still
make
progress
so
like
I
don't
want
to
hold
people.
A
A
A
A
Rebukes,
okay,
then,
let's
go
ahead
with
justin,
let's
go
ahead
with
thursday
yeah
and
then
so
thursday.
For
you
and
me
friday
for
for
harsh
it
then
next
week-
and
I
guess
we'll
we
can
know-
we-
we
probably
can't
determine
next-
is
this
day
workable
for
everyone
next
week,
so
seven
days
from
now
as
well.
A
A
D
Yeah,
that
sounds
good
and
I
don't
know
if
you
wanted
to
like
chat
separately
like
about
administrative
things
on
that
or
anything
like
that,
happy
to
do
that,
or
we
can
figure
out
how.
However,
we
want
to,
if
there's
anything
else
that
I
need
to
know
about,
but
I
doubt
that
it
very
much
so
these.