►
Description
Jenkins Configuration as Code project meeting continue after the summer break. We discussed the status of System Read Permission (JEP-224) and plans for its GA, reviewed the recent JCasC releases and ongoing development. In addition to that, we discuss introducing a Configuration as Code SIG in Jenkins.
Full agenda and meeting notes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.eghzmsmgoij7
A
Hello,
welcome
to
the
jenkins
configurations
code
project
meeting
today
is
august
12th,
so
it's
just
over
the
middle
of
summer
break.
So
we
have
two
contributors
on
the
call
team
and
me,
and
I
doubt
that
we
are
going
to
have
more
participants
today,
so
we
will
run
through
the
standard
agenda
unless
there
are
motor
picks
to.
B
A
B
Yeah,
I
think
we
should
be
able
to,
but
I
think
it
was
all
in
the
235
lcs.
I
think.
A
If
I
recall
correctly,
our
tool
page
has
missed
the
lts
and
also
the
view
plugin
compatibility
issues
because
yeah
I'm
just
logging
in.
A
A
So,
let's
take
a
look
so
here
and
they
we
still
have
some
tasks
which
haven't
been
addressed
yet
but
the
agents,
your
access
for
agent
extended
three
trade.
B
A
A
So
here
we
still
have
quite
a
number
of
tasks
to
be
completed,
but
yet
to
be
honest,
I
don't
think
that
it's
really
a
blocker
for
ge.
A
B
A
B
A
B
Yeah
yeah,
I
think
so
when
it
does
just
check
change
the
your
remote
beta
and
have
it
enabled
by
default.
B
B
B
I
think
it
should
be
so
it
was
introduced
in
2009
with
a
for
a
beta
period
as
disabled
by
default,
with
someone
going
to
come
along
later
and
enable
it
by
default.
Only
one
objection.
I've
previously
heard
is
that
the
matrix
plug-in
looks
bad.
If
there's
too
many
permissions.
A
B
A
A
A
Much
in
principle,
but
yeah.
B
There's
more
exposure
are
it's
already
already
enabled
a
lot
of
instances
anyway?
It's
because
if
they
update
right,
I
think
they
get
it
installed.
B
A
Yeah,
I
agree
so
yeah
for
us
yeah.
We
still
have
some
open
items.
I
believe
that
we
can
just
at
least
this
topic
for
october,
1st,
etc.
So
hopefully
some
of
them
will
be
eventually
updated,
but
yeah.
I
personally
agree
with
you
that
all
critical
stuff
is
there.
I
have
a
systematic
permission
enabled
on
my
instance.
I'm
totally
happy
with
that
yeah.
Maybe
monitoring
would
be
cool,
but
yeah
monitoring
is
a
bit
tricky
because
it
has
management
layers.
It
has
read-only
layers
yeah
and
it
basically
provides
all
ui
from
external
components.
A
A
B
A
So
it's
a
great
step
and
thanks
a
lot
to
joseph
for
doing
that
speaking
of
past
and
encrypted
secrets
still
on
my
plate.
Still
in
my
hall
of
shame.
A
Yeah
well,
I
hope
I
will
get
to
that.
No,
no,
but.
A
Still,
even
if
I
don't
know
how
to
do
that,
the
request
from
joseph
already
provides
a
great
foundation
because
yeah
we
have
some
support
so
and
I
guess
there
was
no
major
changes.
This
releasing
edition,
though,
we've
got
some
documentation
improvements
thanks
to
everyone
who
contributed
to
it
in
1.43.
A
So
here
we
had
validation,
message
fixes
or
some
dependency
updates,
but
yeah.
I
guess
nothing
super
significant
to
talk
about.
B
No,
not
really
just
that
it
was
a
big
core.
Ux
improvement
broke
our
validation
message
on
the
buttons.
A
Oh,
it's
part
of
life,
but
anyway
it
looks
pretty
well
these
days
yeah.
So
I
think
that
the
plug-in
is
pretty
stable
and
we
kind
of
keep
polishing,
but
it
definitely
does
the
job.
So
I
think,
but
it's
in
pretty
good
shape
these
days.
A
A
C
There's
one
pr
here
for
me:
the
third
one:
that's
mostly
it's
not
an
improvement.
It's
I
discover
probably
a
bug
somewhere
between
jks
and
snake
email,
and
so
here
it's
just
to
to
reproduce
and
open
the
discussion.
We
discuss
a
bit
with
tim
about
that,
but
yeah.
Basically,
when
you
have
a
double
as
a
class
in
your
configuration,
if
you
don't
use
a
string
to
configure
them,
they
are
initialized
as
new
and
not
even
with
a
correct
value
and.
A
Looks
like
a
bug
somewhere
yeah.
I
don't
know
many
plugins
using
double.
Do
you
have
examples
of
plugins
open.
C
Source
ones,
no,
sorry
so
yeah
it
was
ready
to
to
open
the
discussion
it's
not
to
because
I
don't
have
radio
solution.
I
just
don't
know
about
that,
and
so
it
was
good
to
to.
C
Somewhere
yeah,
so
string
looks,
works
well
and
and
also
yeah,
and
so
the
the
the
main
issue
is
for
a
ux
point
of
view.
When
you
do
the
export
of
the
configuration
you
will
get
double
as
as
you
expect
as
this
this
form,
but
if
you
configure
with
the
basically,
if
you
configure
your
your
instance
with
what
you
just
exported,
it
won't
work.
You'll
get
you'll,
get
a
new
value,
so.
B
C
I
I
yeah
I
tried
to
to
create.
I
created
the
gear
because
when
I
debugged
it,
it
was
somewhere
in
inside
a
snake
yammer,
but
I
wasn't
able
to
reproduce
anything
inside
snake
camo
through
through
the
tests.
C
So
I
I
thought
that
maybe
it's
because
of
the
it's,
maybe
because
of
the
infrastructure,
the
the
the
class
structure
of
the
configuration
itself
or
something
like
that,
because
you
have
in
snake
email.
You
have
a
method
to.
I
think
it's
the
two-step
constructor
something
I
I
normally.
I
put
the
description
on
on
the
on
the
pull
request,
but
when
I
was
using
directly
snack
camera,
I
wasn't
able
to
go
through
that
that
method
and
but
I
am
able
to
produce
on
on.
A
So
for
floats,
I
believe
that
the
round
trip
works
well,
at
least
from
what
I
remember
there
was
test
coverage,
so
the
first
focus
would
be
to
actually
just
see
whether
there
are
any
differences
between
float
and
double
in
the
code.
B
This
is
bad.
Sorry,
is
that
this,
or
did
we
sit?
Do
we
set
the
floating
format
on
the
in
the
previous
line.
A
A
Okay,
so
for
plugin
installation
manager,
so
you
have
been
working
on
that
recently.
B
Yeah,
so
2.0
includes
a
lot
of
fixes
to
try
and
make
it
behave.
How
you'd
expect
so
there
was
some
minor
bug
fixes
where
things
like
previous
dependency
versions,
so
dependencies
could
pull
in
newer
versions
of
plugins
that
you've
explicitly
declared.
B
So
that's
disallowed
now
plugin
dependencies
will
always
pull
the
latest
version
by
default,
which
is
how
jenkins
core
and
the
install
plugin
script
works,
which
means
that
you
want.
You
won't
get
out
of
date,
plugins
by
default.
B
A
B
Yep,
the
biggest
new
feature
in
this
is
the
ability
to
update
existing
plugins
files.
So
you
can
you
can
ask
when
you,
when
you
look
look
for
available
updates.
You
can
output
it
in
a
machine,
passable
format,
either
yaml
or
txt,
or
you
can
just
view
and
stand
it
out
as
well.
B
Comments
in
the
divs,
no
it
can't
so
snake
sneaky
ammo
doesn't
support
comments
at
all
ext,
possibly
it
could
but
yeah
yeah
comments
is
just
not
easily
retainable.
A
B
A
A
So
when
I
was
working
on
dependency
resolution,
I
actually
did
some
steps
to
improve
to
create
a
kind
of
test
framework,
but
yeah.
I
believe
that
why
mock
us,
this
implementation
is
definitely
much
better
than
like.
It
was
before.
B
Previously,
it
was
guesting
updates
into
urls,
based
on
the
folder
path
structure,
which
is
getting
removed,
so
use
version
parameters
to
resolve,
update
center
correctly
about
taxes.
A
Thanks
for
getting
it
over
the
line,
okay,
yeah,
that's
a
great!
There
is
some
progress
there,
so
yeah.
I
guess
we
will
need
3.0
eventually,
but
yeah.
This
version
is
much
more
stable.
B
A
So
this
is
a
draft
for
draft.
There
is
no
assets
but
below
yes,.
A
Yeah
there
are
shields
and
in
shields
there
are
downloads
for
github
releases.
A
A
So
in
jinx
file
runner,
I
started
integrating
the
plugin
installation
manager,
so
there
is
a
pull
request
for
that.
One
thing
I
stumbled
is
just
a
problem
of
plugin
installation
manager
inside
jinx
file
runner
because
it
basically
had
no
parameterization
at
all.
So
you
cannot
pass
custom
updates
and
et
cetera,
et
cetera.
So
here
you
can
see
that
basically
right
now
always
commented
out
by
default
and,
to
be
honest,
I'm
actually
thinking
about
alternate
approach.
Just
embedding
cli
right
inside
jinx
file,
runner
so
splitting
it
cli
and
adding
command
plugin
manager.
B
B
A
I
really
can
see
the
options
just
adding
cli
and
delegating
everything
there
because
yeah
for
me
imaging
is.
It
already
became
quite
complicated
because
it
has
a
single
level
cla
now
so,
for
example,
there
is
a
command
which
basically
flips
to
the
table
and
switches
it
to
the
cli
mode,
etc.
A
So
having
a
two
level,
common
line
structure
would
be
beneficial
anyway,
but
yeah
anyway,
I'm
going
to
integrate
it
soon.
I
just
switched
to
performance,
but
yeah
it's
in
progress
and
for
docker
images.
Have
you
already
integrated
the
pull
request?
Yeah.
A
A
A
Okay,
jinx
fellow
runner,
you
slightly
discussed
plugin
installation
manager.
Actually
I
experienced
another
issue
which
might
be
interesting
to
this
group.
A
It's
related
to
groovy
hooks,
so
the
thing
is
groovy
hook
so
that
right
now
there
are
only
two
ways
to
pass.
One
is
through
jenkins
home
another
one
through
bundling,
has
a
resource
and
war
file
yeah.
In
the
case
of
j
caskey.
We
have
also
a
way
to
kind
of
configure
the
thing
by
passing
environment
variable
and
this
way
is
not
available
in
a
jenkins
file.
Well
in
and
at
the
same
time
jinx
fell.
A
Runner
cannot
use
either
of
these
squeeze
because
there
is
no
kickstart
jinx
home
at
the
moment,
and
if
you
don't
have
package
the
word
file
using
custom
word
packages,
then
yeah
it
doesn't
work
so
there.
Actually,
I
had
to
opt
out
to
just
configuration
as
code
groovy
because
well
it
works
for
me
but
yeah.
I
wonder
what
is
the
current
status
of
this
plugin
because
yeah
there
is
no
active
development
at
the
same
time
it
just
works,
so
I'm
not
sure
whether
it
needs
any
active.
A
Yeah
but
yeah.
Finally,
so
I'm
trying
to
get
surging
cell
runner
over
the
line
to
have
integration
testing
for
jenkins
pipeline
library.
So
here
basically
what
I
can
be,
obviously
that
yeah
I
will
switch
to
another
packaging
floor,
powerful
and
yeah.
So
the
jkusk
now
looks
like.
A
A
A
So
anyway,
jinx
fell
around
right
on
to
create
a
bit
more
patches
for
better
gc
support,
because
I
started
prototyping
with
moving
jinx
file,
runners
to
crds
and
basically
use
image,
controller
and
other
things
and
yeah.
Then
gcask
becomes
a
bit
more
tricky
there.
B
Yeah,
it
might
be
on
the
jackson,
2
api,
one.
A
A
Yeah,
so
if
there
is
a
use
case
for
basically
json
management
in
a
configuration
is
code,
you
could
just
add
dependency
on
jackson,
epi,
and
so
there
would
be
know
these
issues
going
forward,
because
jackson
api
would
be
coming
from
bom,
always.
A
A
So
I.
C
A
So
you
check
some
data
brand
to
data
format.
No,
we
don't
well.
We
depend
on
the
configuration
as
code
as
plugin
there,
yeah
so
yeah.
Basically,
we
put
it
the
same
dependency
on
jackson,
plugin
in
principle.
It
shouldn't
change
anything
for
users
of
the
framework,
except
the
fact
that
if
they
use
jackson
data
format,
libra
well
jackson
api,
then
they
will
have
to
resolve
conflicts
but
yeah.
I
believe
that
it's
not
a
big
deal.
A
So
what
we
have
system
rules
flex
mark,
so
this
unlikely
to
conflict
with
anything
json
schema.
A
B
B
A
Okay,
so
one
topic
I
wanted
to
discuss
today,
if
you
have
time,
is
about
configuration
as
code
seek
so
just
to
explain
the
context.
I've
finally
got
to
the
working
cloud
native
seek,
and
what
I
would
propose
to
do
is
to
actually
remove
configurations
code
from
here
and
basically
emerged
it
to
the
configuration
as
code
sub
project
and
called
a
special
interest
group,
because
yeah,
like
we
discussed
before
I
do
not
see
so
much
difference
between
subprojects
and
six
at
the
moment.
So
maybe
I
would
rather
merge
it
towards
conflicts.
B
A
C
A
A
Then
I
will
just
stop
with
the
recording
and
thanks
andrea
thanks
team
forgot
to
run
to
meetings
and
yeah.
I
will
publish
the
video
soon.