►
From YouTube: Hacksgiving: Intro to the Jenkins Project
Description
This session introduces some of the resources available to Jenkins contributors of all backgrounds.
See also:
https://wiki.jenkins-ci.org/display/JENKINS/Beginners+Guide+to+Contributing
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
A
So
the
stuff
that
I
wanted
to
go
through
first,
you
know
this
is
mostly
for,
for
my
own
benefit
or
four
for
the
the
YouTube
stream.
I
just
wanted
to
sort
of
start
out
walking
through
the
beginners
guide
and
most
people
I
would
imagine
that
I
found
hacks
giving
have
found
that
either
through
this
wiki
page
or
through
the
meetup
page.
A
Both
pages
links
to
this
page,
that's
called
the
beginner's
guide
to
contributing
to
Jenkins
click
on
links,
and
it's
just
the
beginner's
guide
to
contributing
and
I'll
include
this
in
some
some
notes
for
for
after
this
session,
I
wouldn't
say
that
this
page
is
perfectly
up
to
date.
I've
gone
through
and
I've
made
some
minor
edits
here
and
there,
but
what
this
page
goes
through.
A
Just
some
of
the
basic
resources
I'm
going
to
begin
this
text
a
little
bit
so
most
people
I,
would
hope,
know
how
to
find
IRC.
But
if
you
cannot
find
it,
if
you
just
search
for
the
IRC
channel
page
on
the
wiki,
that
is
how
you
find
a
couple
of
our
Jenkins
IRC
channels.
All
of
our
IRC
channels
are
on
freenode,
which,
if
you
go
to
free
node
net,
will
open
up
a
web
chat
for
you,
which
is
pretty
good.
A
Most
everything
that
happens
with
the
project
is
going
to
fit
into
pretty
much
one
of
three
different
web
applications.
One
is
the
bug
tracker,
which
is
just
issues
Jenkins,
CI
org,
which
is
a
standard
sort
of
JIRA
installation,
and
there
you'll
see
we've
got
the
the
Jenkins
project.
We've
got
the
infrastructure
project,
defensed
security
and
website.
Most
everything
that
you're
going
to
encounter
if
you're
trying
to
contribute
to
Jenkins
is
going
to
be
under
this
Jenkins
project
and
under
the
Jenkins
project.
A
If
you
go
in
and
you
create
an
issue,
this
is
all
assuming
you've
created
an
account
and
I'll
get
back
to
that.
In
a
second,
be
you
know
filing
bugs
and
the
components
are
almost
always
going
to
be
based
on
you
know
a
jira
or
sorry
at
not
a
jira
they
plug
in.
So
if
I
had
a
problem
with
the
github
plugin
I
just
start
typing
github
and
choose
the
plug-in,
and
this
allows
any
ticket
that
you
file
to
go
to
someone
that
is
responsible
or
assumes
maintainer
ship.
A
If
there
is
a
maintainer
of
that
plugin,
that's
just
a
brief
foray
into
JIRA.
If
we
jump
back
and
the
other
place
where
there's
a
lot
of
content
is
in
the
wiki,
which
is
just
wiki'd
Inc
in
CI
dot
org-
and
this
is
where
you
would
find-
let's
use
github
again,
you
know
the
github
plugin
documentation
page
have
to
forgive
the
dogs
barking
in
the
background.
A
A
The
Jenkins
organization
is
just
under
github.com
/,
Jenkins
CI,
and
this
has
most
of
the
documentation
for
the
new
website
that
I'm
working
on
all
the
plot
for
the
majority
of
plugins,
the
plug-in
source
code
and
then
Jenkins
core
source
code
as
well.
So
if
you
just
go
to
Gingka,
see
I
/
Jenkins,
if
I
could
spell
it
quickly
and,
for
example,
this
is
where
the
Jenkins
server
itself
has
hosted.
A
But
most
everything
that
you
need
to
find
is
going
to
be
under
issues
that
jig
at
CI,
the
wiki
or
on
github,
and
if
we
keep
going
through
this
beginner's
guide
to
contributing
there's
a
lot
of
different
ways
that
you
can
contribute
to
the
project
now.
I,
for
example,
don't
really
enjoy
writing
Java
code,
so
most
of
the
contribution
that
I
make
is
in
the
way
of
documentation
or
infrastructure.
A
But
if
you
do
work
on
Java
code
or
you
enjoy
writing
Java
code,
there's
a
whole
lot
of
resources
that
can
get
you
started
on
on
writing.
Plugins
and
probably
one
of
the
best
places
to
start
is
the
plug-in
tutorial
and
now,
in
three
hours
from
now,
Steven
Cristo
is
going
to
give
a
plug
in
development
workshop.
A
Now,
if
you
just
go
to
etherpad
osu
OSL
org,
slash
jenkins,
dash
hacks
giving-
and
this
is
a
public
etherpad
and
I've
I'll-
start
to
collect
links
in
here
and
encourage
other
people
to
do
the
same
as
as
the
day
progresses
and
as
tomorrow
starts
and
then
after
that
afterwards,
we
can
use
some
of
this.
Some
of
these
notes
to
to
help
improve
some
of
the
Jenkins
documentation.