►
Description
Recording of the regular Jenkins Configuration-as-Code sub-project meeting. Breaking changes in the Jenkins core 2.231 and required JCasC upgrade, new features and compatibility enhancements, ongoing development and future plans. Full agenda and meeting notes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.ok6j1hen9npt
A
Welcome
to
the
regular
Jenkins
configuration
has
called
Project
meeting
and
day
is
April
22nd
and
we
are
going
to
discuss
the
project
status
and
going
development,
and
recent
news
in
the
Jenkins
configuration
is
called
area
so
basically
we'll
be
running
the
center
transgender
and
we
have
a
number
of
participants
on
the
call.
So
thanks
to
everyone
for
joining
okay.
So
what
do
we
have
in
our
agenda
for
today?
So
we've
got
some
news,
especially
about
the
breaking
changes
in
the
Jenkins
core,
so
team.
Would
you
like
to
summarize
them
yep.
B
B
We
shipped
a
quick
fix
on
the
day
we
found
us
and
we've
got
clean
effects
coming
soon.
We,
basically
we
added
the
annotations
in
configurations
code
temporarily
and
we've
got
a
follow
up,
pull
request
to
remove
them,
but
didn't
want
to
have
to
do
the
testing
at
the
same
time
just
want
to
and
get
the
emergency
fix
out.
B
Apart
from
that,
we
have
so
Dickens
2
to
6
change
the
layouts
on
the
confirm
the
manage
page
to
have
categories.
If
you
didn't
specify
when
you
went
right
to
the
bottom
and
categorized
so
now,
we've
seen
it
so
that
we're
in
a
category
and
we're
further
at
the
top.
Now,
apart
from
that
sure,
there
might've
been
a
couple
of
other
minor
changes
in
the
release,
notes.
B
A
I
really
feature
which
is
a
became
available
and
github
couple
of
months
ago.
So
now
you
see
get
a
chat
here
and
if
you
want
to
add
something
else,
it's
ultimately
possible
so
here
plug
in
maintaining
it,
you
can
add
even
more
links,
for
example,
linking
to
your
special
interest
group
channels,
like
my
name,
please
and
whatever
so
its
quality
of
life
improvement
for
maintained
years,
and
you
just
request
anything
another
llamo
file.
A
Ok,
thank
you.
For
this
overview.
Another
Jake
asked
related
news
that
yesterday
we
had
online
meetup.
They
we
had
a
presenter
from
Africa
about
how
to
use
configuration
as
code
together
with
kubernetes.
It
includes
the
Jake
asked
plug-in
also
integrations
with
job
day
sale,
also
helm
as
infrastructures
code
layer.
A
So
if
you're
interested
for
some
example
how
to
run
Jake
asked
in
practice,
you
can
take
a
look
at
this
online
Meetup
and
the
recording
is
already
published,
and
speaking
of
that,
I
have
a
topic
for
later
about
other
meetups
and
blog
posts,
but
yep
we
can
discuss
elated.
You
can
do
basic
eating,
okay,
any
other
in
use.
We
are
missing.
B
Yes,
oh
those
administrative
monitors,
his
support
and
it's
very
nice
because
I
used
it
the
next
day
and
there's
been
a
couple
of
ones
related
to
time,
zone
and
ssh
authorized
keys
for
the
local
security
realm.
B
B
A
C
A
D
E
E
F
So
anything
else
about
the
news:
yes,
jerk,
evil
secret
sauce,
resolver.
A
A
A
F
A
It's
actually
am
just
looking
for
other
items,
so
basically
on
truck
to
have
something
pretty
useful
in
the
next
release:
right
next
LCS
yeah
next
LCS
yeah.
So
we
will
have
LCS
baseline
selection
in
two
weeks
and
yeah
by
these
two
weeks.
You
like
to
get
all
these
patches
in
place,
because
community
ratings
look
pretty
good.
Yet.
B
B
B
B
A
A
A
My
said
for
system
with
permission,
I
finally
updated
my
demo
to
support
it
well,
I
just
bumped
to
the
weekly,
not
even
to
the
previous
ones.
Yes,
it
works
pretty.
Well,
though,
I
also
started
reporting
a
plugin
manager
to
use
plug-in
installation
manager
tool
because
I
want
to
use
dependable
and
I,
don't
want
to
use
custom
or
packages
in
this
demo,
so
it
takes
a
bit
longer
than
I
expected
if.
A
E
A
B
B
A
So,
just
to
explain
some
context
about
it,
so
there
was
a
for
Bill
of
Materials,
which
we
actually
implemented.
So
now
you
can
use
maybe
an
HPA
plugin
to
generate
a
bill
of
materials.
It's
basically
a
mall,
it's
Yama
lien
in
different
format,
which
is
not
supported
by
plug-in
installation
manager
tool
at
the
moment,
but
still
it's
a
foundation
and
I
just
tweaked
the
code
to
generate
plugins
16
in
the
future.
We
just
need
to
generate
final
plug-in
installation
manager,
camel
I,
believe
you.
A
B
A
B
Dozen
to
PCT
dozen,
so
basically
in
script,
security
palm
they
have
configuration
is
carried
in
configuration
skirt,
a
stylist
and
PCT
is
only
updating.
The
comparison
is
codependency
and
not
the
test.
Anna
Swan
and
the
T
stylist
is
trying
to
load
all
the
old
sneaking
occurred
and
it's
conflicting
so.
A
The
one
we
didn't
fit,
we
need
to
bleed
PC
to
eat
or
drink,
assess
harnesses
all
right,
yeah
yeah.
The
problem
is
that
there
isn't
a
bit
of
Jenkins
test.
Harness
also
includes
upgrade
of
htmlunit.
So
it's
not
going
to
be
easy
because
you
have
did
Jenkins
test
harness
and
after
that
everything
starts
breaking
because
of
binary
incompatible
changes
at
least
a
day.
It's
my
suspicion.
I
really.
B
A
A
B
A
Yes,
speaking
of
that,
what
we
could
do
since
Jake
asked
is
widely
used.
You
could
just
integrate
it
into
plug-in
pawn
because,
for
example,
what
we
can
do
plug-in
pomo
includes
dependency
management
section.
So
here
we
could
add.
Basically
Jake
asked
test
harness.
You
could
all
set
a
property
which
defines
its
version
similar
to
how
we
do
with
other
tools,
and
then
we
can
assume
that
all
begins,
which
use
Jack
Astor's
harness,
would
be
ranked
on
the
same
property
name
and
every
write
about
it
in
PCT.
B
The
guidance
is
really
is
used,
Bob,
where
you
can
and
then
don't
add
one
true
problem
as
we
had
it.
We
had
issues
getting
the
latest
bomb
release
out
because
we
to
update
everyone
so
their
their
ISM.
So
possibly
we
can
yeah.
It's
just
just
difficulty
having
a
breaking
change
like
this.
The
sneaky
ml
fast
path
changes,
because
normally
that
wouldn't
be
a
breaking
change,
so
it
would
work
even
though
they're
out
of
sync,
we
would
have
had
the
same
issue
with
the
TCR
I
assume
as
well.
B
A
G
G
A
B
A
A
F
A
Okay,
so
secret
encryption
is
external
secret
key.
A
quick
update,
no
updates,
but
I
still
intend
to
do
that
and
pretty
much
the
same
for
configurator
EPA
I
tried
implementing
that
two
weeks
ago.
I
hid
some
issues
with
binary
compatibility.
I
can't
fix,
without
reflection,
so
I'm
back
to
the
drawing
board
for
a
while.
A
B
Don't
know
like
most
people
seem
happy
enough
bumping.
Their
codependency
is
required.
They
seems
to
be
less
hold
back
and
increasing
conversions.
Recently
from
what
I've
seen
among
other
plugin
developers,
it
used
to
be
just
target
the
very
lowest
version,
but
people
seem
happier
we
can
always
release
lower
versions,
as
required
as
well.
I
was
wondering
if
one
I
mean
just
going
back
to
the
last
one.
Only
jake
has
test
harness
for
the
bomb.
We
could
release
a
version
of
the
snake
here,
more.
C
A
G
A
A
G
A
A
We
had
a
long
discussion
about
configuration,
call
Ascott
api
because
current
situation,
if
you
want
to
offer
a
new
api
for
other
plugins,
then
these
other
plugins
will
have
to
depend
on
the
same
version
of
the
core
Ezra
cask
or
higher.
So
it
means
that
now
we
should
Jake
ask
for
the
recent
version.
A
If
we
want
to
add
new
API,
for
example,
for
configurators,
then
you
will
have
to
update
other
plugins
to
be
compatible
with
this
new
version,
and
we
don't
have
so
many
use
cases
for
configurator
api,
but
at
the
same
time
it's
it
might
cause
problems
at
some
point.
If
we
need
to
drastically
extended.
For
example,
we
did
some
configurator
API
changes
for
the
communication
generation
when
we
working
on
the
community-based
project
with
shaylen,
and
there
might
be
some
similar
changes
away.
G
G
A
B
G
B
B
A
When
I
did
it
in
2017,
it
was
easy,
but
yeah.
Now
it's
more
complicated
to
use
all
these
inter
dependencies
yeah.
Okay,
we
already
only
bed
somehow,
okay,
they
put
some
items
like
road
map
updates,
some
accounts,
etc.
Before
we
press
it
to
date,
do
we
have
any
technical
topics
so
that
we
can
spend
time
on
them.
B
F
D
D
G
A
So
yeah
a
quick
update
on
the
Jenkins
roadmap.
So
yet
tonight
we
have
a
first
drink,
is
roadmap
meeting
and
we'll
be
working
with
special
interest
groups
and
projects
to
have
it
in
place.
So
it's
quite
long
and
will
likely
need
to
refactor
it
a
bit
and
butter.
Some
items
related
to
Jake
asked.
For
example,
we
have
G
cos
like
incompatibility,
also
system
edit
permissions,
a
built
in
plug-in
management.
A
It's
mostly
plug-in
installation
manager,
plus
integration,
Center
distributions
than
pluggable
configuration
sources
which
we
discussed
before
the
roadmap
and
basically
they'd
see
about
Jake
asked
right
now.
Obviously
other
stories
may
include
some
beats,
but
yet
the
number
of
stories
he
is
quite
limited
and
if
anyone
wants
to
put
something
else
on
the
list,
please
do
so
because
yeah
this
list
is
community
driven.
A
A
Okay,
so
yeah
the
next
one
plug-in
compatibility,
highlights
I,
believe
we
discussed
it
in
the
beginning
and
the
new
section
changing
some
account
for
meetings.
So
one
good
news
that
we
finally
have
a
specialist
account
for
Jenkins
what
it
means
that
yeah.
A
B
A
B
A
A
A
Just
think
okay
I
will
I
think
about
here.
Okay,
so
it's
coming
into
driven.
We
definitely
do
assign
tasks
to
create
something
yeah,
but
if
somebody
is
interested
yes
and
specifically
about
Jenkins
and
kubernetes,
so
we
run
a
series
of
online
meetups
and
if
somebody
wants
to
present
how
to
use
Jake
asked
together
with
kubernetes
it's
more
than
welcome.