►
Description
Jenkins Online Meetup: Jenkins in Google Summer of Code 2022
February 23, 2022
00:00 - Introduction
01:34 - Agenda
02:10 - Intro to Google Summer of Code
03:05 - Jenkins in GSoC 2022
09:44 - Project Ideas
22:32 - Project Presentations by Mentors
22:58 - Automatic Git Cache Maintenance
24:30 - Automatic Spec Generator for Jenkins REST API
26:18 - Jenkinsfile Runner Action For GitHub Actions
27:41 - Pipeline Step Documentation Generator
28:51 - Plugin Installation Manager Tool Improvements
30:09 - Plugin Health Scoring System
32:28 - Jenkins Config as Code (JCasC) Drift Detector
A
A
A
Some
housekeeping
notes
before
we
begin.
Please
put
your
questions
in
the
chat
window.
One
of
our
speakers
will
respond
to
your
question
throughout
the
presentation
this
session
is
being
recorded.
We
will
share
the
link
on
the
meetup
page
later
today
and
if
we
can't
get
to
your
question-
or
you
have
questions
after
the
session
feel
free
to
drop
a
note
or
your
questions
in
the
getter
or
the
community
community
discourse
channel,
and
we
will
respond
to
it
there.
A
A
A
A
A
A
A
A
The
project
types
that
we
offer
are
key
initiatives
to
jenkins
goals,
such
as
configuration
as
code
plug-in
improvements
and
jenkins
pipeline,
just
to
name
a
few,
so
these
projects
actually
do
yield
a
high
value
to
the
community
in
general.
So
what
this
means
is
that
your
contributions
are
benefited
by
jenkins
users
as
a
whole.
C
Yes,
thank
you
so
first
this
gives
you
an
idea
of
what
the
projects
were
that
were
selected
last
year
and
that
reached
a
successful
end.
I'm
not
going
to
explain
them
because
today,
because
we
have
a
lot
of
other
topics
that
we
want
to
and
explain.
The
current
projects
have
a
look
to
the
history,
so
the
the
archives
browse
through
it
get
ideas,
look
how
they
were
conducted
there
before
going
to
the
next
slide.
I
just
want
to
explain
just
to
be
sure
that
everyone
understood
it.
C
What
we
call
office
hours
is
that
we
have
a
meeting
every
week
at
a
regular
cadence,
where
it's
just
open
for
at
least
half
an
hour
and
where
you
just
come,
and
either
we
have
some
organized
topics
there.
But
at
least
this
is
the
watering
hole
where
you
can
come
to
ask
questions
and
and
see.
What's
what's
going
on,
where
you
have
an
interactive
way
of
dealing
and
we
we
have
them
flipping
a
time
time
zone.
C
So
we
have
one
that's
more
oriented
for
asia
and
the
other
one
more
europe,
asia,
europe
middle
east,
in
africa,
the
time
zone
next
slide.
Sorry
for
that
the
explain,
but
I
I
thought
it
was
important
the
beginning,
I
didn't
know
what
an
office
hour
was
so
here
these
are
some
pictures
of
last
year's
or
previous
year's
experiences.
C
One
of
the
things
that
I
find
very
great
is
that
the
successful
contributors
get
invited
to
the
annual
devops
devops
world
conference
and
have
a
chance
to
present
their
their
project
to
the
community
and
interact
with
with
a
lot
of
people
and
in
well.
This
is
an
interesting
reward
and
the
picture
below
is,
I
think,
I'm
not
sure
of
that.
I
think
this
was
one
of
the
the
reunion
of
the
various
candidates
at
the
google
campus.
I'm
not
sure
at
all
that
this
will
take
place.
A
A
All
right
so
how
to
apply.
So
if
you
go
to
this
link
here,
it's
go
all
the
way
up,
so
this
site
is
really
helpful
in
walking
you
through
the
application
process
and
setting
correct
expectations
before
the
the
the
program
and
actually
for
the
entire
program
itself.
It
contains
a
lot
of
helpful
links
to
all
things,
jenkins
and
gsoc
tips
and
important
information
to
keep
in
mind
during
the
program.
A
This
template
is
just
a
suggestion,
so
you're
welcome
to
use
your
own
template.
We
also
recommend
that
you
don't
wait
until
april
to
start
working
on
your
application.
Start
writing
your
proposal
much
sooner
so
again
to
solicit
feedback
and
encourage
potential
mentors
to
help.
You
make
a
a
better
proposal
for
yourself
for
for
google,
okay
and
then.
C
Yes,
so
well,
you
can
have
a
look
to
the
to
the
url.
That's
that's
there.
Maybe
if
listen,
you
can
click
on
the
link
just
so
that
we
we
see
it
so
just
browsing
through
it.
You
will
see
that
there
are
three
categories
of
projects
and
let's
go
back
to
the
presentation,
so
we
have
the
overview
there.
So
the
the
first
and
more
mature
project
is
the
approved
one.
That
means
that
a
project
has
been
fully
qualified
is,
is
defined
and
ready
to
fly
draft
projects.
It's
still
ongoing.
C
There's
some
discussion
and
refinement
going
going
on
these
projects
and
there's
currently
only
one
there
they're
fine
to
apply.
So
you
can
start
already
preparing
your
epic
application
for
these
kind
projects
under
discussions.
There
are
currently
two
in
that
there
are
still
discussions
going
on
on
scope,
feasibility
and
you're
you're
you're
invited
to
join
the
discussion.
If
you
have
ideas
but
be
cautious
because
we
we
didn't
have
we
don't
have
mentors
for
them
for
sure
or
it's
still
underway,
so
listen
carefully.
C
C
C
Start
writing
early.
Well,
most
of
you
have
been
in
higher
education,
so
they
know
the
earlier.
You
start
the
better
chances
your
chances
are
to
reach
a
successful
and
quality
end.
So
don't
wait
the
last
day
to
to
do
and
submit
draft
proposal
make
them
available
to
the
community,
publish
them
via
getter
or
discourse.
So
so,
how
you
do
that
you
create
a
google
document,
you
prepare
it,
and
then
you
say
here:
this
is
the
first
iteration
on
my
draft.
C
Put
someone
have
a
look
to
it,
make
comments,
and
so
now
this
is
something
important
in
one
and
you'll
you'll
discover
many
other
differences,
one
of
the
the
the
things
that
makes
working
on
open
source
different
than
what
you
used
to
do
at
at
university
or
others.
Where,
generally
you,
you
keep
the
work
for
yourself,
you're
working
on
your
own.
C
You
share,
there
is
cross
polarization.
Even
people
can
take
some
of
your
ideas.
It's
part
of
these
this
this
of
the
process
to
have
these
ideas
flowing
and
move
and,
and
one
builds
on
on
the
other.
So
don't
be
afraid
of
it
and
saying
afraid
is.
I
know
it
takes
some
courage
to
put
a
work.
That's
not
exactly
at
your
quality
standards
openly
in
the
world
and
say
what
are
people
going
to
think?
C
No,
and
particularly
the
jenkins
community,
and
we
as
org
admin
and
the
mentors,
have
the
same
attitude,
we're
there
to
help
and
we're
a
friendly
community
and,
don't
be
afraid,
don't
be
shy.
We're
here
to
work
together
to
make
this
experience
successful.
So
don't
be
shy,
don't
be
afraid
to
to
share
that
discussing
and
reviewing
a
document
openly
is
part
of
the
experience
is
part
of
working
on
open
source
and
one
of
the
things
we
would
like
to
share
with
you.
C
C
So
I
I've
seen
a
lot
of
questions.
How
do
we
start
we're
eager
you're,
like
horses,
ready
to
start
the
the
the
race
start
as
soon
as
possible,
understand
the
subject
that
you're
interested
in
explore
it
get
acquainted
and
expl
and
get
practical
experience
on
jenkins
on
the
ecosystem,
how
the
community
works
get
familiar,
also
with
the
pull
request
methodology
and
how
all
this
works.
C
This
is
the
very
good
time
to
get
these
muscles
flexed
and
to
to
get
experience
in
that
by
doing
that
exercise
interacting
with
people
getting
ideas,
you
will
build
up
the
knowledge
in
order
to
to
do
a
powerful
submission
for
that,
so
we
can
move
to
the
next
slide.
If
there
are
questions
mark,
you
will
have
to
yeah.
C
B
C
C
It
really
depends
on
what
is
your
experience
with
the
tool
if
you
just
heard
about
it
and
and
had
one
demo,
a
quick
demo,
it's
very
important
that
you
have
a
good
understanding
of
the
various
components
that
you
see
how
it
looks
like
how
you
work
with
it.
So
at
least
you
should
install
your
own
jenkins
instance,
somewhere
on
on
the
laptop
or
or
whatever
configure
it
and
have
a
pipeline
for
a
regular
build
so
build
one
of
your
projects
on
it.
C
Okay,
the
last
the
last
thing
I
want,
if
you
get
stuck,
if
you
don't
know,
you
don't
know
what
I'm
talking
about,
or
what
rd
this
concept
come
to
the
office
hours.
Ask
your
questions.
You
have
the
asynchronous
ways
of
of
using
the
various
communication
channels.
We
are
don't
stay,
stuck
stuck
shy
in
your
corner
and-
and
I
don't
know
how
to
do
that-
try
to
find
it
myself
ask
for
help
we're
together
in
this
adventure
mark.
C
C
The
mentors
in
org
admin
for
jenkins
are
then
going
to
select
in
the
various
applications
who
will
join
the
next
step
of
the
the
adventure
and
their
contributors
will
be
announced
on
may
20
at
that
day.
So
once
we
reach
that,
then
we're
okay.
We
rejoice
and
I'm
okay,
sorry
for
the
people
that
were
not
selected
and
there
will
be
other
opportunities.
C
The
next
step
is
that
we
we're
going
to
start
what's
called
the
community
bonding
period.
It
means
that
you
will
then
get
into
contact
and
build
the
relationship
with
your
mentors
and
you're
going
to
see.
Oh,
how?
How
is
this
going
to
work?
How
so
there
there
will
be
quite
some
some
meetings
and
discussions
so
that
you
you
get
warmed
up
and
the
actual
coding
is
is
starting
on
june
30.
C
and
what
happens
afterwards
and
how
it's
organized.
You
will
hear
from
your
mentors
and
we'll
do
other
sessions
to
coach
you
there.
An
important
thing
is,
I'm
not
sure
in
the
submission.
I
don't
think
that
there
is
a
question
there,
but
generally
don't
forget
to
state
and
discuss
what
are
your
availabilities
during
the
summer.
C
I
would
recommend
adding
it
to
the
submission
form
as
as
a
note
meaning
that
if
you
have
obligations
during
your
summer,
if
you
still
have
end
of
term
papers
to
write
or
or
or
you're
going
to
get
married
or
whatever
important
things
where
you
will
not
be
able
to
focus,
as
you
would
like
on
on
this,
let
us
know
so
that
we
can.
We
can
eventually
organize
and
see
that
that
the
mentors
are
available
or
I'm
not
waiting
for
you,
while
you're
away.
C
So
so
we
need
to
organize
this
this
period
and
it's
okay
to
say
that.
Well,
no,
I
I
have
a
work
for
university
to
do
and-
and
I
prefer
to
to
stop
you're
still
welcome,
at
least
as
as
contributors
to
our
project
and
and
there
will
be
other
coaching,
but
google
summer
of
code
is
an
important,
an
important
thing.
C
D
E
All
right
I'll
cover
this
one,
so
this
jenkins
is
incredibly
powerful
and
there's
a
lot
of
really
cool
things
you
can
do
for
it,
but
one
of
the
struggles
that
we've
had
is
making
sure
that
all
these
really
interesting
things
are
documented.
So
this
this
project
works
on
kind
of,
creating
that
central
documentation
resource
for
being
able
to
access
the
jenkins
rest
endpoints.
E
So
this
is
kind
of
modeled
after
what
we
do
right
now
on
the
website,
if
you
ever
go
to
jenkins
io
and
look
at
the
pipeline
steps
that
are
available
on
that
page,
and
we
will
be
talking
about
that
in
a
later
later,
a
project
idea.
You
can
see
that
all
the
things
are
displayed
there,
so
we
this
project
is
kind
of
doing
the
same
for
our
different
rest.
Endpoints.
E
Also,
if
you
install
jenkins,
there's
actually
a
link-
and
you
can
see
what
rest
points
are
available
within
your
specific
instance
of
jenkins.
But
the
problem
is
it's
a
lot
of
text,
so
we
need
to
also
be
able
to
display
that
using
standards.
So
that's
swagger
or
open
api
three,
and
so
the
this
project
is
being
able
to
come
up
like
with
that
being
able
to
do
that
automatic
generation
expose
what's
available
and
then
potentially,
maybe
even
make
that
available
within
jenkins
itself.
E
D
Okay,
so
back
to
me,
this
project
jenkins
file
runner
action
for
github
actions.
It's
it's
not
entirely
new,
because,
like
previously,
we
have
had
a
poc
project
that
that's
a
similar
name
from
three
years
ago,
and
the
goal
of
this
project
is
to
use
new
tool
called
jenkinsvale
runner
to
implement
a
new,
complete
feature
versions
of
what
we
have
had
before,
which
is
for
you
on
github.
D
So
you
can
see
poc,
link
below
the
skills
to
study
or
improve.
Are
java
jenkins
file,
runner
docker,
get
auctions,
configuration
and
points
to
note,
so
it
has
been
done
before
so
I,
it
won't
be
like
a
start
from
scratch,
project
which
is
like
a
starting
point
and
then
to
wireless
strength
of
the
incubating
project,
check
this
out
runner.
So
more.
It's
fine!
E
Right
back
again
so
similar
I
was
talking
earlier,
we
do.
If
you
go
to
the
jenkins
I
o
site,
you
can
actually
see
this
really
amazing
list
of
all
the
different
steps
that
are
available
through
pipeline.
However,
some
of
those
steps
are
a
little
bit
confusing
to
read,
because
the
way
that
we
generate
this
is
we
basically
have
like
a
headlight
or
like
a
a
jenkins
list.
E
Plugin
manager-
and
it
just
is
using
exactly
what's
coming
from
the
source
code
itself,
but
sometimes
that's
not
exactly
the
best
to
be
able
to
read
like
for
a
human.
So
what
this
is
supposed
to
do
is
you're
supposed
to
go
and
kind
of
do
the
research
to
figure
out,
maybe
how
we
want
to
display
this
information
on
the
page
rather
than
just
kind
of
barfing
some
things
up
and
then
have
a
chance
to
improve
the
layout.
So
there
is
some
like
writing
that
will
be
available
here.
E
It's
not
100
code,
but
there
is
some
thinking
about
how
things
should
look
on
like
to
be
able
to
help
with
documentation
and
also
kind
of
maybe
potentially
even
making
those
changes
to
code
themselves.
So
this
is
working
with
the
tool
that
we
already
have
in
place
and
making
some
improvements
to
that.
So
it's
kind
of
beginner
and
beginner
type
project.
B
And
the
plug-in
installation
manager
tool
improvements,
project
idea
is
taking
a
projectile,
a
project
that
was
actually
a
google
summer
of
code
2019
project,
and
that
is
widely
used
now
throughout
jenkins
to
manage
plugins
configuration
as
code.
So
I
specify
precise
versions
of
plugins
I
want
and
the
plug-in
installation
manager
tool
goes
and
retrieves
them
for
me
brings
them
down
and
installs
them.
B
This
project
idea
is
that
we
encourage
you,
as
you're,
considering
proposing
a
pro
a
plan
for
this
project,
idea
that
you
look
at
the
open
issues
review,
which
things
could
use
improvement
where
the
places
where
users
have
had
difficulties,
what
has
caused
them
struggles
or
challenges,
review
the
existing
documentation,
looking
for
things
that
are
commonly
done,
review,
chat
sessions
or
reddit
sessions
or
community.jenkins.org.
Looking
for
common
questions,
so
that
you
can
then
use
that
to
shape
your
project
plan
with
your
selection
of
improvements
and
your
implementation
plan
for
those
improvements.
B
Oh,
oh,
yes,
that's
right!
Sorry,
I
should
keep.
I
can
also
no,
no
thanks,
john
mark.
Thank
you
for
the
reminder.
Yes,
so
so
in
the
jenkins
ecosystem,
we
have
jenkins
core
and
jenkins
core
provides
a
a
platform
on
which
one
or
many
plugins
are
installed.
Those
plugins
provide
the
key
capabilities,
and
that
means
over
the
course
of
the
15
years
that
jenkins
has
been
under
development.
There
have
been
many
plug-ins
developed.
There
are
over
1800
available
plugins
from
open
the
open
source
community
right
now,
and
the
number
of
plug-ins
continues
to
grow.
B
However,
for
maintainers
and
for
users
they
aren't
always
sure
about
the
condition
of
a
particular
plug-in.
Is
it
well
maintained?
Is
it
actively
maintained
how
many
people
are
using
it?
What's
their
success
or
failure
rate
using
it?
Those
kinds
of
questions
and
this
project
idea
suggests
that
we
would
like
to
have
a
google
summer
of
code
contributor
join
us
in
helping
to
create
a
plug-in
health
scoring
system,
so
that
maintainers
can
see
which
things
are
important
for
them
to
be
doing.
In
order
to
show
that
their
plugin
is
well
maintained.
B
It
also
will
help
users
as
they
say,
which
plugins
are
better
maintained
and
which
may
not
be
as
well
maintained,
so
they
can
bias
their
choices
towards
plugins
that
are
well
maintained
and
will
give
them
a
good
experience.
Now.
This
is
a
multi-component
project
and
there
are
phases
in
this
project
where
we
we
know,
we've
got
to
collect
the
data
with
1800
plugins,
there's
a
lot
of
data
to
collect.
We
need
to
aggregate
the
data
and
combine
it
in
useful
ways
that
will
require
some
data
storage.
Some
consideration
of
how
do
we
store
the
data?
B
Then
we
need
to
present
it
and
we
have
at
least
two
different
audiences
that
need
to
see
the
presentation,
the
maintainers
who
have
one
set
of
needs
and
the
users
who
may
have
quite
a
different
set
of
needs,
so
collection,
aggregation,
presentation
and
data
delivery.
All
part
of
this
project
idea,
john
mark,
was
there
something
before
we
go
on
to
that
one
john
mark
was
there
something
else
you
wanted
to
highlight
on
plug-in
health
scoring
no.
C
Besides
that,
this
is
a
project
that
I'm
very
fond
of,
so
I've
been
dreaming
of
that
for
for
some
time
it's
it's
not
a
one-man
story
or
one.
Ladies
story:
there
are
sub
components
in
that,
and,
and
so
the
the
you
don't
need
to
to
tackle
the
whole
there's
several
stories
in
there
there's
in
in
the
description
you
can
have
a
few
hints.
This
is
just
a
summary
for
for
it,
so
the
prototyping
just
this
is
why
we
highlighted
these
components.
C
Components
are
typically
one
thing
where,
where
people
can
work
quite
separately,
so
love
to
see
that?
Oh,
that's,
that's
my
turn
too
so.
Well.
This
is
another
project
that
comes
from
my
my
previous
years
as
jenkins,
admin
or
or
working
with
that.
So
jenkins
configurations
code
is
a
very
neat
feature
that
allows
to
configure
jenkins
based
on
a
yaml
description,
and
so
this
is
also
the
preferred
way
when
you
want
to
work
the
github's
way
to
configure
jenkins,
we
don't
like
mouses
and
the
end
of
the
joke.
C
C
C
There
are
different
ways
to
implement
it,
so
it's
currently
under
discussion.
So
it's
it's
living
mainly
in
my
brain.
I
see
how
it
like
to
to
see
it
working
many
things
happening
in
my
brain
honestly,
but
I
I
see
how
I'd
like
it,
but
it's
not
defined
yet
so
I
there's
different
ways.
So
if
somebody
chooses
that
that
project
there
would
be
an
an
important
functional
description,
part
and
say
how
could
this
work?
What
would
be
the?
How
would
the
user
or
or
an
admin
use
the
tool?
C
So
there
there's
an
interesting
creativity,
part
in
implementing
that
it
should
be
usable
in
the
pipeline
or
within
the
user
interface.
So
it's
it's
a
it's
an
interesting
project.
Now
I'm
selling
it
again,
but
I
could
have
used
such
a
tool
in
my
my
previous
live
and
on
my
current
jenkins
environment.
B
Be
surprised
if
multiple
project
ideas
wouldn't
be
much
bigger
than
the
time
would
allow
in
the
three
months
that
we
have
for
google
summer
of
code,
but
I
I
think
it
would
be
a
valid
proposal
to
say.
Yes,
I
think
this
idea-
and
this
idea
in
combination
might
be
a
better
story
for
some
reason
so,
but
but
it
would
still
be
the
candidates
single
proposal.
Their
proposal
is
here's.
B
C
Know
the
english
word
for
that,
but
another
way
to
to
answer
the
question.
I
hope
we
answered
the
question
in
some
way
correctly.
So
please,
let
us
know
if
this
was
not
correctly
answered.
The
other
question
and
there
were
several
replies
to
it-
was:
can
experienced
professionals
also
participate
to
gsoc?
C
B
Now
and
I
think,
there's
something
interesting
hiding
in
chris's
answer
chris,
I
believe
you
were
actually
a
google
summer
of
code
participant
twice
right,
so
you
were,
you
were
in
the
second
time
still
considered
new
enough
to
open
source
to
qualify,
so
new
to
open
source
sounds
seems
like
it's
relatively
flexible
right
you.
You
really
worked
on
two
different
years
on
google
summer
of
code
as
a
student.
D
B
C
B
So
there
was,
there
was
one
more
john
mark
and
it
was
the
number
of
hours.
Well,
the
the
question
was
yeah
experienced
professional
contribute
if
they
don't
have
30
to
40
hours
a
week
to
give
to
the
project
which
people
who
are
in
a
full-time
job
typically
do
not,
and
I
think
the
the
question
was,
can
how
many
hours
is
expected
of
someone
who's
selected
to
participate
in
google
summer
of
code
and
in
in
the
earlier
sessions
in
2020,
2019,
etc.
B
They
expected
30
to
40
hours
a
week,
but
my
understanding
was
with
covet
19
in
2021
and
now
in
2022
they've
cut
that
number
in
half
so
that
so
that,
if
you're
disrupted.
For
this
reason
or
that
reason
you
can
still
be
successful
in
google
summer
of
code,
if
you
can,
on
general,
commit
15
to
20
hours
a
week
to
the
project
over
the
course
of
this.
The
three
months.
D
E
Of
also
want
to
throw
out
like
the
idea,
but
if
you
have
your
own
idea,
that
is
amazing,
and
we
really
like
these
are
just
ideas
that
we
have
for
you.
If
you
have
your
own
idea,
that's
wonderful.
One
thing
I
do
suggest
is
trying
to
get
that
proposal
written
as
quickly
like
as
soon
as
possible
to
be
able
to
get
it
out.
E
So
we
can
try
to
help
you
find
mentors
on
that,
maybe
be
even
beyond
the
people
on
this
call
like
at
the
outside
to
be
kind
of
able
to
help
guide
you
through.
But
if
you
have
your
ideas,
no
problem
submitting
them
just
kind
of
do
it
early
and
we'll
try
to
be
able
to
pair
you
up
with
somebody
that
might
know
more
about
the
area
you're
concerned
about,
but
yeah.
I
just
want
to
highlight
that
very
excited.
C
E
C
Yeah
yeah,
but
this
is
this-
is
very,
very
true
and
and
yeah.
I've
forgot
to
to
mention
that
any
idea
is
open
and
this
is
a
principle
of
open
source.
Whoever
comes
with
an
idea,
just
put
it
on
the
table
and
we're
going
to
see
if
we
can
build
something
around
or
get
people
get
traction
and
get
people
on
it.
So
a
very
good
day
to
emphasize
that.
C
C
B
B
So
does
that
give
you
an
indication
of
the
competitiveness
at
some
level?
Yes,
each
year
will
be
different.
The
previous
year,
I
think
I
reviewed
actually
far
fewer
applications
for
the
the
topic.
I
was
mentoring,
so
it
depends
on
the
number
of
people
applying
is
to
decide
how
competitive
or
non-competitive
it
is.
D
E
B
B
C
Good
there
was
a
question
asked
and
chris
answered
to
it,
but
for
the
re,
the
people
watching
the
recording,
I
would
like
just
to
repeat
it.
So
there
was
a
question
about
how
is
time
devoted
quantified,
as
in
somebody
may
require
some
time
to
do
research
so
would
that
be
accounted
chris?
Do
you
want
to
either
repeat
your
answer
or
add
more
color
to
it
for
the
audience.
C
D
D
B
C
And
the
other
advice
I
I'd
give
is
is
take
particular
care
in
preparing
a
good
proposal
and
think
of
the
people
that
are
going
to
read
it.
So
by
writing
your
proposal,
you're
talking
to
people
that
you're
trying
to
convince
and
try
to
make
to
be,
as
as
precise,
correct,
creative
convincing
in
what
you
do.
D
C
Then
there
is
another
question
here:
oh
is
how
competitive
is
jenkins
g-stock
according
to
previous
year's
application,
I
think
we
answered
that
one
did
I
miss
that?
No,
I
think
we
no!
No.
We
addressed
that
one.
We
addressed
that
one
right.
Okay,
so
I
clicked
on
done
other
questions
or
doubts
that
we
can
clarify.
C
Don't
forget
if
you
have
other
questions
while
you
sleep
on
it
and
rehash
what
has
been
said
here,
we
have
the
various
asynchronous
communication
channels,
the
getter
channel
discourse,
so
community
jenkins,
dot,
io
and
the
office
hour
sessions
that
we
that
we
organize,
where
you
can
come
back
to
your
to
your
questions.
So.