►
Description
(View Slides: https://goo.gl/swxWyb)
Pipeline as code is becoming the standard when it comes to defining jobs in Jenkins. Now we need a similar solution to maintain Jenkins itself.
The Jenkins Configuration as Code Plugin allows us to manage Jenkins and its plugins configuration via human-readable configuration files.
Ewelina (https://github.com/ewelinawilkosz) and Nicolas (https://github.com/ndeloof) will talk about the how the plugin works, the current features, and future plans. They will also discuss how (and why) they work on the plugin and how you can contribute. The session will include with a live demo of the current version of the plugin.
GitHub: https://github.com/jenkinsci/configuration-as-code-plugin
JEP: https://github.com/jenkinsci/jep/blob/master/jep/201/README.adoc
A
Everyone
welcome
to
a
Jenkins
online
Meetup,
I'm,
Liam
Newman
I'll,
be
your
host
for
today.
Today,
we'll
be
talking
about
Jenkins
configuration
as
code.
It's
a
new
project
being
hosted
by
practie
sponsored
by
Evelyn,
o
Eveline
Oh
bill
cults,
bill,
cosh,
sorry
and
Nicola
aloof
and
they'll
be
telling
us
all
about
it
today,
Evelina.
What
do
you
take
away?
Oh
wait.
Sorry,
my
bad
we'll
be
doing
questions
on
the
IRC
channel,
the
the
Jenkins
IRC
channel,
hashtag
drinkin's
I'm
go
over
there.
A
B
You
hi
everyone
so
today,
as
Liam
mentioned
well,
we'll
talk
about
Jenkins
configuration
as
code,
we're
gonna
tell
you
why
we
do
it,
how
we
do
it,
what
it
exactly
is
and,
most
importantly,
how
you
can
get
involved
if
you're
interested
in
that,
but
let
me
introduce
myself
and
then
Nicola
who
who
proved
them
together
with
me
today,
Wesley
I
mentioned
my
name
is
Evelyn
until
Akash
and
I
work
as
IT
consultant
at
pragma.
I
was
a
software
developer
before
for
six
years
at
Ericsson,
but
I
decided
to
join
the
continued
integration.
B
B
C
So
I'm
Nicola
drove
I'm
working
at
Toby's
as
part
of
the
CTO
office,
I'm
a
Jenkins
contributor
for
a
few
years
now,
and
also
trigger
captains
or
involved
in
visor
to
go
plugins
and
as
part
of
the
job
I
was
involved
in
investigating
some
ice
core
principle
for
setting
up
Jenkins
my
presence
here
and
as
I'm.
Also
a
conference
organizer
in
my
local
city
beat
up
organizer
and
also
doing
some
videos
or
I.
You
welcome
to
join
me
on
youtube,
but
anyway,
let's
focus
on
the
configure
Scott
for
today.
B
Thank
you,
so
those
of
you
who
are
ever
trying
to
start
up
their
own
Jing
all
that
it
can
be
installed
in
a
very
different
way
from
native
system
packages
using
docker
can
be
run,
stand
alone
by
any
machine
that
has
has
Java
installed,
but
doesn't
matter
how
you
run
it
most
of
the
time
you
have
to
manually,
configure
it
so
so
you're
familiar
probably
with
that
kind
of
page.
It
may
not
be
very
readable,
but
but
yeah
this
page
can
become
much
much
much
longer,
and
this
is
only
a
small
small.
B
That's
me
start
up
new
Jenkins
instance.
We
have
to
go
through
the
pain
of
feeling,
all
the
all
the
information,
and
we
don't
always
like
that.
I
can
imagine.
There
are
situations
that
yeah,
maybe
it's
comfortable
and
easy,
especially
if
you're
in
it
most
of
the
time
I
I'm
gonna
risk
the
statement
that
we
don't
like
that.
So
I
would
like
to
get
rid
of
that
part.
So
the
question
is:
how
do
we
solve
it
and
knowing
who
will
solve
it?
B
A
B
B
A
lot
of
discussions
about
how
to
how
abbreviate
it
and
I
think
like
yeah
most
of
us
are
happy
with
Jake
asked
but
yeah
before
I
dive
into
Jake
asked.
Let
me
explain
how
it
started.
It
will
be
a
very
short
story,
so
it's
idea
that
we
want
to
make
it
easier
for
our
customers
to
spin
up
their
Jenkins
instance
to
make
it
more
safe,
more
reliable
and
easy
to
reproduce
our
least
touring
casement
Feiler.
So
we
started
this
Jenkins
s
code.
B
Reference
project
that
is
successfully
successfully
rolled
out
in
a
number
of
our
customers
and
pragma
itself
is
using
this
this
project
for
our
own
Jenkins,
but
during
that
and
what
our
customers
would
discover
that
it
has
some
paints.
So
it
requires
everyone
who
wanted
to
use
it
to
be
all
in
to
use
a
very
specific
docker
solution.
B
It
was
complicated
and
it
has
complicated
and
time-consuming
radically
deployment
process
and
I
have
those
quote
a
quotation
marks
because
it's
not
really
very
complicated
and
the
time
is
a
matter
of
minutes,
but
in
a
modern
software
development
world
we
minutes
arch
and
too
many
times
it's
becoming
complicated.
Most
importantly,
we
had
what
mixed
with
house,
so
we
were
relying
on
the
solution
provided
by
Jenkins,
allowing
you
to
put
groovy
scripts
in
a
specific
folder
and
the
scripts
would
be
run
when
Jenkins
starts
up.
B
But
we
we
had
configuration
the
groovy
scripts
mixed
with
the
actual
configuration
of
specific
Jenkins
instance,
and
we
decided
that
we
don't
like
it
a
lot
and
we
need
to.
We
need
to
product,
will
have
the
same
functionality,
but
will
be
easy
easier
to
maintain
easier
to
use
with
Jenkins
s
called
reference
which
I
still
like
and
feel
very
comfortable
using
that
we
we
weren't
happy
with,
like
forcing
users
to
fork
repository
to
actually
use
use
our
product.
B
That's
what
we,
how
we
came
up
with
the
idea
of
creating
a
plugin
that
you
can
very
easily
download
and
and
will
not
repeat
the
X
with
with
jenkins
s
code
reference,
so
jake
ask
is
actually
jenkins
plugin
that
is
available
via
this
link
on
geek
pub
and
I'm.
Assuming
will
have
a
way
to
share
this
possession
in
some
way.
So
all
the
links
we
can
see
here,
you
should
be
able
to
like.
A
B
So
we
hope
this
Jenkins
configuration
is
called
plug-in
will
be
D
configuration
is
called
solution
for
Jenkins
and
there
is
a
Geoff
Jenkins
enhancements
enhancement
proposal
document
little
that
is
still
in
that
state.
Where
you
can,
you
can
comment
and
discuss,
proposed
solutions
and
ideas.
So,
if
you're
interested
in
the
future
of
the
project-
and
you
have
ideas
please
through
that
patient-
we
had
Jenkins-
is
called
reference
project
and
I
mentioned
it's
paints,
but
I
don't
want
this
plug-in
to
the
only
a
solution
for
my
issues.
A
So
sorry
interpret
you're,
basically
describing
how
most
plugins
probably
started.
Someone
had
a
problem
they
wanted
to
solve
for
themselves
and
then
made
it
a
little
more
general
and
then
put
it
out
in
the
open
in
the
past.
We
would
the
project
would
just
sort
of
organically
you'd
have
one
person
running
that
that
plugin
and
they
would
sort
of
own
the
feature
said
and
all
of
that
all
at
once
and
just
for
people
that
aren't
familiar
with
it.
B
And
the
more
people
involved
in
the
early
stage,
the
more
chances
for
a
success
in
the
future.
So
we
started
at
pragma
me
and
a
couple
of
my
colleagues
working
on
some
solution,
and
then
we
got
in
touch
with
Kostka
and
nicola
and
oleg,
and
they
are
also
working
on
on
similar
solution
and
the
ideas
we
have
and
the
requirements
we
have
are
much
very
much
aligned.
B
So
we
decided
to
work
together,
which
meant
it
was
not
exactly
how
we
at
the
beginning,
but
well
we're
happy
that
we
were
able
to
change
the
direction
at
the
very
beginning.
So
for
some
time
it
was
pragmas
and
cloud
with
effort
working
on
that
plugin.
But
a
couple
of
alpha
racists
were
are
already
available
out
there
and
we've
already
got
some
external
contributors
and
I
have
no
idea
how
they
found
out
about
the
project,
but
I'm
very
happy
they
did
so
we
have.
B
We
have
have
Tyrael
happened,
a
couple
of
other
guys
that
are
contributing
via
creating
issues.
We
are
providing
documentation
or
even
implementation.
So,
thank
you
very
much
guys
and
like
whoever's,
interested
yeah
to
the
github
repository
where
we
use
for
now
you're,
almost
using
github
issues
to
discuss
and
track
the
progress.
Oh.
A
So
I
wanted
to
say
on
that
subject:
you
should
ask
them,
because
I
would
be
interested.
You
know
how
they
how
they
found.
You
I
mean
some
people
probably
are
just
subscribe
to
the
drinkin's
CI
github,
or
something
like
that,
but
if
they
it'd
be
interesting
to
know
where
they
how
they
picked
this
up.
I
mean
this
is
obviously
really
an
interesting
area
for
someone
running
Jenkins
in
general,
but
if
we
can
ask
them
afterwards,
yeah.
B
A
B
So
once
again,
thank
you
guys
and
yeah.
We
want
to
go
so
you
don't
have
to
be
a
hacker
or
a
very
experienced
Jenkins
user
to
to
start
using
Jenkins
configuration
as
code,
so
in
general
the
idea
is
that
you
have
to
write,
prepared,
James,
yeah,
no
file
and
store
it
on
your
local
disk,
store
it
in
a
repository
where
how
we
haven't
maintained
it.
That's
another
thing,
but
very
simple
idea.
We
have.
B
We
have
Yama
file
that
is
being
given
when
to
think,
and
whatever
you
have
under
manage
Jenkins
should
be
should
be
configured
automatically
during
startup
or
when
Jenkins
is,
is
working
which
I
will
show
during
a
very
short
demo,
so
simply
configure
global
security,
page
credentials,
tool
configuration
plugins.
Those
are
sections
that
we
want.
Jenkins
configuration
as
code
plug-in
angle
in
benefits
that
I
see
is
well
safety,
security
and
traceability.
That
will
be.
B
B
Restart
Jenkins
hands
in
case
of
I,
don't
know
a
disk
failure
where
you
have
to
move
it
to
another
machine
or
if
you
use
containers
or
if
for
some
reason
you
need
to
stands
because
we
have
another
project
and
another
company
buddy
her
working,
Jenkins,
configurable,
Jenkins
configuration
and
Scott.
It
is
simply
copy.
Jenkins
ya,
know,
file
and
change
things.
You
want
to
change,
and
then
you
have
your
Jenkins,
your
new
Jenkins
working.
So
it
should
be
easy
to
use
and
easy
to
be
used
in
case.
You
need
to
scale
right.
C
Yeah
point
you
mentioned
really
now
is
that
we
don't
make
any
assumption
on
the
ways
this
general
file
is
told,
so
it
can
be
provided
from
SCM
repository
or
whatever
code
management
system.
You
are
using
may
be
adopting
chef
to
patrol
writing
by
hand
if
you
really
want
to,
but
we
can
just
embrace
all
practice
in
terms
of
operations.
C
B
Exactly
so,
we
have
this
great
ideas
about
this
great
product,
but
of
course
there
are
some
challenges
and
for
now
you
can
see
a
slide
that,
with
a
summary
of
this
chart,
yes,
but
each
one
of
those
channels,
so
I
will
just
move
on
a
human-readable,
config
files.
So
I
already
mentioned
that
we
will
use
llamó.
We
had
a
discussion.
B
B
A
B
The
fact
that
we
don't
need
to
use
different
kinds
of
brackets,
it's
not
it's,
not
the
only
advantage
of
llamo,
it's
very
easy
to
read
and
I
I
mean
find,
probably
even
for
people
that
are
not
software
developers.
It's
it's
not
a
rocket
science,
it's
commentable
and
it's
not
language
centric.
So
it's
not
like
you,
you,
you
know
specific
programming,
programming
language
and
it
gives
you
the
advantage.
So
if
it's
what
we
decided
to
go
with
because
of
the
how
easy
to
use
it.
A
C
B
Yep
so
another
like
the
biggest
challenge
now
hands
on
keyboard
now,
click
on
UI
should
be
should
be
possible
to
get
that
fully
working.
Thank
you
smash
without
those
elephants.
At
some
point
you
have
to
click
at
some
point.
You
have
to
use
keyboard.
It
needs
to
prepare
the
Jenkins
UML
file,
but
when,
when
the
basic
stuff
is
it's
ready,
you
can
you,
you
should
be
able
to
easily
automate
it
and
we
mesh
risk
stability
is
a
failure,
so
you
want
to
prepare
your
configuration
and
automation
scripts
again.
B
The
plugin
does
not
care
about
how
you
start
up
your
Jenkins,
so
it's
not
like.
We
will
provide
it's
your
way
to
fully
be
start
without
without
clicking
anywhere.
You
can
use
docker.
You
can
use
another
solution
and
we
will
talk
about
that.
Some
places
where
you
can
find
some
some
help
regarding
that,
but
but
general,
it's
only
about
configuring
Jenkins,
but
once
once
the
configuration
file
is
ready,
you
should
be
able
to
avoid
UI.
If
you
don't,
if
you
don't,
don't
want
it
also
very
important
thing,
if
not
all,
of
the
plugins
by
default.
B
So
the
first
idea
I
mentioned
that
we
we
got
in
touch
with
cloudBees
and
they
had
similar
go,
maybe
a
little
bit
different
idea.
So
I'm
at
the
first
day,
I
had
was
like
yeah
right
support
for
every
plugin
and
then
realize
that
we
have
more
than
a
thousand
and
a
half
plugins
already
available,
and
even
if
not
all
of
them
are
configurable
in
this
managing
global
mission.
Still
it
would
be
a
lot
of
code
right.
B
So
smart
solution
is
where
we
don't
need
to
write
glue
code
for
every
supported,
plugin
and
we
hope
to
support
most
of
the
plug-in.
Actually
is
the
ones
that
are
written
following
some
conventions
to
support
them
out
of
the
box,
or
it's
not
the
case
right
now.
We
still
need
some
dedicated
solution
for
dedicated
Claggett
for
a
specific
plan.
It
means
and
I
think
perhaps
later,
but
nevertheless
we
believe
that
this,
this
plug-in
jenkins
configuration,
is
called
plugin
without
an
extra
effort.
B
I
mean
we
already
know
that
without
an
extra
effort,
a
number
of
plugins
are
already
supported,
and
if
there
is
some
there
is
a
plugin
that
is
not
currently
supported.
We
can
either
create
some
solution
on
Jenkins
configuration
is
called
plug-in
site
or
we
can
submit
a
Chan
for
the
for
the
plug-in.
So
it
depends
on
specific
case,
but
we
have
different
ways
to
solve
potential
issues.
B
Also.
What
what
we
want
to
achieve
and
make
available
for
you
is
to
generate
documentation
and
validation
tools.
So
again
we
don't
have
to
write
everything
manually,
and
so
you
don't
need
to
be
a
Jenkins
experts
to
prefer
Jenkins
e
mo
file,
because
documentation
will
be
available
and
Lara
way
to
how
job
DSL
plug-in.
Does
it.
When
you
use
job
DSL
plug-in,
you
can
have
access
to
an
API
view
viewer
on
your
local
Jenkins
instance.
B
That
will
reflect
you,
your
the
installation,
so
the
plugins
you
have
installed
will
be
listed
there
and
support
for
this
plug-in
and
how
you
can
use
DSL
for
those.
So
it
will
be
similar
for
us,
as
you
will
have
a
documentation
based
on
your
Jenkins
instance,
when
you,
when
you
use
Jenkins
configuration
s
code
supporting
plugin,
sorry
and
so
yeah.
We
have
ideas,
we
have
challenges
and
telling
for
to
github
repository
with
the
plug-in
was
already
mentioned.
B
In
one
of
the
previous
slides,
but
here
it
is
again-
and
there
are
two
very-
very
interesting
and
important
Alden
files
in
this
repository,
one
one
of
the
files
is
implementation,
detail
description
and
we
also
have
guide
for
plug-in
developers.
I
mentioned
that
plugins
that
follow
some
all
this
project
of
the
box
and
the
plug-in
plugins
and
e-file
describe
what
we
need
in
a
plugin
to
support
it
with
Jenkins
configuration
is
gold
so
before.
A
We
before
we
head
on
just
for
a
second
I'm,
just
gonna
hop
in
here
and
for
those
who
arrived
after.
We
started
we're
taking
questions
on
IRC.
If
anyone
has
any
questions
go
over
to
the
Jenkins
channel
and
IRC,
and
you
can
ask
them
there
and
actually
there
was
someone
who
was
asking
whether
or
not
I
know
you
guys
are
still
in
process
on
the
discipline
features
that
he'll
talk
about
that
you
guys
are
working
on
later,
but
can
you
can
you
create
jobs
as
part
of
the
Jenkins
configuration
is
coded?
B
A
C
A
B
Okay,
so
yeah
well,
nothing
it'll
go
go
through
whatever
was
mentioned
thereafter
and
we
can
have
a
discussion
about
creating
some
new
features
but,
as
Nicola
said
another
case
for
now,
but
okay
yeah,
so
actually
that's
a
that's.
The
time
we're
in
e.coli
is
the
you
can
go
over
to
I
will
stop
shooting
this
girl's,
gonna
Nicola
right.
A
D
This
configuration
is
called
I
mean
now
O'connor's,
so
the
order
that
firstly,
configurations
could
plug
in
runs
and
then,
if
you
need
to
do
something
else,
you
can
use
all
style
mechanism
to
do
configurations
code
if
needed,
and
is
that,
for
example,
the
configuration
is
code
reference
Evelina
referenced
in
the
beginning,
beginning
also
uses
crew,
be
hooks
right,
all
right,
no
okay!
So
technically
you
can
I
use
both
solutions
if
you
want
but
yeah.
Of
course,
it
requires
some
attention
because
you
make
course
collision.
C
C
C
So
we
just
join
force
on
this
topic,
and,
and
so
what
I
want
to
introduce
here
is
is
how
we
can
pass
yeah
Mel
file
likes
when
I'm
just
showing
here
to
get
Jenkins
master
configured
without
getting
anything
change
on
Jenkins
core
or
any
of
the
plugins
that
you
have
installed
so
the
first.
The
first
point
for
the
parser
is
to
be
able
to
to
to
identify
the
target
components
that
we
are
trying
to
configure.
C
So
in
this
ml
5
we
have
the
Jenkins
root
element
and
we
also
have
a
major
root
element,
so
in
term
of
plug-in
API
is
we
have
dedicated
API
for
this
root
element,
configurate
role
and-
and
this
guy
comes
with
some
default
implementation.
As
you
can
guess,
we
provide
one
for
search
engines
root
instance.
We
also
have
configured
roles
for
the
BIOS
global
configurations
that
you
have
all
your
plug-in
descriptors.
C
We
just
use
a
simple
name
like
so
may.
Looking
for
some
welcome
with
this
mailer
root
element
and
as
we
do
now
explained,
we
come
with
some
default
mechanisms
that
we
expect
to
cover
most
leggings,
but
there
is
always
some
kernel
cases,
and
so
typically,
we
have
one
with
the
credentials
begin,
so
we
created
as
a
proof-of-concept
credential
with
configurators
that
introduces
trillion
shots
retainment
and
allow
us
to
just
plug
some
specific
adapter
code.
C
C
Now
the
second
level
from
this
Jenkins
root
object
is
what
we
call
an
attribute.
So
you
can
just
think
in
terms
of
Java
code
like
Java,
Bean
properties,
that's
exactly
the
same
thing.
So
here
we
have
the
security
wheel.
We
define
some
abstraction
here
as
well.
An
attribute
has
just
named
a
target
type
can
be
a
collection
of
things,
just
a
single
element,
and
we
need
some
way
to
set
a
value.
So
there
is
no
requirement
to
have
javabean
setters.
C
That
can
be
something
very
abstract
with
a
custom
implementation
where
time
thinking
here
is
anything
about
doing
some
lookup
to
drag
a
singleton
or
whatever
other
truckers
who
want
to
write.
So
the
external
API
is
just
to
say,
I
have
a
name:
I
have
a
type
and
I
want
to
set
the
value
generic
generic
mechanism,
it's
just
to
rely
on
javabean,
setters
or
the
tab
on
constrictor
for
for
new
objects.
You
want
to
create.
So
following
this
simple
rule,
we
have
set
security.
C
Reading
that
allow
us
to
to
set
this
this
attribute
and
the
parameters,
the
target
type
actually
is
an
extension
point
which
means
execute
with
dream
is
an
abstract
class.
So
the
next
step
for
configuration
s
code
is
to
understand
which
specific
implementation
we
want
to
set
up
and
only
input
we
have-
is
this
Eldad
string?
C
So
what
we
do
here,
as
we
know,
the
type
that
we
want
to
create,
is
we
have
a
list
of
candidates
based
on
the
install
plug-in
on
the
specific
Jenkins
master?
So
some
component
already
are
using
the
symbol
annotations,
so
we
already
have
a
name
for
them,
which
is
used
to
be
a
very
short
one,
human
friendly
name,
and
for
so
for
also
plug
in
some
legacy
wants,
or
maybe
some
of
them
just
didn't.
Yet
up
adopted
this
practice,
we
rely
on
some
pattern.
C
Discovery
something
that
Java
developer
used
to
do
when
the
implement
an
API
is
that
they
use
this
IP
API
name
as
a
suffix
for
the
class
name.
So
for
samples,
the
LDAP
security
rhythm.
We
can.
We
can
guess
what
I
like
to
call
a
natural
run,
name
as
LDAP
by
just
removing
so
extension
class
name
and
and
based
on
this,
we
can
discover
them.
The
requested
LDAP
implementation
is
not
just
LDAP
security,
WinForms.
Well
that
pregnant.
So.
C
But
workarounds
for
to
avoid
what
we
want
to
have
already
here
is
to
enforce
people
to
use
fully
qualified
class
name
for
those
of
you
who
have
been
adopting
pipeline
at
the
early
beginnings.
There
was
many
places
where
you
had
to
use
some
dollar
class
and
the
fully
k4
class
name
of
your
target
component,
which
resulted
in
the
ugly
script,
and
thanks
to
this
single
annotation,
we
know
have
a
very
simple
way
to
just
express
which
component
we
want
to
use.
C
That's
it's
a
main
issue.
When
you
come
with
such
a
new
solution
is
we
can
make
some
pull
requests,
but
it's
really
hard
to
get
a
pull
request
approved
for
some
things
that
is
still
in
early
development.
So,
let's
say
I
come
to
the
active
directory
maintainer.
That's
asked
him
to
ask
a
simple
institution
that
I'm
using
on
my
pre-alpha
configuration
as
clicking
I
guess
he
won't
be
really
happy
to
just
match
because
I'm
asking
he
wants
to
have
some
concrete
reason
to
do
that,
and
so
we
have
this
balance.
C
We
offer
a
simple
way
to
have
some
reasonable
name,
and
there
is
probably
some
cases
where
it
won't
be
enough
and
for
those
we
will
require
some
symbol
annotation,
but
we
already
have
a
good
solution
to
to
keep
human
friendly
name
into
the
morph
description
cool
right.
So
so
here
we
have
identified
the
target
components
that
we
want
to
create
and
to
set
us
Jenkins
security,
Winnie
implementation.
C
So
this
component,
initially
ml
file,
has
certain
amounts.
We
are
using
the
exact
same
logic,
to
set
up
all
the
constrictor
parameters,
so
we
are
using
the
data
burn
constructor.
Here,
generally
speaking,
we
are
relying
on
all
the
UI
binding
mechanism,
because
that's
something
that
enforce
such
the
code
will
be
maintained
by
is
a
plug-in
developer.
We
don't
want
to
introduce
some
new
mechanic
that
will
require
to
keep
in
sync
with
the
UI,
and
we
also
want
those
parameter
to
reflect
as
much
as
possible
so
user
experience
when
they
just
brought
on
Jenkins
web
UI.
C
So
we
expect
that
the
su
forms
created
for
the
web
UI
will
be
using
attribute
names
such
more
or
less
the
same
other
attribute
levels.
So
here
we
have
a
configuration
disabled,
mail,
adress,
resolver
and
in
many
cases
just
attribute
name
is
enough
to
have
some
some
reasonable
name
in
the
ml
file
and,
as
you
can
guess,
we
always
have
some
workaround
to
to
switch
to
other
implementation
when
required.
C
So
you
also
can
see
in
these
samples
that
we
are
supporting
enumeration
with
the
ID
strategy
parameter
and
and
first
youõll
everything
about
data
buildin
setters
for
additional
optional
parameters.
So
with
those
mechanism
where
I
go
to
fully
setup,
LDAP
security
rhythm
and
to
configure
our
Jenkins
master
with
those
options,
but
there
is,
as
you
can
guess,
many
corner
cases,
typically
as
we're
relying
on
setters
there
with
many
setters
that
are
not
really
here
to
reflect
some
things
that
end
user
is
supposed
to
configure.
Some
of
them
are
here
for
the
cassie
reason.
C
Some
of
them
are
here
to
for
internal
binding
between
components,
but
not
designed
to
be
used
by
end
user.
So
we
are
just
reading
the
deprecated
and
restricted
annotations
to
exclude
them
from
the
configuration
s
code.
We
also
propose
to
enlarge
the
use
of
a
symbol
and
addition,
so
it
can
also
be
used
in
setters.
C
So
if
I
have
Java
in
property
with
the
technical
name
like
syllable
stream,
that
exists
on
Jenkins
echo
object
as
the
end
user
is
just
expecting
level,
not
labelled
string,
so
we
can
use
just
one
annotation
to
make
it
simpler
and
for
very
complex
use
case.
One
can
just
come
with
a
dedicated
implementation
for
all
those
components,
and
this
is
exactly
what
we
did
with
credentials.
C
So
what
we
did
here
is
more
proof
of
concept
of
how
to
implement
this,
to
ensure
that
it
is
feasible.
So
actual
support
for
credentials
would
probably
require
to
get
some
feedback
from
the
credential
speaking
maintainer.
The
high
D
ear
is
to
rely
on
simple
syntax,
so
this
one
is
map
syntax
for
llamo,
maybe
something
most
people
are
not
really
used
to.
C
So
we
created
the
dedicated
credentials,
good
configurator
off,
which
handle
everything
in
required
to
introduce
a
fake
attribute
system,
and
this
attribute
is
expecting
a
certificate
gate
key
and
internally.
It
will
do
the
get
instance,
get
domain
credential
mapping
in
injector
key
in
the
map
and
all
that's
logic
that
we
would
expect
to
just
be
coding
a
setter
but
doesn't
exist
in
this
begin.
So
just
this
glue
code,
it's
mostly
ten
lines
of
code,
I,
guess
and
these
enough
for
us
to
introduce
full
support
forces
begin.
C
So
we
know
few
plugins
will
require
to
do
such
adapter
cloud,
and
the
idea
is
so
far
is
to
demonstrate
this
is
feasible
as
part
of
the
contribution
Escott
begin
and
maybe
later
when
the
speaking
is
largely
used,
we
will
be
able
to
migrate
source
custom
configurator
in
target
plugins
themself,
so
this
code
will
leave
directly
in
the
credentials
begin
and
be
maintained
as
part
of
the
credential
speaking.
What
I
have
in
mind
here
is
the
way
the
pipeline
was
introduced
with
support
for
kit.
C
C
A
C
A
C
So
question
work
to
:
and
then
some
items
yeah
so
to
make
it
clear
this.
This
specific
sample
has
been
used
also
to
experiment
with
the
flexibility
of
chameau
in
term
of
configuration
and
how
we
can
expose
as
much
as
possible
what
is
supported
by
the
credentials
bring
in.
We
could
have
something
way
simpler
if
we
just
want
to
let
people
configure
global
system
credentials
on
Jenkins
master
with
a
single
element.
You
know
here,
I
wanted
to
experiment
about
keeping
flexibility
and
how
much
line
of
code.
A
A
All
right,
those
basic
key
to
reduce
them
all
right
that
and
that's
just
currently
the
way
that
we're
we're
doing
it
there
might
be
could
be
changed.
But
it's
a
little
it's
a
little
weird
right,
but
it
is
a
proof
of
concept,
so
this
is
you're
just
figuring
out.
Okay,
we
can
do
it
and
and
they'll
they'll
be
there's
the
possibility
to
change
and
improve
okay
and
so
leave
this
right
in
the
status
of
like
okay,
where
we
are
yeah
exactly.
A
A
B
Or
have
some
plugins
available
in
alpha
version?
I
will
I
will
go
back
to
that
in
a
moment,
but
yeah
I
want
to
I
want
to
highlight
what
key
features
are
already
available,
both
in
the
version
that
you
can
use
o
it
support.
Reading
configuration
file,
Yama
file,
both
from
local
drive
or
whatever
URL.
We
are
using
raw
github
URLs
in
our
demo
setup.
B
There
is
a
ton
available
under
manage
Jenkins
configuration
is
called
reload.
That
I
will
show
you
in
like
two
minutes,
and
we
also
work
on
extending
folder
in
the
posit
re
means
the
list
of
supported
plugins
and
the
the
pieces
piece
of
yell
file
that
should
be
used
to
configure
the
plug-in.
But,
of
course
the
number
of
supported
plugins
is
not
opening
are
available
in
this
this.
This
folder.
This
is
just
just
some
extended
documentation
to
make
it
easier
for
for
newcomers
to
start
using.
B
The
plug-in
I
said
that
if
or
that
we
don't
handle
Jenkins
startup
and
like
maintaining
the
hosting
changes
instance
VR
the
plug-in,
but
we
want
to
make
it
easier
for
you
to
start
the
plugin.
That's
why
we
provide
this
toker
demo
setup
available
under
pragma
drinking's
cask,
a
repository
that
is
also
linked
here
and
actually
a
fork
of
that
repository
is
what
I
used
to
start
up
by
my
demo.
B
We
need
feedback,
so
we
we
can.
We
can
provide
more
features
that
are
willing
that
version
0.3
is
already
available
and
0.4
is
coming,
but
you
have
to
use
experimental,
update
sense
and
the
details
are
available
under
this
link.
But,
of
course,
if
you
search
for
experimental
plugins
update
Center
for
Jenkins,
probably
the
first
result
in
Google
will
take
you
to
the
page
that
describes
how
to
how
to
use
experimental
plugins
up.
B
We
hope
to
have
the
official
release
available
in
May,
2008
18
and
the
features
that
will
come
in
this
release
are
later
releases,
the
things
that
will
want
us
on
our
the
support
for
configuring
configuration
file,
location
not
of
the
VI
URL
only
but
did
repository
and
branch.
For
example.
That's
what
Nicola
was
mentioning.
We
want
to
make
it
flexible,
so
you're
not
being
pushed
to
one
specific
arg
in
the
installation.
Support
is
a
bit
tricky.
There
is
a
discussion
in
in
jab,
ongoing
and
nicola
mentioned
that
sometime.
B
We
need
some
pool
requests
to
another
project
and
it
may
not
very
easy
when
our
project
is
still
in
alpha,
but
anyway
something
is
happening.
So
we
can
support
installing
plugin
different
plugins
in
specific
versions.
Via
jenkins
configuration
is
code
flagging.
Other
people
were
when
we
were
presenting
it
on
different
forums
were
asking
about
how
to
reload
configuration
feature.
We
have
it
on
our
list
and
improve
documentation.
I
thought
that's
something
that
I
really
want
to
have
so.
B
B
You
were
talking
exactly
about
it
with
Nicola.
Today
there
is
some
cue.
There
is
a
pull
request,
waiting
to
be
merged
in
another
project.
So
if
they
manage
to
merge
the
pull
request
before
we
release
the
first
first
version
and
then
it
may
end
up
in
the
first
release,
but
if
they
don't
want
to
support
to
merge
it
too
fast,
because
as
for
the
reason
they
may
have,
we
may
decide
to
release
the
first
version
without
this
plug-in
installation
support.
So
it's
it's
difficult
to
say
like
for
100%.
B
B
Well
present
and
be
available
for
anyone
interested
in
the
plug-in
to
explain
how
we
do
it
in
more
details
and
listen
to
what
what
what
features
are
missing
and
what
would
be
cool.
So,
if
you're
going
to
one
of
Jenkins
worlds,
this
year
we
have
San
Francisco
and
nice
if
I
remember
correctly,
I
think
so.
A
B
A
B
A
B
B
Jenkins
config
environment
variable
to
past
allocation
of
Jenkins
Yama
file
in
this
investing
that
I
provided
in
one
of
the
slides
for
visit
re
with
d'amboise,
well
I've
decided
to
switch
to
because
it's
a
little
bit
easier
and
here
here's
an
example
of
Yama
file
I'm
using
and
someone
asked
about
configuring
jobs.
So
here
is
how
we,
how
we
I
have
two
jobs:
two
pipelines
configured
on
my
Jenkins
doing
start.
This
is
how
I
don't
know
if
you're
familiar
with
job,
DSLR
or
pipelines,
then
it
should
be
like
no-brainer.
B
B
B
B
And
then
the
drink
is
configuration
is
called,
plugin
is
available
under
manage
Jenkins
configuration
is
called,
reload,
reload
happens
and
the
system
message
is
changed
and,
of
course
it
will
work
the
same
way
for
anything.
You
do
want
to
change.
So
it's
very
simple
and
the
one
of
the
features
that
I
made,
but
this
one
first
you
want
to
be
part
of
the
the
first
release
will
be
out
early
loud.
A
B
Yes,
so
in
Jenkins
is
called
reference
I.
We
had
this
like
pipeline
job
that
took
six
minutes.
So
when
you
made
a
change
in
my
you
had
to
like
redeploy
Jenkins
completely
here,
Jenkins
is
working,
so
it
it
works
the
same
way.
You
would
do
it
if
you,
if
you
are
using
Jenkins
in
a
traditional
way,
you
just.
B
C
A
C
A
C
A
B
B
Yeah
so
I'm
gonna
try
once
you
get
get
the
presentation
you
will
have
all
the
links
available
feel
free
to
ask
questions.
My
my
github
handle
or
Twitter
handle
was
available
at
the
beginning,
I
mentioned
we
are
using
github
issues
and
you
feel
free
to
contribute
to
those.
Any
way
you
want
to
contribute
is
a
good
way.
There
is
no
better
or
worse
contribution,
even
if
you
have
a
become
R
and
X
Type
O.
A
We've
actually
been
keeping
up
with
them.
Actually,
during
the
presentation,
let's
see
there
was
one
more
left
over
about,
they
were
asking
whether
or
not
they
were.
This
could
be
used
to
dynamically
download,
plugins
and
I'm
I'm,
trying
to
think
of
what
how
what
this
would
involve
with
it
yeah
it
like.
Can
you
use
this
to
configure
plugins
as
well
I
like
to
add
certain
specific
plugins,
or
is
that
under
discussion.
B
C
If
I'd
so
I'm
working
on
a
pull
request
to
add
support
for
plug-in
management
is
the
main
point
so
far
is
that
what
we
want
to
do
here
is
to
have
full
control
in
term
of
reproducibility,
so
that,
if
you
want
to
have
get
plug-in
3.8,
you
will
always
get
keeping
in
3.8
and
the
same
dependency.
You
you
had
the
first
time
you
you
define
this
installation
and
update
center.
C
Jenkins
only
offers
latest
version
of
things,
so
we
are
looking
for
some
way
to
to
ensure
that
we
really
install
the
expected
set
of
plugins,
and
this
requires
some
me
know,
changes
to
the
update
center
itself.
So
this
still
work-in-progress
not
not
a
big
effort,
but
needs
some
some
discussion
within
for
our
team
and
and
some
more
experimentation,
but
Jack
clearly
that
something
that
is
part
of
the
scope
of
this
begin.
So
maybe
this
won't
be
ready
for
one
dot
all,
but
this
week's
come
through
later,
but
it's
it's
definitely
a
of
interest.
A
A
That's
no
problem
and
I'll
add
the
some
of
the
links
that
you've
that
you
have
in
the
presentation
and
the
link
to
the
presentation
to
the
to
the
to
the
YouTube
description
when
we're
done
here
so
that'll
be
good
there
and,
let's
see
here
so.
Thank
you
very
much.
Yes,
that's
exactly
what
asking
say
thanks
everyone
for
joining
us.
Thank
you
guys
for
presenting
and
for
I,
don't
like
to
thank
pragma
for
sort
of
for
supporting
and
having
you
be
part
of
the
Jenkins
project.