►
From YouTube: JCasC office hours, Nov 21, 2019
Description
Recording of the regular JCasC sub-project meeting. New releases, ongoing developent, and project updates. Meeting notes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.7t9zg2q88b6g
A
B
B
C
B
B
Since
then
1.33
it
was
released,
so
we
have
a
secret
sauce
implantation
for
properties
files.
That's
so
you
can
just
have
one
file
with
all
your
secrets
and
rather
than
having
to
have
the
file
name
is
the
key
and
the
contents
of
the
file
is
the
value,
so
it
can
be
quite
useful
for
people
who
are
still
running
on
vm's
or
we're
on
running
in
docker
or
kubernetes
quite
useful.
A
couple
of
the
two,
the
Jake
asked,
dev
tools,
project
enhancement
for
JSON,
schema
documentation,
a
misspelling
in
the
API
which
had
no
consumers.
B
And
a
few
demos
and
documentation
updates
and
quite
a
few
dependency
updates,
but
there
are
other
integration
tests,
so
it
shouldn't
affect
anyone
and
some
more
cleanup.
So
the
main
feature
is
the
secret
sauce
implementation
and
pending.
We
don't
we're
only
about
dependency
updates
pending
currently.
B
B
I've
had
a
request
for
clarifications
code
class
to
be
unrestricted,
so
the
cloudBees
beekeeper
can
decorate
the
output
in
some
way.
Yeah
wait,
yeah,
just
another
invite
development,
I,
think
there's
the
schema
generation
to
finish
off
to
Jay
kiss
dev
tools.
Work
inside
of
Jake
asked
there's
currently
a
couple
of
issues
with
thoughts
like
one.
What
tests
are
failing
ends
and
there's
a
duplicate,
Jenkins
configurator
because
of
the
Jenkins
object
and
the
Jenkins
configurator
is
causing
some
issue
better
year.
That
poor
request
is
critical
for
the
schema
generation
to
work
properly.
B
C
C
So
we
have
much
conflict
there,
consensus
about
future
flock
and
I
assume,
so
we
could
probably
all
end
it
in
one
of
the
next
week
days:
okay
yeah
a
little
bit,
we
should
have
new
baseline
selection
to
be
so.
It
means
that
it
mrs.
Jenkins
LCS,
but,
on
the
other
hand,
I
do
not
see
what
would
be
the
schedule,
because
usually
we
used
to
skip
one
months
due
to
Christmas
break
another
think
so
maybe
he
applies
this
year
as
well.
I
already
so
I'll
try
to
understand
the
status.
Sure.
B
C
C
B
B
C
C
The
number
father
Benedict
as
compatibility,
fixes
what
he
will
need
to
clarify
this
date.
Anyway,
all
majors
were
plugins
already
compatible.
So
here
we
apply
it
fixes
he
in
there,
but
yeah
I
just
need
one
instance
to
Jake
asked
last
week
and
basically
I
didn't
experience
any
contributing
issues
while
moving
really
really
instance,
which
is
quite
unexpected,
but
it
was
nice.
C
B
C
A
A
C
C
B
C
C
C
Statistics,
so
we
can
break
it
not
very
quickly,
but
they
require
a
new
core
version.
Each
might
cause
some
issues.
For
example,
if
you
ever
want
to
deliver
another
security
fix
of
a
plug-in
materials,
because
it
means
that
whomever
wants
to
pick
up
new
g-class
question
number
we
feel
from
new
IPs,
then
they
would
have
to
bump
the
core
dependencies.
Well
yeah.
It
was
one
of
the
main
reasons
for
me
to
propose
configurator
API
plug-in
almost
three
years
ago:
I
guess
but
yeah.
C
B
C
C
There,
maybe,
since
we
have
some
time
it
makes
sense
to
quickly
discuss
it.
Basically,
we
have
two
options:
one
to
keep
the
meetings
in
the
current
time
zone
modest,
so
it
means
that
your
people
from
Europe
and
Asia
can
easily,
but
at
the
same
time
it's
not
that
comfortable
for
United
States,
especially
for
East
Coast
West
Coast.
Here
it's
quite
late,
but
they
probably
can't
Martin
meeting,
but
your
first
coast
is
the
current
spot
is
not
good.