►
From YouTube: GSoC 2021 Git credentials binding 2021 05 19
Description
Google Summer of Code mentoring session for the git credentials binding project
A
C
Okay,
I'm
rishabh.
I
am
a
back-end
developer.
You
know
I've
been
working
for
almost
a
year
now
I
was
a
gsoc
student
last
year,
the
same
for
the
same
plug-in
gate
plugin.
My
project
was
related
to
performance,
improvement,
mark
and
justin
were
my
mentors
and
I
had
a
really
great
experience
with
them.
Great
learning
experience.
D
Justin
you
want
to
go
next:
yeah
justin
moringa,
I'm
a
little
bit
of
a
chameleon.
I
guess
my
current
I've
done
front
end
back
end
and
I
guess
I'm
more
ci
cd
these
days,
but
have
a
lot
of
time
on
like
working
through
jenkins,
project
and
stuff,
like
that
I've
open-sourced
some
plugins
and
helped
submit
some
prs
to
existing
plugins.
This
will
be
my
third
g
sock
for
jenkins
and
yeah.
D
It's
good
times
like
the
echo
over
shop
last
year
was
excellent
and
it
was
great
working
with
the
two
of
you
and
looking
forward
to
working
with
you
also
hardship.
A
Thanks
justin
and
I'm
mark
wheat,
I'm
I'm
a
longtime
jenkins
user.
I've
been
the
maintainer
of
the
jenkins
one
of
the
maintainers
of
the
jenkins
git
plug-in
and
get
client
plug-in
for
probably
six
or
seven
years
and
been
involved
with
jenkins
longer
than
that
discovered
that
you
did,
you
don't
have
to
be
brilliant
to
help
with
important
plugins
and
you
don't
have
to
be
especially
great
as
a
programmer.
But
it's
wonderful
to
be
part
of
a
community
that
lets
me
do
things
and
and
learn
things
and
grow.
A
So
this
time
is
an
excellent
one
to
introduce
students
to
the
community,
get
them
on
the
right
mailing
list
working
with
their
mentors
on
their
timeline
for
the
summer
etc.
So
I
think
of
this
as
planning
and
and
preparation
and
getting
to
know
each
other
and
identifying
processes
we
should
use
rishab.
Maybe
you
can
share
some
of
the
things
we
learned
from
from
our
last
time
of
places
where
community
bonding
wasn't
as
wasn't
as
as
perfect
as
we
would
have
liked
or
things
you
say.
C
Oh
yes,
that'd
be
great.
So
for
me,
when
I
started
community
bonding
was
more
about,
I
would
say,
being
comfortable
with
the
mentors
and
establishing,
I
would
say,
an
open
communication
channel
with
them
being
comfortable,
asking
doubts
and
understanding
the
plugin.
I
and
I
mostly
spent
my
time
actually
since
my
project
was
more
research
based.
C
I
I
was
spending
my
time
doing
that
during
the
community
morning
period,
and
my
assumption
was
that
I
cannot
make
a
good
design
proposal
or,
I
would
say,
a
design
plan
for
my
project
because
I
don't
I'm
not.
I
just
don't
know
what
I'm
going
to
code
right
now,
because
I
don't
my
pro
my
in
my
specific
case,
it
was
imperative
that
my
research
shows
something
which
will
actually
give
us
the
the
blueprint
of
what
we
want
to
code.
C
So
so
because
of
that,
I
did
not,
I
would
say,
use
the
community
bonding
period
to
foresee
or
plan
how
my
development
experience
is
going.
My
development
plan
is
going
to
be
for
the
rest
of
the
gsa
and
that,
I
would
say,
got
us
into
some
issues
at
later
stages.
C
So
what
I
would
suggest
is
planning
is
definitely
a
major
part
of
the
community
bonding
people.
First
is
yes,
I
I
would
say
the
priority
would
be
set
like
be
comfortable
with
the
mentors
with
the
community.
Try
to
understand
the
code
base.
If
you
already,
I
am
sure
you
must
have
looked
at
some
part
of
it.
C
If
you
have
doubts,
ask
that
regularly
you
can
you
can
ask
anything
from
everything,
don't
don't
hesitate
and,
and
then
I
would
say,
plan
planning
is
really
essential
at
this
stage
it
might
seem,
like
you
know
we
could
the
the
proposal
we've
sent
or
you've
sent
and
the
at
this
stage
might
might
you
know
you
could
start
with
that,
but
I,
I
would
say
just
discuss
now
that
you
have
more
time
the
mentors
are
going
to
give
you
more
time.
You
should
discuss
that
extensively
and
come
up.
C
A
design
document
is,
is,
I
would
say,
the
preferable
preferable
way
to
go.
That
makes
sense.
A
So
hashid
I've
I've
started
a.
I
realized
that
I
hadn't
started
meeting
notes
for
this
session,
so
I'm
going
to
share
a
screen
with
with
meeting
notes
on
it
and
let's
go
through
and
we'll
just
I've
already
captured
some
of
the
things
that
that
rashab
had
noted.
Let's
go
through
that
and
we'll
we'll
talk
about
it
together.
A
Yeah.
Okay.
Sorry,
yes,
that's
that's
that's!
This
is
me
trying
to
get
get
on
the
ball
here,
okay,
so
so
what
we
could
do
is,
I
think,
reshab
already
highlighted
a
good
thing.
We
could
review
the
project
plan
and
have
our
talk
through
the
project
plan
as
already
identified,
so
that
we
could
just
have
a
conversation
about
it,
discuss
it
here
that
that
might
be
one
very
good
thing
to
then
allow
harsha
to
to
form
a
deeper
plan
or
answer
questions.
A
One
of
the
things
that
richard
noted
also
was
identifying
the
work
to
be
done
during
the
project
and
for
me
this
one
is
particularly
complicated
in
testing
and
validation
because
of
the
the
many
different
places
that
we've
got
a
many
different
things.
We've
got
to
check
so
I
was
thinking
we
talked
about
implementation
and
talk
about
testing.
Both
are
there
other
topics
that
any
of
you
would
like
to
put
on
the
list.
As
for
today,
I
and
I
apologize.
C
I
I
have
an
idea
mark
and
justin:
could
you
validate
it?
So
I
I
think
I
did
not
re
at
the
time
I
was
starting.
I
did
not
know
the
development
life
cycle
of
you
know,
creating
a
feature
coding
it
and
then
testing
it
and
then
finally
pushing
into
production.
C
I
I
don't
know
if
it's
feasible,
but
would
it
be
possible
that
we
give
her
a
small
task
which
can
be
a
feature
or
could
be
I'm
sure
he
is
fix
some
bugs.
But
the
point
is
that
if
he
is
able
to
code
that
plan
code
test
and
deploy
it,
maybe
he
would
understand
how
much
time
he
has
to
keep
while
he's
planning
for
a
feature,
a
simple
feature
to
go
into
production,
because
that
is
something
I
I
could
say
I
underestimated.
C
A
Good
that
that's
a
that's
a
good
idea,
so
harshit
had
come
submitted.
A
he'd
submitted
a
fix
for
jenkins,
38
699
in
pr
1064
and
and
that
one.
B
So
that
issue
was
regarding
the
the
deletion
of
the
files
that
was
caused
due
to
youtube
plug-in
v
ws
clean
up,
plug-in
hangers.
A
Right,
exactly
and
and
but
there
were,
there
were
complications.
If
I
remember
correctly
in
that
one,
when,
when
exploring
okay,
what
do
we?
What
do
we
do
with
it?
How
do
we
fix
this?
How
do
we
test
it?
At
least
for
me,
there
were
a
number
of
things
I
had
to
do
in
investigating
it
to
see.
Oh,
what's
going
on
because
so
derived
from.
A
692.,
so
so
it's
I
think,
richard's
got
a
good
suggestion.
Should
we
should
we
put
you
on?
Should
we
identify
something
where
hey
as
a
first-time
contributor
take
this
other
thing
also
through
to
all
the
way
to
production,
or
are
you
already
comfortable
how
shoot
that
that
you
think
you've
got
a
handle
on
how
the
workflow
operates
in
the
jenkins
community.
B
A
So
then,
that
that
may
be
a
better
choice
than
then
that's
a
good
thing
to
to
be
doing.
In
addition
to
the
planning,
I
like
that
very
good,
okay
reshab,
were
there
any
any
specific
tasks
that
you
had
in
mind,
as
you
think
about
things
that
helped
you
learn
or
or
prepare
better.
Were
there
specific
things
that
you
thought?
Oh
hey.
This
was
a
good
class
of
issue,
or
this
was
a
good
type
of.
C
So,
as
far
I
remember
correctly
during
the
community
bonding
period,
I
was
I
was
working
on
working
on
some
bugs.
I
remember
so
for
me,
the
most
I
learned
by
the
the
source
code
for
git
plugin.
I
I
learned
mostly
while
creating
unit
tests
for
some
of
the
cases,
so
the
bugs
I
was
fixing.
C
I
would
have
to
look
through
them,
but
the
point
is
that
the
mostly
my
learning
experience
on
the
exploration
phase,
where.
C
During
solving
friendly
issues
and
writing
unit
test
cases
for
them,
yeah,
I
would
say
I'd
say
that's
how
I
like
the
jenkins
architecture.
I
I
think
there
was
a
limited
it's
I
think
it's
a
huge
thing
to
commit
to,
but
I
I
think
I
I
learned
is
as
much
context
would
require
for
me
to
do
my
project.
I
would
say.
C
And
yeah,
I
think
I
would
need
to
think
more
about
that
mark.
What
were
the
issues
which
actually
helped
me?
I?
I
could
probably
list
some
of
them,
which
had
because
I
specifically
remember
that
writing
unit
tests
was
very
helpful
because
I
got
to
know
you
know
certain
jps.
B
Also
like,
I
would
like
to
add
something
so
the
issue
that
I
am
currently
facing
in
the
planning
phase
the
web
need
is
the
ui
implementation
that
how
I
will
be,
how
will
the
user
interact
with
the
the
code?
I
mean
the
feature
that
I
am
providing
in
the
pipeline
job.
A
Okay,
good
all
right
well,
so
so
that
that
is
a.
How
will
the
user
interact
interact
with
the
credentials
binding.
D
And
there's
a
few
good
guides
of
plug-in
development
too.
I
wonder
and
I
could
link
those
to
you
if
that's
helpful,
but
that
those
might
help
you
kind
of
figure
out
some
of
these
things.
If
you
haven't
seen
them
before
you
perhaps
you
have,
I
know
docs,
don't
always
tell
the
whole
story
so
sometimes
getting
your
hands
dirty
is
helpful.
D
A
A
Different
controls
that
are
available
in
a
in
in
the
ui,
let's
see
so
no,
not
that
we
want
the
archetypes
there.
We
go
this
one,
so
this
one
has
and
how
do
you
do?
How
do
you
get
started
by
if
you
wanted
to
create
a
brand
new
plug-in
now
I
don't
think
in
this
case
we're
creating
a
brand
new
plug-in,
although
that's
that
may
be
possible.
A
D
Page,
I
don't
know
if
it's
linked
to
from
that
other
tutorial,
but
that's
also
a
really
good
one.
C
And
I
just
remembered
mark
you
shared
two
very
good
documentations
with
me,
related
to
sc
scm,
api,
consumer
guide
and
scm
api
implementation
right.
Those
were.
A
Yeah
and
now,
but
now
because
harsher's
work
is
actually
not
around
the
scm
api,
I'm
not
sure
that
that
that
will
actually
help
him
as
much
as
we
might
have
wanted
it
to
because
harshit's
ish
harshit's
task
is
to
work
in
the
credentials
binding
and
to
create
the
environment
such
that
it
can.
We
can
use
credentials
binding
with
command
line
git,
so
scm
api-
actually,
I
think,
is
probably
not
going
to
be
involved
for
him.
C
A
Credentials
binding
this
was
the
is
at
least
how
the
original
idea
was
modeled,
that
the
user
would
do
a
with
credentials
and
then
the
argument
would
be
some
sort
of
a
get
thing
here:
a
git
username,
password
and-
and
I
think
that
was
also
in
your
project
plan-
that
that's
how
you
envision
it.
Are
you
still?
Okay
with
that,
as
as
the
idea
of
how
we
approach
it.
B
A
A
A
A
A
A
Interesting
happy
scope,
yeah,
except
that
they
are
all,
or
at
least
a
number
of
them
are
okay.
So
I
don't
understand
why
this
is
is
doing
what
it's
doing,
but
I
was
assuming
this
would
be
the
user
experience,
ignoring
the
fact
that
I'm
surprised
that
my
that
I
don't
have
credentials
id
is.
Is
this
matching
what
you
were
expecting
harshad
or
is
there
something
else
that.
B
B
A
B
B
B
A
A
B
A
E
F
C
Are
you
sharing
this
video.
A
I'm
not
yet,
oh,
I
should
shouldn't
I
because
until
harsh,
it's
ready
with
the
second
we
can
be
staring
at
this,
so
here
were
some
of
the
things
that
we
had
suggested
before
update
biography,
and
I
think
that's
already
been
done.
Actually
I
think
hushed
has
submitted.
A
A
C
We
should
do
because
it's
it's,
I
think
it's
a
precursor
to
writing
blogs
after
each
phase.
We
do
that
in
a
dog
right
right,
so
I
think
it
will
be
a
good
exercise.
A
C
A
Well-
and
I
think
that
I
think
that
harshit's
tasks
are
are
much
less
recess
resource
research
loaded
than
yours
were
right.
We
don't
have
a
question
about
which,
which
implementation
path
should
we
take
at
least
not
nearly
the
same
level
as
as
we
had
with
yours,
because
yours
was
run.
A
bunch
of
benchmarks
perform
a
bunch
of
a
bunch
of
performance
tests
before
deciding.
C
A
Could
even
do
okay
now,
that's
an
interesting.
We
don't
really
have
an
upcoming
release
of
the
get
plug-in
to
test
and
these
things
yeah.
I
don't
think-
and
if
I
remember
correctly,
I
that
one
might
be
but
see,
I'm
not
sure
that
unit
tests
for
the
git
client
are
as
useful
to
to
harshit
as
they
would
have
been
to
you
just.
C
Yes-
and
I
think,
would
be
better
that
he
spends
time-
I
think
two
things
first
would
be
to
understand
the
code
in
second
exploring
designing
the
doctor
creating
the
design
document.
I
think
through
that
process
we
would
get
a
lot
of
doubts
and
concerns
and
a
direction
to
do.
A
F
A
B
A
B
B
D
B
D
I
go
ahead
and
just
you
would
have
that
kind
of
block
either
in
pipeline
script
here
or
it
would
be
in
get
right,
as
opposed
to
it
being
like
kind
of
a
checkbox.
B
A
A
C
A
A
A
A
A
This
is
reminding
me
when,
when
I
created
the
project
idea,
I
probably
should
have
created
a
video
to
go
with
it,
because
so,
when
you
click
sample
step
and
look
down
to
the
alphabetical
list,
one
of
them
will
be
with
credentials.
And,
of
course,
none
of
the
rest
of
us
can
see
it
because
we're
not
seeing
your
drop
down
menus.
A
D
A
D
D
D
Yeah
so
basically,
like
those
snippets
are
helpful
for
putting
them
into
that
that
box
that
we
saw
or
putting
them
in
git.
I
think
a
lot
of
people
end
up
having
this
in
git
and
then
git
is
just
pulling
the
pipeline
stuff,
but
this
is
a
simpler
way
of
looking
at
this
without
having
to
know
all
that
other
stuff.
For
now,.
A
A
I'm
sorry
you
say
that
again
har
I
missed
it.
I
have
not
added
the
credentials
yeah
you
have
this.
You
see
the
same
surprising
thing
that
I
see
so
don't
worry
about
that.
It's
harmless!
For
now.
I
suspect,
there's
a
bug
in
the
credentials
binding
plug-in
that
it
should
be
showing
us
something
there
and
it's
not
so
type
in
a
a
name
for
the
username
variable.
A
B
D
So
the
good
news
is
that
simplifies
things
for
you,
because
some
of
the
plumbing
and
stuff
is
kind
of
handled
for
you.
So
some
of
the
pipeline
integration
guide
stuff
will
help.
You
figure
out
how
you
can
get
this
to
work
and
what
this
ends
up
doing
is:
there's
there's
some
stuff
that
you
can
do
across
both
pipeline
jobs,
but
as
well
as
with
regular
freestyle
jobs
where
people
do
have
all
those
check,
boxes
and
drop
downs
and
all
that
stuff.
D
Typically,
the
freestyle
jobs
are
where
you,
you
would
see
more
like
drop
downs,
and
things
like
that
and
people
would
use
the
credentials
binding
plugin
in
those
kinds
of
jobs,
but
pipeline
jobs
typically,
is
all
all
pipeline
all
the
time
for
the
most
part.
In
fact,
some
of
those
check,
boxes
and
stuff
end
up
being
populated
by
pipeline
stuff
in
here
after
you've
run
a
job
for
a
weird
reason.
D
F
A
A
D
D
A
A
Okay,
I
don't
see
anything
that
looks
like
in
a
freestyle
job.
I
could
use
credit
so
justin.
Maybe
we
could
have
you
share
your
screen
and
show
how
that
might
work
in
in
a
freestyle
project,
because
that
that's
a
that's
a
surprise
to
me,
I
was
my
mental
model.
Hadn't
had
didn't
even
have
a
place
for
it
to
be
done
in
freestyle.
A
A
A
And
I'm
probably
looking
for
something
that
calls
itself
a
something
about
credentials
binding
or
is
it.
D
A
We
could
do
inject
environment
variables.
D
Incorrect
here
trying
to
think
what
that
is,
I
can
I
can
look
into
that
and
see
if
I
can
find
it
and
then
maybe
next
time.
D
A
All
right
so
action
items.
D
Very
possible:
I'm
confusing
this
with
another
thing,
so
I'll
look
into
that.
A
They
won't
actually
that's.
That
was
my
assumption
from
the
outset
is,
if
you,
if
you
want
to
use
authenticated
command
line,
git
operations,
you
must
use
pipeline.
So
so
my
working
assumption
from
the
all
and
from
the
very
beginning
was
this
is
only
available
through
this
project
would
only
do
only
add,
authenticated
git
operations.
C
A
Well,
so,
and-
and
that
was
that's
much
bigger
than
the
scope
that
that
the
project
idea
had
had
envisioned
so
so
it
certainly
could
be
done.
I
just
don't
know
then
we've
then
we've
truly
got
the
problem.
That
harshit
was
describing.
How
does
how
do
we
add
a
user
interface
that
allows
the
user
of
a
freestyle
job
to
interact
with
an
authenticated
git
operation.
D
D
Research,
there
sorry
rabbit.
C
Yeah
but
but
then
the
question
I
have
is
that,
if
we're
not
looking
into
that
because
of
the
score
pieces,
but
in
our
current
user
base,
how
many
people
are
creating
freestyle
jobs?
Do
we
have.
A
A
A
Rishabh
had
suggested
it
would
be
easier
for
him
if
we
met
one
hour
later
harshu.
Would
it
be
okay
with
you
if
we
met
one
hour
later
and
my
next
question
is:
could
we
meet
again
tomorrow
at
this
this
time
plus
one
hour
so
basically
right
now,
tomorrow,
night,
so
that
we
could
before
I
leave
on
vacation,
we
could
have
at
least
had
two
sessions
together.
A
B
A
A
Okay,
and
is
tomorrow,
okay
for
you:
yes,
it
is
okay
and
are
likewise,
yes,
okay,
so
I
will
schedule
a
succession
for
tomorrow
and
we'll
continue.
A
Great
okay,
so
tomorrow
same
time
and
talk
to
everyone
tomorrow,
then
thank
you
and
sorry
for
the
the
quick
end,
thanks
very
much
harshit,
it's
so
great
to
have
you
on
the
project
looking
forward
to
to
what
we're
going
to
do
together.