►
From YouTube: Jenkins in GSoC 2022, Feb 3, 2022 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
All
right,
hi,
everybody
welcome
to
jenkins
google
summer
of
code
2022
office
hours.
Today
is
my
it's
my
thursday,
so
it's
february
3rd,
but
for
most
of
you,
it's
friday
february
4th
so
before
we
get
started
just
wanted
to
do
a
really
quick
introduction
so
that
you
guys
know
who's
who,
on
this
call
at
the
moment
so
mark
waite
is
our
gsoc
mentor.
A
Chris
stern
is
also
our
gsoc
mentor,
plus
our
org
admin
for
this
year.
Natasha
is
a
mentor
and
I'm
an
arc
admin.
So
I
mean
we
are
recording
this
session,
as
you
saw
so
I
will
put
the
link
in
the
google
doc
after
the
session.
What
else
we
will
start
on
time.
We
will
end
on
time
and
if
you
have
any
questions,
please
feel
free
to
put
them
in
the
chat
window
or
unmute
your
mic
and
ask
your
question.
A
I
put
together
an
agenda,
but
mark
talks
me
out
of
the
out
of
the
agenda
and
said,
given
that
this
is
our
first
office
hour.
Let's
open
this
up
for
a
casual
conversation,
just
ask
questions
of
our
previous
g-stock
students
like
natasha
and
chris,
who
are
now
mentors
and
ask
the
mentors
whatever
it
is
that
you
want
to
ask
so
that
we
can
help
you
in
this
process
of
your
application,
so
I'll
leave
it
as
that.
B
A
A
A
I
had
put
some
just
based
on
some
of
my
digging
around
well
previous
years
office
hours,
gsoc
office
hours.
I
thought
it
might
be
helpful
just
to
add
some
helpful
links
to
our
beginners
or
applicants.
A
Some
helpful
links
here
are
what
was
what
was
the
outcome
of
previous
years?
Just
to
give
you
an
idea
what
to
expect
this
year?
What
are
some
project
ideas
that
we
are
that
has
been
accepted
for
this
year?
How
to
propose
your
project
ideas
where
to
have
an
open
discussion
on
gsoc
and
then
simple
guide
and
how
to
get
started.
A
Okay,
so
I'm
gonna
move
on.
So
please
ask
your
question.
Stop
me
ask
your
questions
anytime,
okay,
so
then
we
will,
let's
start
with
our
discussion
for
the
project
ideas.
The
first
one
is
automates
automatic
specification
generator
for
jenkins
rest
api,
and
I
believe
this
is
marx
and
kristen's.
C
Okay,
cool
yeah,
so
the
goal
of
the
the
kind
of
behind
this
is
that
there's
a
bunch
of
rest
apis
that
are
available
kind
of
a
different
plugins
have
or
core,
and
what
we
would
like
to
do
is
be
able
to
generate
help
pages
and
stuff
on
the
website
automatically
so,
and
we'd
also
like
to
publish
it
kind
of
in
a
format:
that's
easily
consumable.
So
the
open
api
standard,
open,
api,
three
or
sometimes
called
swagger,
but
the
official
ones
open
api
three
just
to
help
document
it.
C
C
We
have
a
kind
of
tool
ready
that
goes
and
generates
the
pipeline
steps
for
the
different
plugins,
so
we'd
probably
be
doing
something
very
similar,
but
focusing
more
on
rest
and
then
being
able
to
kind
of
tie
that
into
how
the
build
is
done
and
then
also
yeah
figuring
out
what
we
want
to
have
for
the
different
http
responses
and
pieces.
I
think
you
can
go
right
currently,
if
you
have
like
a
system
running,
you
can
actually
see
like
the
rest.
C
So
this
is
a
good
introduction
to
being
there's.
It
doesn't
necessarily
have
to
be.
I
say
the
project
probably
will
be
in
java
that
type
of
stuff,
but
there's
a
chance
to
be
able
to
also
work
with
rest
and
be
able
to
figure
that
part
out
so.
B
But
this
is
proposing,
let's
take
it
to
the
next
level
and
comply
with
open
api
three
with
the
swagger
spec
and
have
that
published
separately,
so
that
it's
available
from
the
the
assembly
of
all
plug-ins
and
available
outside
of
a
running
jenkins
instance.
I
I
think
the
project
id
is
really
cool
and
we
would
love
to
have
someone
take
it
up
and
turn
it
into
a
project
proposal
for
the
jenkins
project
in
gsaw.
A
C
Not
necessarily
this
is,
or
at
least
I'd
dig
into
a
little
bit
more,
but
mostly
this
is
just
kind
of
dealing
with
the
plugins
as
they're
already
existing
like
and
the
structure
of
stuff
is
kind
of
the
expected
output
would
be
something
that
could
be
posted,
at
least
to
me,
like.
I
think
that
some
of
it
is
like
documentation
on
the
website
if
we
want
to
also
tie
in
like
open
api
aspire
into
jenkins
itself.
C
As
long
as
it's
able
to
kind
of
be
displayed,
it's
kind
of
working
within
the
framework
of
jenkins
and
then
also
like
on
the
website.
I
would
be
more
like
you're
producing
some
type
of
markup
document,
or
it
could
be
ascii
doc,
but
I
think
markup
be
better,
but
that's
going
to
be
probably
more
of
a
static
piece
and
probably
actually
like
an
actual
open
api
document
that
can
be
posted
on
the
website,
but
no
specific
framework.
B
B
B
B
E
C
I
don't
necessarily
think
so,
because
the
the
stuff
already
kind
of
exists
right,
like
the
whole,
we
want
to,
or
it's
kind
of
his
present.
We
just
need
to
be
able
to
get
the
information.
That's
already
there
so
and
you
do
not
have
to
worry
about
like
installing
a
plug-in
into
jenkins
because,
like
if
you
as
mark
was
saying
like
you
can
actually
go
and
like
see
the
rest
calls
that
are
available
like
in
your.
C
I
don't
have
a
good
example
of
a
thing
that's
running
right
now,
but
I
think
further
in
the
project
details
there's
a
if
you
run
your
own
jenkins
instance
and
pop
it
up.
There's
like
a
url
that
you
can
hit
and
you
can
see
like
what
it
would
be
like
for
your
specific
install.
So
what
we're
kind
of
needing
is
something
that
can
take
what's
already
kind
of
generated.
C
It
might
end
up
being
the
stuff
that
you'd
end
up
publishing
on
the
website
would
probably
be
more
of
just
kind
of
a.
I
would
take
inspiration
for
what
we
do
for
generating
the
pipeline
steps
help
and
I
think,
like
for
getting
this
swagger
piece.
It
might
be
something
that
we
can
try
to
do
with.
I
think
core
is
in
core,
so
you
might
be
able
to
add
part
of
that
stuff
to
core
and
you
wouldn't
necessarily
need
a
plug-in.
B
So
sweat,
I
I
I
would
reinforce
what
what
kristen
said
that
this
is.
This
will
be
a
tool
that
runs
outside
of
jenkins
but
reads,
but
couldn't
can
use
jenkins
source
code
can
use
jenkins
apis
to
generate
a
list
of
or
a
description
of,
the
the
rest
apis
that
are
available,
but
it
actually
isn't
running
inside
jenkins.
Naturally,
the
the
example
that
I
think
kristin
referred
to
earlier,
of
a
possible
idea
of
how
this
might
be
done
was
there's
a
thing
called
the
pipeline
steps,
documentation
generator
and
that
pipeline
steps.
B
B
B
Okay,
so
here's
here's
my
and
you
would
see
this
same
thing
if
you
were
to
run
a
jenkins
installation
yourself
and
you
should
run
a
jenkins
installation,
it's
a
good
thing
to
do
so.
This
is
a
jenkins
installation
running
on
a
public
url
that
I
happen
to
maintain,
and
here,
if
we
look
the
bottom
right
hand
corner
is
this
rest,
api,
hyperlink-
and
this
thing
gives
me
all
sorts
of
really
okay,
here's
the
documentation
describes
this
and
and
oh
by
the
way.
If
you
use
this
these
options
to
it,
you
can
do
this
example.
B
You
can
do
this,
and
so
here
are
all
sorts
of
things
already
available
just
by
navigating,
and
what
this
hints
at
is
that
these
apis
are
discoverable
by
jenkins
itself
and
the
reason
they're
discoverable
by
jenkins
itself
and
generated
by
jenkins,
I
think,
is
because
of
the
stapler
framework
that
goes
around
and
looks
for
them.
Kristin
did
I
describe
that
correctly
or
have
I
missed
something
there.
B
Yeah
the
and
what
this?
What
this
hints
is
that
for
many
many
places
in
jenkins,
I
can
do
exactly
this
and
oh
hey,
there's
xml
data
at
this
level.
It's
telling
me
about
all
sorts
of
labels
on
my
agents
and
all
sorts.
So
so
many
different
levels
have
have
the
apis
available
and
you
can
use
them
directly.
C
C
It's
easier
to
be
able
to
use
the
api
or
kind
of
share,
share
the
document
or
just
kind
of
like
share
the
knowledge
of
like
what
you
want
to
work
on
versus
having
to
you
know,
maybe
parse
the
xml
manually
or
the
json,
and
look
at
it
to
figure
out
what
you're
trying
to
do.
B
A
Sorry,
I
need
to
take
myself
off
mute,
so
the
jenkins
file
runner
action
for
github
actions,
and
this
one
is
chris
and
oleg,
but
chris
this
is
since
you're
here.
This
is
all
yours.
D
D
Yep,
so
our
end
goal
is
to
have
something
similar
to
this,
except
the
content
will
be
all
different,
so
in
the
end
that
would
use
this
type
of
actions
with
your
project
the
same.
So
this
is
what
we'll
see,
and
so,
let's,
let's
take
a
look
here,
so
this
is
quite
like
quite
raw
because,
like
before
we
didn't
have
jenkins
file
runner.
D
Now
we
do
so
so
this
is
like
just
poc,
so
a
lot
has
to
be
changed,
and
this
is
basically
what
what
we
can
do
so,
if
in
case
you're
interested
only
you
should
start
with
this.
D
Maybe
you
can
scroll
faster
to
the
end,
because
it's
just
yeah,
so
it's
just
so
in
here.
We
only
have
one
action
and
I
think
for
in
our
case
we
can
have
like
similar
this
one,
and
this
one
is
one
on
ubuntu.
So
we
for
our
project,
we
can
have
it
run
on,
say,
mac,
linux
and
windows.
D
And
let's
go
back
after
that,
okay,
yeah
and
then
let's
go
back
to
the
approach.
I
didn't
page
okay.
So
if
we
go
to
jenkinsville
in
a
project,
the
type
link
above
what
we
saw
before
so
this
is
what
what's
new
after
the
plc
was
done.
So
this
is
what
we're
based
on
to
to
to
start
our
own,
like
jenkins
style,
runner
action
and
the
last
release
of
says,
as
we
can
see.
D
On
the
right
hand,
side
is
august
thirtieth,
twenty
twenty
first
at
some,
it
has
been
maintained
until
quite
recently,
and
so
if
we
can't
go
all
the
way
to
the
bottom
slowly
so
as
you
can
see
here,
that
is
an
incubating
project,
which
means
it's
it's
quite
brand
new,
it's
it's
still
in
in
incubation
and
for,
if
you
can,
if
you
see
in
in
the
section
titled
usation.com
this
is
only
like
and
and
in
this
repo
it's
only
the
no
distribution
yeah,
it's
going
down
yeah.
D
I
know
okay,
so
you
station
docker
here
and
then
with
this
reversion,
but
we
want
to
extend
this
possibly
to
include
like
all
the
distributions,
as
well
or
instructions
for
other
people
to
follow
to
extend
it
because
we're
like
right
now,
the
the
instructions
are
not
that
complete
and
you
have
to
base
like
outfits
and
to
create
actions
for
github
actions
and
that's
the
basic
idea
of
the
project.
D
So
it's
quite
detailed
here
because,
like
I
think,
oleg
was
working
on
this
before,
like
the
voice
guy
who
changed
so,
as
you
can
tell,
he
put
a
lot
of
time
and
effort
into
it.
So
part
of
your
world
map
is
what,
as
you
can
see
like,
if
that
one
is
what,
if
you're
interested
in
this,
you
can
so
look
at
this
and
see
what
is
in
the
works
and
what's
been
planned
and
also
for
contributing
different
instructions.
So
we
can
see
here
contributing
guidelines.
D
D
Maven
like
what
I
use
for
it
as
3.8.4
device
version,
ide
docker
make,
and
they
also
have
documentation
for
this,
so
it
will
get.
You
started.
D
See
it
develop
documentation
and
building
as
the
most
important
part,
possibly
because,
like
you
want
to
check
out
how
to
do
it.
First,
we've
tested
it
and
we,
I
think,
like
for,
for
this
to
work
to
build
successfully.
You
have
to
do
pseudo
before
like
before
commands
here
so
mv
and
clean
package.
You
have
to
put
soda
in
front
and
for
the
building
dock
images.
I
think
for
the
dock
images.
D
We
have
to
rework
it
a
little
bit
because,
like
for
the
last
time
I
I
checked
it's,
I
needed
some
upgrade
and
debugging.
So
the
picking
guidelines
here
testing
changes.
So
it
tells
you
that
we
can
do
the
test
and
proposing
changes.
That's
this
is
what
we
you.
You
need
to
use
quite
a
bit
if
you
are
like
to
work
on
the
project
idea
because,
like
we,
you
may
need
to
like
submit
all
the
pr's
to
these
people
as
well.
D
I
think
for
continuous
integration,
so
so
job
can
be
seen
like
and
where
it
says
here
like
for
store
and
john's
file.
Possibly
would
so
a
lot
of
the
details
can
be
seen
in
transform.
D
D
Okay
thanks,
so
if.
A
D
To
newbie
this
section
is
assassinated
would
be
so
blank
yeah,
newbie
friendly
issues.
So
if
you
want
to
get
started,
you
can
like
check
out
some
pages
at
this
link
and
for,
as
you
can
see,
like
a
bunch
of
like
issues
how
the
label
feels
good
issue.
So
these
can
get
you
started
and
they
get
familiar
with
the
code
base
here
and
so
yep.
Let's
go
back
and
now,
let's
see
so
skills
to
improve
and
study.
D
So
basically,
it's
based
on
java,
but
doing
good
like
a
lot
of
config
to
be
done
too,
like
including
docker
and
github
actions
and
my
co-manager.
My
potential
commander
is
olac,
but
he's
not
available
today.
So
let's
hope
he
can
show
like
some
other
time
and
for
portrait
things
organization
lines.
These
are
like
the
same
for
all
project
ideas
and
I
think
that's
like
most
of
the
things
I
need
to
cover
any
questions.
B
So
chris
I
like
that
you,
you
pointed
the
the
the
potential
contributors
to
the
the
friendly
issues,
so
they
would
just
pick
up
one
of
those
and
submit
a
poll
request
to
to
work
on
that
issue,
or
they
could
engage
with
us
that
way
already
just
by
getting
involved
and
gives
them
experience
with
the
code
base.
Anything
you
would
suggest
there
or
recommend
of
oh
use,
these
techniques
or
those
techniques
to
to
become
aware
of
what's
happening
in
the
code.
D
Yeah
yeah,
that's
a
good
idea.
It's
like
we
have
a
channel
on
getter
so
well.
We
can
talk
like
through
some
issues
that
first
before,
like
if,
if
like,
if
the
student
or
the
contributor
wants
to
start
an
issue
on
their
own,
they
can
do
that.
We
can
work
together
to
like
to
submit
proquest
that
way.
So
I
can
like
I
can
put
submit
the
finalized
version
or
like
they
can
do
it
themselves,
so
either
way.
A
B
Yeah,
so
so
the
the
jenkins
pipeline
is
a
domain
specific
language
that
is
extended
by
plugins,
as
they
contribute
functionality
to
that
domain-specific
language,
those
plugins
as
they
contribute
that
functionality
can
also
provide
help
and
or
in
many
cases,
not
provide
help,
but
they
can
provide.
They
certainly
provide
keywords:
arguments
that
help
the
that
allow
the
user
of
jenkins
pipeline
to
perform
the
operations
they
want
to
do
in
their
jenkins
file.
B
This
pipeline
step,
documentation
generator
reads
from
the
set
of
all
plugins
that
contribute
these
pipeline
steps
and
formats
their
documentation,
so
that
we
can
present
it
on
the
jenkins
website.
This
project
is
to
search
search
for
ways
that
we
can
improve
the
layout,
the
presentation
and
the
under
the
comprehension
of
of
that
documentation.
B
So
alyssa
on
this
page,
I
want
to
have
you
open
the
most
terrible
horrifying
one
in
the
middle
paragraph.
It
says,
for
example,
when
you
read
the
read
file
step
documentation,
not
that
one,
but
the
next
link
after
when
you
read
the
checkout
documentation,
so
click
that
and
we're
going
to
wait
for
a
little
bit.
Okay.
This
is
an
example
of
of
an
awful
lot
of
information
presented
in
a
rather
difficult
form
to
consumers,
and
one
of
the
things
we
would
like
this
project
proposal
to
consider
is:
how
could
we
do
this
better?
B
B
One
click
expands
into
this
enormous
thing
and
there
are
about
60
other
things
like
this
on
this
page.
So
it's
just
too
much
information
for
one
single
page,
so
the
project
is
to
find
better
ways
to
present
this.
This
kind
of
information
so
that
it's
more
easily
navigated
by
users,
kristin
insights
from
you,
kristen
kristen,
was
the
one
who
was
brilliant
enough
to
create
this
tool.
C
C
So
I
don't
know
like
I
think,
a
lot
of
it
is
going
to
be
figuring
out
how
to
maybe
tweak
it
to
maybe
tweak
the
tool
to
come
up
with
a
better
way
to
generate
the
pages
and
maybe
also
honestly,
like
figuring
out,
maybe
a
better
way
to
display
some
stuff.
So,
but
I
think
there's
a
lot
that-
and
maybe
this
might
also
involve
us
going
or
whoever
is
exploring
this
to
also
go
and
figure
out.
Maybe
how
to
like
improve
some
of
the
documentation
for
the
specific
pieces
that
are
providing
problems.
C
So
maybe
there's
just
better
descriptions
or
even
kind
of
just
helping
figure
out.
What's
going
on
so
you're,
not
ending
up
with
a
huge
page
of
lots
of
things
twisties
to
open
up
that
kind
of
give
all
the
different
options
it
just
might
there
might
be
a
better
way
to
display
it
on
the
page,
so.
B
Yeah,
so
so
for
me,
this
one
has
an
elements
of
not
just
java
design
but
also
web
page
design
and
information
navigation.
It's
it's
not.
This
is
not
just
a
coding
exercise
right.
This
one
is
a
think
about
how
you
would
design
something
that
human
beings
would
enjoy,
reading
and
and
would
have
a
better
layout.
B
B
A
Yes,
one
minute
left,
so
I
will
carry
this
over
to
our
next
meeting.
The
next
meeting
is
going
to
be
friday
well
next
february
10th
and
it's
at
up
2
p.m,
utc
and
mia
time,
and
then
we
will
be
alternating.
So
if
you
are
checking
back
on
the
agenda
of
your,
you
can't
make
it
to
the
mia
time
to
circle
back
up
to
this
document,
and
I
will
have
the
next
meeting
for
asia
and
amia
following
that.
So
thank
you.