►
From YouTube: Jenkins 2022 and Beyond? - Oleg Nenashev, Dynatrace
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
Jenkins 2022 and Beyond? - Oleg Nenashev, Dynatrace
Virtual Track
Speakers: Oleg Nenashev
Is the Butler Still Young? Maybe not but it is still one of the most popular automation tools. Jenkins in 2022 is not Jenkins in 2012. It keeps evolving to address demands from its users and contributors: pipeline as code, configuration as code, better support for cloud environments, UX, etc. We are looking forward to the next major iteration in Jenkins evolution. So what’s next for it? I will focus on the current challenges for Jenkins. What does need to change in the project and the community to keep it relevant? We will talk about revitalizing the community and attracting new company contributors, consolidating user experiences, and reusing experiences of BlueOcean and Jenkins X? We will also talk about interoperability with other projects, making Tekton a first class citizen Pipeline engine, and making Jenkins available everywhere regardless of CI/CD system you actually use.
A
Well,
thanks
for
having
me
at
the
cd
con,
I'm
happy
to
participate
virtually
this
year
as
I
have
no
passport.
So
I
cannot
join
you
in
austin,
but
I
hope
you
have
a
great
conference
and
a
great
contributor
summits
after
that
my
name
is
alex
nash.
If
I
work
for
donald
trees
and
I'm
one
of
contributors
in
the
jenkins
project,
I'm
also
a
tc
member
in
the
genius
delivery
foundation
and
in
november
I
joined
dynatrace
to
help
with
open
source
projects,
including
captain
open
feature
and
other
open
source
initiatives.
A
Today,
my
presentation
will
be
about
jenkins
and
its
future,
mostly
focus
junkies
users
and
contributors.
It
will
be
quite
high
level
talk.
I
don't
have
much
time
to
do
deep
dive,
but
I'm
happy
to
do
it
in
community
lately,
if
you're
interested
so
slides
are
already
available
and,
as
always
disclaimer.
I
just
talked
about
my
own
opinion,
not
very
aligned
with
the
jenkins
community
at
the
moment,
because
actually
I'm
taking
a
sabbatical
at
the
moment
because
of
my
personal
reasons
because
of
the
ongoing
war.
A
You
know
the
jenkins
and
the
easterly
foundation
made
official
statements,
but
I
still
participate
in
enjoying
his
governance.
Do
mentorship
and
google
summer,
of
course,
will
help
kriston
and
abu
dhabi
to
help
a
student
working
on
joining
runner
and
github
action
and
be
sure
I
will
be
back
in
the
community
soon.
A
Okay,
so
if
you
have
ever
used
changes,
probably
you've
seen
my
name
there
a
few
times
so
yeah
a
moment.
You
know
I
can.
As
far
as
events
and
meetups,
I
was
jenkins
evans
officer
for
something
like
one
year.
I've
been
organizing
google
summer,
of
course,
since
2016,
and
until
this
year
I'm
also
commenting
at
in
the
junkies
configurations,
code
plugin
and
I'm
a
big
fan
of
configurations,
code
and
infrastructure,
scottish
system
and
jenkins,
and
I'm
a
maintainer
of
jenkinsville
runner.
A
It's
a
new
engine
for
serverless
execution
of
jenkins
pipelines,
I'll
recover
it
later.
So
before
we
go
to
the
future
of
jenkins.
Let's
go
to
the
past
and
yeah,
you
know
jack
started
more
than
15
years
ago
to
automate
various
use
cases,
including
building
testing
software.
It
was
long
ago
and
drinks
became
an
industry
standard,
so
all
of
us
know
about
it
and
there
is
no
point
to
spend
time
on
15
years
of
history.
A
So
let's
skip
them
a
bit
and
actually
what
is
jenkins
now
so,
first
of
all,
it's
automation,
server
and
framework.
It's
not
the
ci
cd
to
as
many
thing
it's
fully
open
source.
It
has
open
community
and
there
are
more
than
eighteen
hundred
plugins
in
this
eca
system
and
thanks
to
this
community,
you
get
a
lot
of
support.
You
get
a
lot
of
assistance
and
the
ecosystem
keeps
evolving
in
many
directions,
from
front-end
to
extra
integrations
and
kubernetes
support,
and
for
many
people,
one
of
important
items
that
commercial
support
is
available.
A
So
if
you
need
it,
you
can
get
one.
So
how
jenkins
succeed
again,
I
will
avoid
kosoki
on
this
side.
So
actually
he
pointed
out
three
main
reasons
for
drinking
success.
So,
first
of
all,
it's
extensible,
so
you
can
adapt
it
for
any
needs.
It's
general
purpose,
so
you
don't
have
to
be
a
software
engineer
or
engineer
at
all.
So,
for
example,
I
started
using
jenkins
for
testing
hardware
projects
when
it
was
still
hudson,
but
many
use
it
for
various
kinds,
including
accounting,
automation
and
just
works.
A
And
last
but
not
least,
one
of
the
factors
was
a
captain
community.
Sorry
jenkins,
community.
This
is
a
great
community
and
it
pushed
the
project
forward
since
its
very
beginning
and
now
more
than
15
years
later,
it
still
evolves
thanks
to
its
community.
So
for
me
the
key
reasons
for
success
are
just
open
governance.
Always
decisions
are
taken
publicly
and
this
can
be
discussed
publicly.
A
The
evolution
is
defined
by
contributors.
So
basically
the
project
officially
declares
marital
crises
of
decision
making.
If
you
contribute,
you
have
a
seat
at
the
table
and
if
you
want
to
participate
just
start
contributing
and
if
your
company,
if
individual
contributors,
the
project,
is
open
for
you,
you
can
just
join
and
start
working
on
your
interest
and
we
do
not
set
up
many
requirements
for
the
pluginikai
system,
so
maintainers
basically
have
full
powers
in
their
plugins.
It
leads
to
many
disadvantages.
A
Well,
many
of
us
talk
about
plug-in
health
dependency
issues,
etc.
At
the
same
time,
it
was
the
way
for
changes
to
achieve
this
ecosystem
and
actually
for
me,
it
works
well.
So
the
project
has
been
evolving
since
the
very
beginning
and
actually
changed
a
lot.
So
maybe
you
remember
hudson
in
2008
when
it
was
basically
just
working
executing
some
bills.
A
Changes
became
much
more
powerful
in
terms
of
tools
in
terms
of
a
case
system,
and
if
we
talk
about
jenkins
in
2022,
I
would
mention
a
few
items
like
pipeliners
code,
so
defining
all
pipelines
in
acm,
of
course,
configurations
code.
Where
you
define
your
system,
configuration
and
configuration
of
your
entire
system
as
infrastructures
code.
We
have
a
lot
of
new
plugins
and
integrations
for
modern
tools.
A
We
have
modern
packaging,
including
kubernetes,
separator
home,
charts,
docker
images,
and
we
have
distributions
for
public
cloud
available
now
there
is
a
lot
of
work
on
supporting
additional
platforms,
but
the
junkies
is
basically
available
everywhere
and
the
project
keeps
growing.
Unfortunately,
I
haven't
updated
this
screenshot,
but
trust
me.
It
still
keeps
growing
in
terms
of
contributions,
and
there
is
still
a
major
uptick
in
terms
of
automated
contributions
by
boats,
but
we
mostly
care
about
the
contributors
that
participate
as
individuals.
Okay.
A
A
So
now,
open
telemetry
is
probably
a
top
four
project
in
this
ncf
and
it
is
growing
like
hell,
but
ultimately,
jenkins
is
still
one
of
the
second
biggest
project
in
the
foundations,
so
some
obstacles
we
hit
during
the
growth
of
course,
when
having
this
rapid
growth
from
a
few
dozen
contributors
say
in
2010s
to
5
000
contributors
in
recent
years.
Of
course,
we've
got
a
lot
of
visibility
communities.
Sometimes
there
was
lack
of
transparency,
not
intentional
ones,
people
just
we're
just
using
channels
so
that
we're
gonna
defined
well.
A
Sometimes
junkies
can
be
perceived
as
lacking
focus
because
there
are
many
people
pushing
in
different
directions.
Again,
the
changes
happen
only
where
there
are
contributions
and
it
helps
for
many
contributors
to
actually
get
behind
the
initiatives,
because
you
cannot
find
them.
At
the
same
time,
it
is
difficult
to
find
contributors
for
initiatives
too,
so
there
are
many
issues
with
visibility
and
outreach
and
we
started
working
on
community
consolidations.
A
So,
for
example,
10
years
ago
we
introduced
open
governance.
So
when
we
got
renamed
to
jenkins,
they
were
regular
governance
meetings.
Ever
since,
in
2015
we
introduced
the
sub
teams
officers
sub
projects,
then
we
introduced
the
framework
of
jenkins
enhancement
proposals
for
technical
discussions
and
specifications.
A
We
started
at
various
special
interest
groups
so,
for
example,
platform
seek
advocacy
and
outreach
cloud
native,
et
cetera,
et
cetera.
We
also
had
first
have
a
governance
board
elections
in
2019,
yes,
eight
years
later,
but
we
had
them
and
now
this
process
becomes
regular.
Also,
we
became
a
foundation
member
of
the
continuous
delivery
foundation
thanks
to
cdf
for
hosting
this
conference
and
in
2020,
which
graduated
at
the
cdf
as
jenkins,
and
we
also
introduced
public
roadmap
as
a
part
of
this
graduation.
A
All
of
that
was
needed
to
help
the
project
become
more
visible
and
to
help
people
understand
why
we
are
going
so
the
public
roadmap
yeah.
You
made
a
number
of
presentations
on
that
topic.
It's
almost
two
years
old.
By
now.
It
still
addresses
jenkins
users,
contributors,
doctors
and
vendors.
We
keep
this
roadmap
mostly
up
to
date,
and
our
main
focus
is
to
keep
the
roadmap
community
driven.
So
huma
drives
an
initiative.
They
are
welcome
to
put
the
initiative
on
this
roadmap.
All
the
initiatives
are
welcome.
A
Our
dates
jenkins
features
manchester
united,
kicks
his
documentation,
infrastructure,
community
events.
Whatever
all
of
that
can
be
represented
on
the
roadmap,
we
have
an
open
and
transparent
process.
How
we
get
these
items
accepted
based
on
pull
requests.
You
have
open
data,
so
you
can
just
extract
it
in
a
yamaha
format
for
your
own
purposes.
A
At
the
same
time,
we
don't
commit
on
any
dates
and
delivery
at
all,
because
again
we
drink
civils,
where
we
have
contributors.
So
if
you
don't
see
a
particular
item,
evolving
being
start,
let's
say
in
progress
for
something
like
two
or
three
years
or
in
preview.
The
best
thing
you
can
do
is
actually
contribute
to
the
project
and
here
go
the
obstacles
for
the
junkies
community,
because
we
can
speak
about
its
advantages
for
long
time,
but
obviously
not
everything
great
in
the
project.
A
A
This
generation
actually
faced
a
lot
of
issues
since
it
was
founded,
including
introduction
of
continuous
delivery,
develops.
Continuous
deployment
b
tops
configurations
code,
various
quality
assurance
approaches,
like
shift
left
and
the
third
generation
had
to
evolve
a
lot
to
meet
these
demands.
Some
projects
succeeded
like
jenkins,.
A
Also,
of
course,
teamcity,
of
course,
asia
devops
some
projects
didn't
succeed,
but
ultimately
they
were
drastic
changes
and
basically
for
projects
like
jenkins
that
existed
for
a
long
time.
There
were
a
lot
of
periods
with
different
architectures
and
different
solutions,
even
if
the
name
remains
the
same
jenkins,
one
of
the
its
biggest
advantages
and
disadvantages
has
always
been
a
framework
nature.
So
it's
not
something
like
ready
to
fly.
A
You
just
build
something
on
your
own,
so
jenkins
is
not
a
tool
that
does
continuously
vary
openly
integration,
it's
automation
framework
which
you
take
adjust
for
your
cases
and
start
using.
You
need
to
do
that.
You
need
to
have
a
lot
of
configuration
infrastructure.
You
need
to
stop
plugins,
configure
everything
right,
samples
and
demos
for
your
teams
and
also
write
documentation.
A
A
Again,
one
of
the
biggest
things
of
framework
is
that
it
falls
apart
without
proper
maintenance,
so
it
requires
continuous
investment.
It
requires
special
expertise
and
this
expertise
is
again
a
cost
that
falls
on
your
team
as
a
cost
of
ownership.
So
sometimes
you
don't
want
to
take
framework.
Instead
of
that
you
take
sas,
you
take
a
managed
system
because
it's
much
cheaper
for
you
and
you
don't
have
to
find
a
special
expertise
for
your
team
jenkins
is
different.
A
It
it's
great
for
big
projects,
it's
great
for
custom
projects,
it's
probably
not
that
great
for
common
use,
cases
anymore,
and
naturally
it's
framework
richness,
also
it's
too
difficult
learning
curve,
because
you
start
from
very
something
very
easy
like
make
build
or
maybe
in
a
clean
package,
then
you
install
plugins
configure
them.
Then
you
end
up
with
hitting
various
limitations.
You
can
resolve
by
your
custom,
plugins
advanced
features,
and
you
start
working
on
that.
A
A
Another
array
is,
of
course,
compatibility
because
10
years
of
compatibility
also
have
a
cost,
including
various
architecture,
issues
old
libraries-
if
you
take
a
look
at
that
in
github
jenkins,
spends
significant
time
just
updating
dependencies,
cleaning
up
security,
vulnerabilities
and
many
of
the
things
actually
come
from
historical
or
old
architecture
and
yeah.
Some
might
issues
also
impact
scalability.
A
So
we
know
that
in
jenkins,
most
of
the
things
happen
on
the
controller
instead
of
modern
approaches,
when
the
most
of
the
workload
goes
to
executor
and
controllers
tend
to
be
either
ephemeral,
then
this
is
not
a
thermal
arrangement.
This
is
not
cloud
native
as
controller.
You
can
build
a
cloud
native
system
on
the
top
of
it,
for
example,
ask
how
people
in
viktor
schlapp,
built
it
or
and
sap
built
it,
but
still
the
junkies
itself
is
not
cloud
native
and
is
quite
heavy,
and
it
creates
a
serious
lot
of
infrastructure.
A
A
So
thanks
to
many
contributors
and
to
the
ux
in
the
recent
years,
its
visualization
improved
a
lot
navigation
improved
a
lot
and
also
we
addressed
many
common
issues
like
switching
from
table
layouts
to
diff
layouts,
having
better
navigation
between
chronography,
typography
and
also
a
lot
of
ux
features
in
terms
of
sorting
panels.
So
it
becomes
more
useful.
A
Another
issue
for
jenkins
again
coming
from
its
old
style
that,
wherever
you
go,
you
may
see
all
jenkins,
because
jenkins
in
2011
was
completely
different.
One.
There
were
freestyle
jobs.
There
were
plugins
like
custom
tools,
plugins
engineer,
parameterized
trigger
you
used
to
build
change
chains
of
jobs
with
triggers
copy
artifacts.
A
It
was
terrible
design
which
was
sometimes
having
deadlocks,
and
actually
all
these
stuffs
are
still
there
and
they're
reasonable.
In
many
cases,
when
you
don't
want
to
invest
much
when
you
just
need
a
simple
build
use
case,
but
for
classic
pipelines,
of
course.
Currently,
we
would
recommend
the
genius
pipeline
or
integration
with
stick
tone,
and
this
is
something
that
still
hits
us
so
for
us
we
are
currently
in
the
stage
when
jake
is
super
popular.
A
At
the
same
time,
it
has
a
lot
of
struggles
with
growing
to
the
new
next
generation,
especially
being
cloud
native
being
well
suited
for
the
new
world.
When
you
have
a
thermal
executors,
when
you
have
a
lot
of
interoperability
between
tools
when
tools
become
super
modular,
it's
a
fifth
generation.
I
didn't
include
slides
from
that,
but
I
am
happy
to
discuss
some
koine
and
full
evolution
of
ci
cd
is
listed
as
linked
above.
A
So
what
we
need
to
do
in
jenkins
is
actually
we
as
classic
gear
set
in
2018,
and
it
still
becomes
fully
relevant.
We
are
still
stuck
in
the
local
optimum,
so
jenkins
itself
actually
was
it's
very
relevant
for
the
modern
world.
But
if
we
talk
about
the
perspective
in
five
ten
years,
it
will
become
an
issue
because
at
the
moment
people
move
on
to
cloud
native
approaches.
People
move
on
to
better
designed
tools
for
specific
use
cases.
They
integrate
ci
cd
orchestration.
A
A
One
year
ago
I
published
my
vision
about
jenkins.
It
took
a
lot
of
time
to
publish
it
because
of
various
approval
from
my
previous
employee
etc.
But,
finally,
it's
public
and
you
can
see
my
vision
for
jenkins
now
I
will
just
summarize
what
I
want
to
see
and
we
will
be
will
be
able
to
discuss
more
during
the
contributor
summit
in
two
days.
A
So,
first
of
all,
for
me,
jenkins,
is
not
just
a
project.
For
me,
jenkins
is
a
community
first
and
if
the
community
wants
to
proceed
in
a
direction
like
making
cloud
native
for
me,
it's
fine,
even
if
it
impacts
the
project
itself
at
the
moment,
and
even
if
jenkins
community
says
that
we
want
to
build
a
new
tool
like
let's
say,
jenkins
sex,
another
iteration
is
egreg.
Maybe
I
don't
know
it's
totally
possible,
but
at
the
moment,
from
what
we
see
drank
is
still
remains
totally
relevant.
A
It
was
designed
well
thanks
to
kosuke,
and
it
still
remains
as
a
core
but
yeah.
I
wanted
to
emphasize
that
for
me,
the
biggest
objective
in
genghis
right
now
is
making
jenkins
the
best
place
to
contribute
so
what
it
means
it
means
building
a
welcoming
community.
That
would
be
diverse.
That
would
be
focused
on
future
so
on
having
jenkins
here
to
stay
as
a
community
and
maybe
as
a
project
having
fully
open.
A
So
it's
not
just
having
code
it
having
fully
transparent
communications
decision,
making
open
governance
and
not
having
a
single
vendor
dominated
on
the
market.
So
I
want
to
have
a
fully
rendered
neutral
community,
which
would
be
welcoming
to
all
individual
and
company
contributors
and
users
and
making
them
enabled
to
participate
in
all
areas.
So
it
could
be
jenkins
core
jenkins
pipeline,
whether
it's
plugins,
whatever
it
is
security
engines,
so
without
any
implicit
vendor
lock-in
in
open
source
components.
Unfortunately,
we
had
the
cases
before,
and
this
is
something
we
need
to
get
rid
of
watching.
A
This
is
a
project.
First
of
all,
I
want
to
see
jenkins
anywhere,
so
it
means
that
jenkins
becomes
installable
in
kubernetes
outside
kubernetes.
On
a
new
major
public
cloud
providers,
we
have
an
opportunity
to
run
junkies
just
as
a
pipeline
engine
using
junkies
file
runner.
We
can
integrate
it
into
other
systems,
so
I
do
not
long
to
see
jenkins
anymore
as
an
integrated
solution
like
for
me.
It's
automation
engine
is
a
and
a
bunch
of
components
that
can
be
repackaged
as
needed
for
ci
cd
needs
of
other
users.
A
Also,
I
want
you
guys
to
become
more
cloud
friendly.
I
don't
say
cloud
native
because
I
don't
believe
in
cloud
native
for
jenkins
is,
but
I
think
that
we
should
adjust,
so
we
should
make
it
smaller,
modular,
more
scalable
and,
at
the
same
time
provide
the
great
experience
of
junkies
automation
server.
So
for
me,
this
main
reason
why
we
cannot
make
jenkins
cloud
native,
because
in
this
case
it
would
lose
a
lot
of
its
advantages
as
automation.
Server.
A
Factor
of
it.
So
at
the
same
time,
if
something
needs,
we
can
add
more
features
and
we
still
be
need
to
be
security
first,
so
things
like
casio
solo
means
do
not
repeat
through
jenkins,
and
for
that
of
course
we
need
to
be
invested
more
in
security
as
a
community.
So
thanks
a
lot
to
wadick
following
daniel
beck
and
all
the
contributors
who
push
security
forward.
I
believe
it's
important
for
the
project
and
it
should
keep
happening
as
it
used
to
before.
A
So
we
have
a
few
minutes
left.
I
will
just
summarize:
what's
going
on,
you
can
see
all
the
slides
on
the
roadmap
so
for
user
experience,
the
result
of
changes
thanks
to
james
farazek
and
to
other
project
contributors,
of
course,
tim
jackham,
who
contributed
a
lot
to
the
community
and
to
kevin
who
created
site
search
and
who
is
currently
working
on
the
new
js.
A
The
way
you
repackaging,
so
we
wanted
to
have
all
sets
of
user
experience
in
place,
not
just
code,
not
just
ui,
no
just
documentation,
but
we
want
to
make
a
journey
of
junkies
users
and
administrators
beta,
and
it
includes
revamp,
includes
documentation
and
guidance,
and
one
of
the
topics
we
always
talk
about
is
better
pipeline
browsing.
So
I
want
to
have
a
kind
of
lotion
by
defaulting
jenkins
and
this
kind
of
drastic
decision,
because
right
now
I
would
say,
jenkins.
A
Pipeline
roadmap
is
rather
stalled,
nothing
happens
there
and
I
currently
believe
that
something
needs
to
be
done
in
a
radical
way
in
genghis
pipeline.
So
one
of
the
things
pipeline
is
yellow
movie
is
in
a
high
demand.
We
need
to
finish
it.
We
have
jenkins
templating
engine,
we
have
job
dsl
integration
and
we
need
to
make
them
a
part
of
a
default
offering
for
the
majority
of
users.
A
You
want
to
have
idea,
integrations,
documentation,
improvements
and
one
of
the
things
I'm
always
talking
about
is
maybe
making
jenkins
pipeline
engine
pluggable
so
that
other
engines
could
be
used
as
well.
For
example
like
tecton
for
me,
in
recent
years,
jenkins,
pipeline
sustainability
has
been
a
question
and
personally
I
believe
that
champions
should
be
able
to
support
other
pipeline
engines
by
default
classic
platforms.
There
were
a
lot
of
good
changes,
so
recently
we
released
supports
for
different
platforms,
including
karma.
A
There
is
preview
for
java
17
support,
please
try
it
out
and
they
give
us
some
feedback,
and
there
is
a
lot
of
various
housekeeping
initiatives
going
on
to
make
jenkins
effective,
to
make
jenkins
suitable
for
classic
platforms
and
use
cases.
And
again
this
scenario
where
we
always
look
for
contributors.
A
At
the
same
time,
it's
important
to
be
in
the
cloud
native
ecosystem,
and
nowadays,
when
we
see
say
cloud
native,
we
say
kubernetes
for
better
or
worse,
and
this
is
actually
something
we
need
to
have
more
in
the
projects.
We
already
invested
a
lot
as
a
community,
so
we
have
official
hand
charts.
We
have
a
jenkins
kubernetes
separator
which
keeps
evolving,
which
got
two
commercial
offerings
based
on
that
which
gets
more
and
more
adoption.
So,
thanks
to
everyone
who
facilitates
this
areas,
we
also
have
jenkins
file
around
as
a
pipeline
engine.
A
Cloud
native
pipeline
engines
like
tipton,
would
fit
there
well
also
all
stories
for
pluggable
storage,
ideal,
blake,
breaker
and
one
of
the
biggest
things
that
we
have
a
lot
of
stories
in
preview
which
we
need
to
get
over
the
line,
so
cloud
native
seek
is
dormant
again,
and
I
think
we
need
to
revive
that
somehow,
okay,
so
what
sells?
On
my
wishlist
field,
adoption
of
open
telemetry
having
a
cd
events
integrate
for
triggering
and
sending
commands
having
more
observability
so
for
valence,
metrics
traceability.
A
I
really
want
to
have
tickton
as
a
first
class
pipeline
engine
in
jenkins,
and
I
want
to
have
extension
points
so
that
anyone
can
integrate
other
pipeline
engine
they
and
from
the
evolution
standpoint.
I
think
that
jenkins
should
rather
focus
on
automation,
use
cases
where
it's
perfect
and
probably
it
should
be
doing
less
orchestration,
because
there
are
other
tools
that
are
more
designed
for
that,
including
spinning
care
jenkins,
sex
captain.
A
A
A
His
roadmap
needs
to
be
outdated,
something
we
will
discuss
at
the
contributor
summit,
many
projects
underway,
and
I
believe
that
jenkins
in
2022
worth
exploring,
especially
when
you
have
complex
automation,
use
cases
that
can
be
covered
by
other
tools
out
of
the
box
and
as
always,
it's
great
time
to
contribute
in
jenkins.
We
are
always
looking
for
contributors
for
different
areas,
like
code,
documentation,
testing
design
reviews
and
basically,
if
you're
interested
in
open
source.
A
If
you
are
interested
to
participate,
you're
able
to
find
something,
an
open
source
way,
you
could
contribute
and
talk
to
us
at
the
computer
summit.
If
you
want
to
focus
on
particular
areas,
contributing
is
nothing
about
code
and
if
you
are
just
ranked
user,
if
you
want
to
share
your
experiences
with
jenkins,
it's
also
really
valuable
for
the
community
and
we
have
platforms
to
share
that
including
meetup
blogs,
etc.
So,
if
you're
interested
to
share
with
the
community,
you
can
do
that
and
again
reminder.