►
Description
Overview of the recent JCasC releases, ongoing changes, and JCasC Developer tools project sync-up. Meeting nodes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.j8s72rfl3l9x
A
A
Ok,
so
we
had
two
releases
since
the
previous
meeting
one
release
so
yeah.
Last
time
we
talked
about
security
fixes
then,
and
there
was
some
delay,
so
we
had
at
least
128.
This
release
was
mostly
about
maintainability.
You
may
see
that
there
were
many
changes
in
developer
tools.
For
example,
now
we
have
dependable
enabled
we
have
some
tweaks
change,
logs,
etc,
but
really
all
of
the
lives
things
were
about
maintenance.
A
What
really
changed
in
this
release
is
removal
of
the
vault
secret
management.
So
before
this
release
you
were
able
to
use
vault
as
a
secret
source
just
by
installing
the
operations
code
plugin.
Unfortunately,
there
were
some
issues
with
it.
Like
client
library
conflicts,
this
hash
record
from
volt
plug-in,
and
basically
it
was
quite
odd
to
have
a
dependency
on
both
functionality,
then
in
generic
rotations
for
plugin
anyway,
so
we
made
a
decision
to
move
the
functionality
to
the
plug-in
directly.
A
So
now,
if
you
use
the
vault
as
a
secret
source
for
a
j-class,
you
should
be
using
volt
plug-in
and
the
rhythm
so
yeah
there
is
a
Hoshi
corporal
plugin,
Joseph
Patterson
took
ownership
of
this
plug-in.
So
basically,
it's
kind
of
maintained
by
a
Jake
asked
team.
At
the
moment-
and
here
you
can
see
that
there
was
a
new
release
2.50,
so
yeah
were
some
changes
in
addition
to
Jake
asked,
but
basically
you
need
to
install
this
version
to
keep
using
volt
as
a
secret
source
inside
Rick
asked.
A
This
is
a
major
change,
so
keep
it
in
mind
and
after
that
we
also
had
another
release
related
to
my
secret
sources,
its
1.29.
So
we
had
one
issue
report
submitted
in
the
community
that
how
should
the
there
are
issues
with
possible
what
the
resolution?
Actually
it
was
a
long-standing
issue,
but
it
was
hidden
because
before
there's
no
1.24
we
didn't
have
any
kind
of
logging
for
under
resolved
secrets.
A
So
once
we
could
be
slogging,
some
users
stopped
getting
notifications
and
finally,
we
ended
up
this
very
discovered
bug,
which
is
basically
related,
the
initialization
of
secret
sources.
So
yeah
you
can
see
the
tix
is
pretty
simple
but
yeah.
Basically
some
secrets
were
resolved
to
wait.
You
should
have
been
ported
to
all
kinds
of
configuration
management,
so
yeah
it
was
a
fix,
submitted
international
1.29.
It's
also
available
to
users,
and
you
can
see
that
now
other
roles,
dependable
updates,
so
we
use.
A
Automation
nowadays
and
all
dependencies
will
be
kept
up
to
be
so
that's
it
because
and
the
incoming
changes.
Well.
Basically,
there
are
not
that
many
incoming
changes
at
the
moment
in
terms
of
finished
functional,
but
there
is
some
work
and
progress
changes.
One
of
the
changes
is
about
schemin
generation
so
slightly
and
about
it
a
bit
later
and
then
there
is
another
change
which
is
rather
about
quality
of
life.
A
So
there
is
a
lot
of
plugins
using
the
g-class
as
a
test
dependency
or
as
a
contributor,
API
dependency,
and
so
what
is
Joseph
Patterson
doing
at
the
moment
is
adding
jinx
category
schnoz
code
to
plug-in
Bill
of
Materials.
It's
a
new
project
which
has
been
developed
by
jacek
at
the
moment,
so
it's
in
evaluation
phase,
but
it
decays
dependencies
and
versions
for
many
plugins,
and
now
we
also
include
computation,
also
bear
so
it's
game.
Basically,
it's
working
progress
but
yeah.
Hopefully
it
will
be
integrated
zone
and
it
will
simplify
maintenance
for
all
developers.
B
A
A
Yes,
we
already
talked
about:
ok,
ok,
so,
regarding
the
rest,
we
have.
We
have
four
people
on
the
call,
so
I
guess
we
can
just
switch
to
the
full
agenda.
Ok,
because
I
didn't
do
when
we
started.
They
have
beside
only
two
people.
So
what
else
have
in
the
pull
request?
So,
let's
see
doesn't
look
like
so
yeah.
We
still
have
this
to
donnelly
system
configuration
permissions,
but
I
guess
it's
blocked
under
Jenkins
core
changes,
yeah.
A
A
A
A
Okay,
so
yeah
this
one,
you
like
it,
but
you
need
to
finalize
the
base
change
because
yeah
from
what
I
see
there
is
still
a
lot
of
midstream.
I.
Don't
you
right
here:
let's
see
whether
we
kind
of
resource
so
that
somehow
I
would
be
really
happy.
If
you
have
these
fixed
for
the
next
years,
and
maybe
also
in
sensation,
milestone
streets
and
the
junkies
code,
because
then
it
will
change
ability,
especially.
A
B
A
A
A
A
B
A
A
C
C
So
short
introduction
for
myself,
my
name
is
Daniel
Esther,
so
I
was
born
on
Crimea
in
Russia
and
now
I
live
in
Zurich
in
Switzerland,
I
worked
for
GIM
and
for
a
DevOps
team
and
we
use
as
well
Jenkins
and
kidnap
runners.
So
I
am
much
responsible
for
Jenkins.
We
shortly
migrated
for
usage
of
configuration
is
called
plugin
intensively
and
I
also
support
it
by
contributing
for
plug-in
compatibility
and
stuff
and
I'm
very
interested
in
development
of
it.
C
A
Yeah
one
comment
about
a
Swizzle
on
so
yeah
I
plan
to
organize
a
hackathon
in
early
October
with
Jake
asked
as
a
topic.
So
it
might
be
something
interesting
to
you.
Yeah,
we'll,
probably
send
it
up
later
once
maybe
it
is
said,
but
it
will
be
like
the
beginning
of
October,
almost
like
the
inertia
tail,
though
yep
maybe
enjoy
it
escape.
B
C
B
B
Well,
I've
seen
people
read
like
some
of
the
blog
post
for
Jake
asked
and
then
they
come
around
asking.
Well,
the
support
doesn't
work,
blah
blah
blah
and
all
those
things
right.
So
they
installed
all
plugins
for
some
reason
and
nothing
works
and
they
like
confused.
So
so.
I
want
to
I,
want
to
fix
the
duplication
issue
and
have
like
the
same
as
slight
warnings
right.
B
But
maybe
this
could
just
be
stand
out
as
a
plug-in
like
it.
It's
it's
I
hate
having
stuff
in
the
Jenkins
core,
but
it
could
be
a
recommend
dated
already
recommended,
install
or
something
or
something
that
just
decides.
I'll
put
this
in
to
be
a
module.
I,
don't
know
it's
for
all
the
releases
as
well
be
nice
to
just
have
it
in
working.
A
A
Basically-
and
we
see
that
not
that
many
people
go
there,
yes,
the
keys
for
many
plugins,
so
that
is
ongoing
activity
for
having
plug-in
app
updates
at
supporting
github
as
a
source,
and
so
it's
this
activity
is
a
part
of
the
communication
sub
project,
but
it's
still
something
which
is
really
related
to
disco.
Jake
asked
so
it's
been
incarnation
is
one
of
the
contributors.
A
A
Yeah,
basically,
after
some
patches
and
follow-ups,
it
looks
like
that.
So
this
is
pulling
off
the
folder
based
authorization
plug-in
created
by
a
builder.
But
basically
this
information
is
picked
from
github,
with
old
badges
with
images
and
yeah.
We
don't
have
the
same
project
asked,
hopefully
soon
so
now
we
are
just
waiting
for
infrastructure
team
because
we
need
to
github
API
tokens
to
make
it
readable,
because
we
need
to
pull
the
data
from
github
and
you
know
most
motive.
It's
not
going
to
end
well
so.
A
A
A
A
A
A
Yeah
well,
if
you
learn
to
these
features,
it
would
be
brilliant.
I
would
say.
Okay,
so
other
topic
I
wanted
to
discuss
is
about
moving
to
platinum,
special
interest
group,
so
just
to
provide
some
context
in
jenkins
project.
We
have
a
number
of
special
interest
groups
in
which
you
can
see
some
groups,
like
advocacy,
outreach
well
made
here
with
the
commentation
google
Summer
of
Code
platform
etc,
and
the
problem
that
no,
not
all
of
this
special
interest
groups,
are
related.
A
A
One
problem
with
a
special
interest
group
that
well
basically
it's
not
active
and
another
problem
that
Jake
asked,
is
not
only
about
cognitive-
is
basically
used
everywhere
as
a
part
of
the
platform.
So
my
thought
was
that
what
if
we
actually
move
it
to
the
platform
special
interest
group,
so
this
group
is
currently
focused
on
packaging
on
support
of
the
very
existence
yeah.
A
There
is
high
interest
in
generational
code
today
as
well
example,
monthly
music,
and
give
you
that,
but
he
is
heavily
using
jakers
projects
and
basically
all
of
the
people
here
somehow
showed
up
in
Jake
ask
channels
as
well.
So
while
we're
thinking
about
moving
it
here
but
yep,
so
it's
something
for
the
discussion
so
for
employed
from
seek.
We
have
regular
meetings
every
two
weeks
on
Thursdays,
but
guess
it
would
not
change
anything
for
the
project
specifically
except
maybe
periodic
updates
have
a
policy.
A
B
A
A
He
didn't
happen
around
many
reasons.
Why
and
I
cannot
share
all
the
reasons
on
this
call,
but
yeah
basically
of
what
was
happen
to
be
delivered
management.
There
is
some
info
interest
in
a
configuration
sources,
so
it's
not
a
configuration
sources.
We
will
discuss
in.
Please
use
login
throughout
the
generic
configuration
source
of
eager
obvious
a
little
of
this
stories,
so
there.
A
D
D
A
A
D
C
A
Are
obvious
in
putting
integration
in
the
doctor?
So
what
Natasha
stop
was
working?
He
thought
project
yeah.
There
are
opportunities
for
it
in
cognitive,
suite
yeah,
for
example.
If
we
talk
about
official
changes,
health
charts,
then
he
it's
cloud
native
Sheik
and
again
there
are
opportunities
for
collaboration
there,
yep
for
me,
so
Jake
asked
is
basically
part
of
every
see,
always
so
to
see
why
best
reads:
cool,
mainly
it
creating
new
contributors.
Courtship
could
be
also
an
option,
but
yeah
I
think
it's
overkill.
D
D
So
actually,
the
problem
that
we
are
facing
currently
is
and
I
wanted
to
ask
ask
Joseph
that,
since
we
are
generating
the
schema
and
we
call
describe
structure
and
iterate
over
the
nodes,
we
would
need
to
decide
whether
we
add
the
required
label
to
each
one
of
them.
Because
if
we
add
the
required
label
to
the
sub
attributes,
then
it
will.
D
D
Compulsorily
include
them
into
the
yml
and
if
they
aren't
then,
because
otherwise,
if
we
don't
include
them,
then
there
would
be
no
checklist
and
so
suppose,
if
we
suppose,
if
it
is
tool-
and
we
have
kid
and
we
have
installations
and
if
we
don't
require
installations
in
gate
and
we
just
make
a
typo,
then
that
doesn't
get
picked
up
by
the
schema.
But
if
we
actually
include
them,
then
the
user
has
to
compulsorily
add
them.
So
that
was
one
point
that
maybe
Joseph
could
could
elaborate
on.
So.
B
C
B
D
So
so
yeah,
my
question
was
yes,
so
since
we
would
have
to
decide
on
what
tools
at
what
kind
of
sub
attributes
are
required
and
what
sub
attributes
aren't
required,
another
thing
that
actually
we
so
that's
again,
that's
not
actually
a
substitute
aside.
It's
depending
on
how
the
trait
it's
a
plug
in
I,
guess:
yeah
agreed
yeah.
We
could
come
to
that
later
once
we
actually
go
over
the
node,
so
yeah.
One
question
since
we
are
on
the
call,
of
course,
is
the
described
structure.
D
B
You
actually
have
already
done
is
I,
think
you're
filtering
out,
none
Knowles
right
and
that's
incorrect.
You
shouldn't,
because
you
need
the
whole
data
structure,
so
you
cannot
filter
out
objects
that
might
be
now
because
they
might
say
they
might
be.
Actually
they
might
be
just
a
class
that
says,
like
you
can
in
the
CM,
but
there
are
some
I
know,
there's
some
again
still
act
like
they
have
their
the
class
as
like
a
behavior.
That
makes
something
happen,
so
you
should
filter
those
out.
Then
the
data
structure
doesn't
have.
D
B
B
D
B
D
B
So
I
think
inside
the
schema
generator
you
will
do
is
shoot
it
before,
but
instead
you
will
just
reduce
it
to
only
call
like
for
all
the
routes.
Configurators,
you
will
just
call
described
structure
and
then
this
right
structure
will
ensure
that
you
get
there.
You
will
get
down
into
hetero
configurator,
because
that
is
also
that
will
also
have
a
describe
structure
function,
so
it
will
just
go
through
all
of
them.
B
D
D
A
D
Cool
because
at
least
if
we
can
get
kind
of
the
describe
structure
working
for
every
configurator,
we
might
just
have
to
tweak
it
a
bit
here
and
there
and
we
might
have
the
schema
ready
so
yeah.
The
testing
framework
would
be
an
issue
yeah
that
would
maybe
maybe,
by
the
end
of
the
phase,
one
exactly
but
I,
think
yeah,
maybe
I
could
present
something
for
the
demo.
Do
include
me
in
the
list.
B
A
Then
yeah
just
keep
workin
sliding
yeah
yeah
yeah.
That's
under
face
one
yeah
Joseph
and
came
to
understand
how
we
do
the
evaluation
and
because
yes,
so
I
guess
it
would
be
a
kind
of
JSOC
way.
Yeah
yeah
yep,
another
problem,
absolutely
yep
right
now
just
focus
on
the
line
and
if
you
have
opportunity
to
ship
smaller
scale,
changes
like
this
documentation,
update
or
whatever
adjustability
yeah.