►
From YouTube: Mar 17, 2021 Jenkins GSoC Office Hours
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
B
So
I
don't
have
a
just
any
question,
but
I'm
just
I'm
just
saying
sharing
my
progress
so
far,
so
when
I
was
working
with
you
on
the
the
generator
that
generator
for
generating
this
step
pipeline
system
generator,
but
then
I
just
like
some
attracting
what
was
cloud
events
and
from
that
day,
like
I
worked,
I
learned
about
event
driven
architecture
cloud
events
integrated
into
java
sdk
made
a
springboard
api
and
passed
data
all
that
specifications
and
yeah.
B
Now
I
have
to
look
into
two
source
codes
of
the
plugin
to
gather
the
same
idea
of
the
proposed
plugin
to
receive,
and
too
sorry
I
mean
the
listen
and
ambition
so
that
yeah
this
week
I
will
do
that.
Work,
yeah,
so
yeah.
A
C
Hello:
everyone,
I'm
working
on
get
credentials
binding,
plugin.
So
far,
I
am
stuck
at
ssh
bindings
learning,
some
of
this
and
right
now
I
mark.
I
need
some
assistance
in
understanding
the
rationale
of
ssh
bindings
like
there's
a
problem,
not
a
problem,
but
the
thing
is
the.
As
per
the
issues
in
the
ideas
page,
it
was
mentioned,
like
you
have
to
find
the
file
of
passphrase
into
a
non-passphrase
kind
of
file
like.
A
C
Thing
bugs
being
like,
how
does
it
goes
around
and
what
is
the
behind
the
scenes
working
should
be
like
that.
A
Okay,
that
sounds
like
a
a
good
topic
for
a
discussion
here,
so
get
credentials
binding
and
credentials
binding,
and
how
would
it
work.
A
Good
all
right
do
we
want
to
just
dive
into
that
right
away,
so
we
can.
We
can
look
at
it
together
or
are
there
other
topics
that
people
want
to
get
on
the
list,
so
we're
sure
we've
got
I.
I
have
a
hard
stop
in
about
25
minutes,
so
so,
for
me
at
least,
I
will
need
to
pass
off
hosting
to
someone
else
if
we
run
out
if
we
run
have
more
topics
than
we
have
time.
A
All
right,
let's,
let's
take
a
look
at
it
so
ayan
it
was
it
was
you
wanted
to.
You
were
looking
at
well,
maybe
maybe
it's
best.
Let
me
share
my
screen
and
we
can
look
at
the
at
the
description
and
then
you
can
tell
me
which
part
is
unclear
and
we
we
go
further.
There
is
that
okay
or
do
you
want
to
share
your
screen
either
is
fine.
Yes,.
C
The
in
the
the
part
where
the
shs
private
key
was
mentioned,
username
password,
was
very
much
clear.
Like
there
was
simple,
username
password,
you
have
to
do
that
and
all
the
execution
commands
the
user
will
do
the
get
authenticated
commands.
The
pipeline
user
will
work
on
the
kit.
It
will
be
okay,
it
was
simple
to
bind
that
environment
variables
and
pass
them
to
the
command
line,
but
the
in
the
sss
private
key.
There
was
a
term
in
the
rational
with
the
passphrase
and
without
passphrase.
When
there
was
a
with
fast
phrase.
C
We
have
to
create
a
file
and
like
in
the
jenkins
environment.
It
should
be
like
by
the
either
it
would
be
password
using
a
passphrase
or
not
a
passphrase,
but
with
a
fast
phrase
a
file
should
be
created
such
that
the
ssh
private
key
can
use
without
passphrase
things,
and
that
thing
like
a
little
bit
unclear
to
me
like
what
is
going
on
with
that
like
I,
as
I
am
a
you
get
user,
I
do
you.
C
I
personally
use
sss
private
ssh
keys
and
once
I
set
up
a
space,
I
don't
need
to
set
it.
Give
the
passphrase
or
any
time
mode,
but
what
it
is
exactly
like
in
jenkins.
A
Good,
okay,
very
good,
so
I
think
what
you're
saying
is:
how
does
what's
the
concept
to
allow
this
credentials
binding
idea
to
to
do
passphrase,
protected,
ssh,
private
keys,
and
I
might
shift
it
and
offer
the
the
suggestion
that
jesse
glick
offered
what
jesse
suggested
was
hey,
probably
better
than
writing
the
passphrase
onto
the
local
agent
onto
the
agent
would
be
use.
The
passphrase
inside
the
plugin
make
a
call
to
an
appropriate
java
library
that
will
decrypt
the
private
key.
A
That's
passphrase
secured,
so
it
is
no
longer
pass
rate
secured
and
then
write
the
the
the
credent,
the
private
key
to
the
agent.
That
is,
with
that
private
key
not
being
protected
by
the
passphrase.
So
the
idea
was
jesse's.
Suggestion
was
hey:
let's,
let's
shift
the
processing
of
the
passphrase
away
from
having
it
done
on
the
agent
and
instead
do
it
on
the
controller
and
then
pass
the
decrypted
passphrase
or
the
decrypted
private
key
to
the
agent.
So
that
way
you
avoid
having
to
write
the
the
passphrase
to
the
agent.
A
You
avoid
the
problem
of
trying
to
manage.
How
do
we
get
the
information
about
that
passphrase
down
to
the
agent?
Now
it
means
you
do
have
to
find
a
way
to
convert
a
passphrase
protected
private
key
to
one
that
is
not
passphrase
protected
in
in
java,
but
jesse's
indication
was
that
those
facilities
should
be
available.
C
It's
kind
of
like
either
it
be
a
passphrase
protected
or
not
passwords
protected.
We
have
to
convert
it
to
a
not
protected
kind
of
thing
and
jenkins
will
work
on
it
as
it
is
like
jenkins
in
junkies,
we
store
our
credentials
in
using
credentials
plugin,
I
am
not
sure
of
the
name.
C
It
is
jenkins
creation
plugin,
I
guess
so
like
we
can
store
the
passwords
in
some
kind
of
other
file
and
convert
the
using
the
passphrase
convert
that
private
key
file
to
a
non-prospect
protected
file
in
the
workspace
or
the
agent
controller.
As
you
said,
kind
of
like
that.
A
Close
right,
so
it's
that
that
the
credentials
plug-in
continues
to
be
the
thing
that
owns
the
the
passphrase
protected
private
key
and
it
knows
the
passphrase,
and
it
knows
the
private
key
and
inside
the
plug-in.
What
you
would
do
is
use
the
passphrase
and
use
the
press
phrase
protected
private
key
to
generate
a
new
private
key,
a
private
key.
That
is,
that
private
key
decrypted.