►
From YouTube: Newcomer Track Adopt a Plugin
Description
Jenkins Contributor Summit June 25, 2021 Newcomer track - Adopt a plugin
slides https://docs.google.com/presentation/d/1eU0KabpBtGd0BCebuhWyvBgBunBaZvM3hIfcpdy_-OE/edit?usp=sharing
A
A
So
what
what
we've
got
here
is
individual
maintainers,
one
or
two
or
sometimes
three
are
the
ones
who
care
for
an
individual
plug-in
and
those
maintainers
release
the
plug-in
they
update
it,
to
use
new
versions
etc.
Well,
one
of
the
things
we
need
is
more
maintainers,
because
we've
got
over
a
hundred
that
are
ready
to
be
adopted.
A
Now,
first
challenge
is
we
need
to
overcome
your
sense
of
imposter
syndrome?
Oh,
I
can't
do
that.
Then
we're
going
to
talk
about
how
you
can
find
which
plug-ins
you
could
adopt.
Then
you
send
the
request
to
adopt
the
plugin
and
you
start
improving
it.
It's
actually
a
relatively
lightweight
process
to
do
this,
and
some
of
these
plugins
are
so
lightweight
that
you
could.
You
could
adopt
them
and
only
spend
on
the
order
of
minutes
or
maybe
an
hour
a
week
and
still
be
a
very
successful
plug-in
maintainer.
C
B
So
there
you
mention
that
improve
the
plug-in
and
release
the
improvements.
Can
you
can
you
give
me
more
examples
on
how
we
can
improve
a
plug-in.
A
Absolutely
yes!
So
so,
for
instance,
one
of
the
things
that
that
I
think
it
was
actually
jonathan
mentioned
is
he's
been
maintaining
a
plug-in
just
keeping
it
up
to
date
and
one
way
to
improve
the
plug-in
is
to
update
it,
so
that
you're
sure
it
runs
with
and
depends
on
a
modern
jenkins
version.
So
you
might
update
the
pom
file
to
use
the
most
recent
pom.
You
might
update
its
dependencies
to
depend
on
more
recent,
more
modern
libraries.
A
A
A
There
are
plugins
that
you
could
adopt
if
you're
willing
to
do
basic,
fundamental
things
like
this.
Now,
if
you
say
oh,
I
can't
do
those
things
all
right,
then,
maybe
you
shouldn't
adopt
a
plug-in,
but
most
people
with
technology
experience
could
benefit
themselves
and
others
by
adopting
a
plug-in
and
and
caring
for
it.
Spending
10
minutes,
15
minutes,
30
minutes,
exploring
it
to
understand
how
it
might
be
improved
just
a
little
bit.
A
So
let's
talk
first
about
some
of
the
plugins
that
are
available
for
adoption.
So
there
are
api
plugins.
Now
what
an
api
plugin
is
in
the
adoption
list
is
it's
a
plugin
that
is
a
jenkins
representation
of
an
existing
api
component,
for
example,
the
apache
http
client
is
an
a
released
library,
that's
shipped
by
others,
but
in
order
to
make
it
convenient
to
use
for
a
jenkins
developer,
we
have
a
jenkins
plug-in
whose
whole
job
is
to
bundle
that
library.
A
A
A
I
maintain
the
git
plugin
and
the
way
I
got
there
was.
I
started
by
writing
tests
for
the
git
plugin
trying
to
avoid
regressions
and,
after
writing,
tests
for
a
while
people
said
hey.
Should
we
just
give
this
guy
commit
permission
because
he
keeps
submitting
all
these
tests?
You
could
do
that
now.
There
are
more
things
more
plugins
that
could
be
adopted
like
on
windows,
specifier
windows,
user.
There
are
windows,
specific
things
that
could
help
others
and
may
help
you
as
well.
A
A
Likewise,
there
are
test
tools
that
need
to
be
put
up,
for
that
are
that
have
been
put
up
for
adoption
and
are
ready,
so
all
of
them
give
us
a
hint
that
there's
lots
that
you
could
do
if
you
were
willing
to
adopt
a
plug-in
and
help
us.
So
now,
let's
take
a
minute
here
and
look
at
the
at
the
process
and
I've
got
a
whoops.
I
need
to
go
back
one.
A
So
this
is
what
we
do.
We
follow
this
this
page.
That
gives
us
instructions
on
how
to
identify
a
plug-in,
that's
up
for
adoption
and
then
adopted,
and
it
talks
about
hey.
You
send
an
email
to
the
jenkins
developer
mailing
list
with
a
link
to
the
plugin.
You
want
to
adopt
a
link
to
the
pull
request
that
you'd
like
to
deliver,
if
any
your
github
username
and
your
jenkins
account
so
now,
how
do
we
find
plugins
that
need
adoption?
A
A
A
D
A
Oh,
that
that
is
marcel.
That
is
a
brilliant
way
to
find
it.
Thank
you
for
highlighting
that
that
is
absolutely
so.
Did
you
did
you
catch
what
marcel
said?
He
noted
your
jenkins
installation
will
hint
to
you
the
things
you
might
consider
adopting.
So
what
I
did
was.
I
went
to
the
jenkins
dashboard
to
manage
jenkins,
manage
plugins
and
under
installed.
A
Now
look
at
these
nice
big
boxes
that
tell
me
oh,
hey
the
apache,
http
components,
client
4.x,
api
plug-in
is
up
for
adoption
there's.
This
is
one
that
I
was
describing
right.
So
you
see
it
here,
and
this
is
a
great
candidate.
Maybe
you
say
I'd
like
to
know
more
about
that
plug-in.
So
you
open
that
link-
and
here
is-
is
all
the
discussion
about
that
plugin.
Oh
I'd
like
to
see
it's
github
repository
there.
It
is
ready
to
go
okay.
A
What
what
kinds
of
changes
have
happened
recently
all
visible
from
here
and
waiting
for
you
to
get
involved
to
adopt
it
excellent
marcel
thanks,
so
much
for
pointing
that
out.
So,
let's,
let's
look
at
mark's
at
my
installation
to
see
just
how
many
of
my
plug
of
the
plugins
that
I
actively
use
are
are
up
for
adoption,
so
I've
got
apache
http,
authorize
the
bitbucket
branch
source,
the
build
timeout
plugin
conditional,
build
step,
config
file
provider,
this
one's
actually
quite
valuable.
To
me,
I
like
that
one
configuration
slicing.
A
Oh,
I
love
this
one
and
I
would
love
to
some
for
somebody
to
adopt
it
because
it
lets
me
with
one
set
of
clicks,
modify
the
configurations
of
many
many
jobs
all
at
once,
and
and
gives
you
a
good
hint
of
the
kinds
of
plugins
that
are
up
for
adoption
marcel
thanks
again
for
pointing
us
that
way.
That's
a
that's
a
great!
Let
me
put
that
in
the
slides
is,
is
look
at
your
own
jenkins
instance.
A
Excellent,
so
the
the
process
that
was
described
there
send
an
email
to
the
jenkins
developers.
Mailing
list
is
pretty
simple:
it's
there's
not
a
it's,
not
a
very
high
bar.
You
can
just
ask
hey
I'd
like
to
be
made
a
maintainer
now
with
some
of
the
plugins.
They
may
ask
that
you
first
submit
pull
requests
to
show
that
you've
you're
interested
they
that's
a
fair
thing
and
okay,
it's
a
great
way
to
get
involved
any
any
other
questions.
So
far.
E
Oh
hello,
mark
hello.
This
is
over
here
in
context
to
the
skill
sets
that
is
required
actually
to
develop
a
plugin.
Can
you
please
help
me
know
what
specific
java
skills
do
we
need.
A
Good
question,
so
what
specific
java
skills
are
needed
to
maintain
a
plug-in?
So
so,
if
it's
okay,
I'm
going
to
tell
my
story
as
a
way
to
answer
your
question,
so
I
was
a
manager
warning
warning
manager.
I
said
manager.
I
was
a
manager
of
a
team
of
software
developers.
I
had
been
managing
for
many
years
and
therefore
did
not
write
code.
Day-To-Day
right.
I
did
not,
but
I
was
interested
because
I
wanted
to
be
sure
that
the
particular
plugin
that
caught
my
interest
was
had
more
tests.
A
So
I
started
personally
writing
tests,
but
I
had
not
done
active
java
development.
I
had
little
or
no
experience
in
java
ides
and
I
used
my
my
beginnings
of
adopting
the
plug-in
to
learn
those
things.
So,
if
you're
willing
to
learn
about
java,
if
you're
willing
to
learn
about
how
to
use
maven,
I
had
never
used
maven
before
starting
work
on
the
jenkins
get
plug-in.
A
A
E
Thanks
mark
thanks
for
the
answer,
I'm
satisfied,
however,
successful
to
this
question,
and
I
also
have
another
question:
like
you
know,
jenkins
extensions
are
sometimes
built
using
bully
as
well.
So
is
knowledge
of
boogie
also
sufficient
or
be
or
is
it?
Is
it
only
pure
java
that
you
need.
A
So
I'd
we
generally
a
jenkins
plug-in,
will
not
be
built
with
groovy
many
people
use
groovy
to
create
pipelines.
They
use
use
groovy
in
very
interesting
ways,
but
a
plug-in
will
generally
be
a
java
component
rather
than
a
groovy
component,
given
that
groovy
and
java
syntax
are
quite
similar,
I
didn't
find
it
difficult
to
learn
groovy
when
I
needed
it,
but
in
my
case
I
had
been
a
maintainer
of
a
plug-in
for
many
many
years
before.
I
even
did
anything
with
groovy.
E
E
Sorry,
sorry,
sorry
guys
just
a
very
novice
question,
basically
because
I'm
very
very
new
to
this
particular
topic,
but
I'm
very
much
interested
in
getting
along,
because
I
have
been
using
a
lot
of
plugins
there.
E
Been
a
kind
of
you
know,
enthusiasm
as
to
how
the
plugins
are
getting
developed,
and
I
think
this
is
the
best
platform
that
I
can
get
most
of
the
knowledge.
The
question
that
I
had
actually
mark
is
initially
obviously,
like
you
showed
the
materials
as
to
how
to
get
and
adopt
a
plugin.
Basically,
but
there
might
be
instances
where
you
know
initially,
specifically
myself.
I
might
need
some
kind
of
a
hand
holding
so
is
it
possible
that
I
can
reach
to
you
or
someone
else
to
you
know,
understand
and
understand
the
process?
A
A
Let's
see
where
would
I
best
put
that
let's
find
how
about
how
about
we'll
just
put
it
right
here?
So
so
one
is
the
developer's
mailing
list
or
chat
on
newcomer
contributors,
getter
channel
so,
and
that
is
at
this
location.
So
I'm
going
to
go
ahead
and
open
it
up,
and
it's
jenkins
getter
here
and
here
is
the
newcomer
contributors
channel
and
what
that
is.
A
Is
it's
specifically
dedicated
to
helping
people
who
are
brand
new
contributors,
and
so
there
you'll
find
folks
now
if
you've
got
a
very
specific
development
question,
the
jenkins
developer
list
is
a
great
place
to
to
ask
your
question.
If
you're
feeling
like
I
did
initially,
if
you're,
if
you're
letting
your
imposter
syndrome
kick
in,
and
you
say
I'm
not
sure.
I
want
to
ask
a
question
in
that
big
of
a
group.
The
newcomer
contributors
group
is
quite
small
and
very
comfortable.
E
A
F
Yes,
I
had
a
question
I
have.
I
have
noticed
that
some
plugins
have
forks
on
github.
I
I
explain
it,
and
this
does
confuse
me.
For
example,
I
saw
as
an
example,
I
will
name
a
sonar
cube
plugin
sonar
cube
plugin
at
jenkins.
It's
a
fork
of
sauna
scanner
jenkins.
A
Very
good
question:
okay
and,
and
I'm
showing
I'm
showing
on
my
screen
an
example.
That's
not
the
sonar
cube
example.
You
did
but
an
example
that
I
deal
with.
So
I
I
think
what
you're
highlighting
is
this
text
right
here?
Yes,
yes,
right,
it
says:
hey
wait!
A
second!
This
thing
is
forked
from
some
some
and
and
and
that,
while
that
message
is
accurate,
if
we
we
can
open
this
up
and
we'll
see
just
what
that
means.
So,
yes,
the
jenkins
ci,
get
plug-in
repository
accurately
was
forked
from
nigel
magnanese,
a
hudson
git
plug-in.
A
So
so
the
the
simple
answer
is:
you
can
ignore
the
forked,
from
and
and
in
99.99
of
the
cases.
That
is
the
exact
right,
safe
thing
to
do
so,
ignore
the
fork
from
and
follow
the
contributing
directions
that
you'll
find
for
most
plug-ins
in
their
contributing
file
like
this
one
where
it
says
this
is
where
you
should
contribute,
and
this
is
how
you
should
do
it.
Those
kind
of
things.
C
A
All
right
so
so
back
to
our
the
idea
that
we
want
to
want
to
encourage
adoption
of
plugins,
so
you
find
the
plug-in
you
want
to
adopt
and
and
remember.
This
is
the
part
where
you
have
to
overcome
the
the
imposter
syndrome
thing,
oh,
but
I
can't
adopt
a
plug-in
that's
much
too
popular,
much
too
big
or
or
much
too
narrow.
You
don't
stop
making
excuses
and
just
acknowledge
that
it's
a
good
thing
to
yeah.
Okay,
maybe
I'll,
give
a
little
bit
of
time
and
see
how
it
goes.
A
So
when
you
adopt
the
plug-in
you
might
ask,
and
and
this
was
something
that
that
dhiraj
asked-
what
are
some
things
that
you
might
do
initially
to
a
plug-in
and
so
jonathan
I'm
going
to
sort
of
target
your
plug-in
as
one
example
of
this
kind
of
thing,
because
it's
a
valid
question:
hey
I've
got
this
plug-in
that
I
use.
A
A
I
love
this
thing
because
what
it
does
is
it
tells
me
when
the
plug-in
I
maintain,
has
a
new
update.
So
as
an
example,
let's
look
at
one
of
the
the
plug-ins
I
maintain
is
called
the
platform
labeler
and
I
love
what
this
thing
tells
me
in
terms
of
pull
requests,
because
I
will
get
a
pull
request.
That
says,
let's
look
at
closed
pull
requests.
A
Oh
one
of
some
of
my
tests
depend
on
a
docker
image
and
this
bump
the
amazon
limits
linux,
docker
image
was
offered
to
me
by
dependipot.
Without
me
doing
anything
I
did
absolutely
nothing
other
than
configure
depend
about,
and
it
has
suggested:
hey
amazon
upgraded
their
docker
image.
Oh
ubuntu
upgraded
their
docker
image;
oh
alpine,
upgraded
their
docker
image,
each
of
them
with
no
effort
on
my
part,
dependable
just
helps
so
so
this
is
a
great
one
depend
about.
A
A
A
Okay,
next
thing
that
you
can
do
to
simplify
your
life
as
a
developer
is
simplify
the
change
log
maintenance
with
a
release.
Drafter,
okay
release.
Drafter
is
again
a
little
piece
of
automation
that
watches
the
pull
request
that
you
merge
and
proposes
changes
to
the
change
log
so
that
other
people
can
see
it
and
automatically
publish
it
so
that
you
can
automatically
publish
it
when
you're
ready
to
release.
A
A
Was
all
created
for
me
automatically
from
the
pull
requests
that
I
merged
to
the
plugin?
I
didn't
do
anything
to
create
this.
What
to
me
is
a
very
attractive
page.
It
assign
things
to
features
and
improvements
to
dependency
updates
to
documentation,
updates
all
through
the
magic
of
release
drafter.
So
it's
a
great
thing
to
do
as
a
proposed
change
for
a
plug-in
you're
adopting.
A
Likewise,
this
one
use
the
jenkins
plug-in
bill
of
materials
is
a
great
way
to
simplify
the
maintenance
of
a
plug-in
and
and
simplifying
is
really
a
good
thing.
So
this
page
talks
about
how
you
use
this,
how
you
add
this
little
snippet
right
here
and
then
you
start
taking
away
specific
version
numbers
listed
in
your
plugin
and
it's
much
much
better
to
maintain
so
jenkins
bill
of
materials
track
dependencies
with
the
pentabot
and
simplify
your
change.
Log
management
with
release
drafter
all
good
things
to
do
to
contribute
to
a
plug-in.