►
From YouTube: JCasC project meeting - YAML config validation and Visual Studio Code plugin for JCasC
Description
Sladyn Nunes presents his Community Bridge project: JCasC Schema validation and a new JCasC plugin for Visual Studio Code.
Project URL: https://jenkins.io/projects/jcasc/dev-tools/
Meeting URL: https://zoom.us/j/286266977
A
Okay,
now
we
are
recording
hi.
Everyone
today
is
November
13th
we
have
a
non
regular
Jenkins
configuration
is
called
Project
meeting.
Usually
we
need
every
two
weeks,
but
this
time
we
decided
to
have
out
of
all
the
meeting
in
order
to
make
presentation
of
Jenkins
computational
code
project
by
sliding
studying
is
community.
A
Richmond,
T
I
started
working
on
jihad,
developer
tools
enormous,
and
yet
he
will
present
his
work
so
yeah
the
agenda
for
the
today's
goal
is
to
just
have
this
presentation
to
discuss
the
results
and
if
you
have
some
time
left
after
that,
we
can
discuss
common
project
matters,
absolutely
people
on
the
call,
so
it's
slotting
team
we
also
have
Antonio
and
John
and
yeah
I,
think
we
can
just
start.
If
anyone
wants
to
do
meeting
notes,
you
have
a
common
Google
Doc
for
it.
A
B
B
Yep,
it's
all
gone
talking
about
the
time.
I
share
my
screen,
yep,
so
I'm,
the
community
bridge
intern
from
from
Jenkins
I,
started
working
I
think
around
in
August,
I.
Think
three
three
three
months
before
so
my
project
was
dealing
with
the
Jake
asked,
validation,
the
schema
validation
and
developing
a
plugin,
making
it
much
easier
for
the
developers
of
the
of
Jake,
as
in
general,
to
just
be
able
to
configure
their
yamen
files.
So
that's
many
worthy
I
mean
you
want
to
set
up
Jenkins.
B
You
want
to
set
up
a
Jenkins
project
using
the
Jake
asked.
While
there
wasn't
any
provision
for
editing
or
being
able
to
make
changes
to
the
I
mean
being
able
to
have
any
feedback.
While
writing.
So
you
could
have
a
desk
repin
or
you
put,
you
can
probably
make
mistakes,
and
then
you
could
just
apply
the
configuration
and
realize
that
it's
not
it's
not
getting
applied.
So
so
what
we
decided
was
to
be
able
to
I
mean
rectify
that.
B
So
I
had
my
mentor,
who
was
very,
very
helpful
and
supportive
throughout
the
project,
so
shout
out
it
okay.
So
what?
What
was
the
project
about
developers
to
validate
the
yamen
files
that
they
write
for
Jenkins
instance?
Why
hey
Cass?
So
we
thought
to
make
life
easier
for
the
users
by
developing
OBS
code,
plugin
I
mean
the
base
code.
Plug-In
is
just
fighting.
It
comes
as
a
hand
in
hand,
along
with
the
along
with
the
validation,
which
is
the
major
part
so
that
it
just
pulls
in
the
schema
file
for
the
Jenkins
instance.
B
You
are
running
so
I
just
I
mean
I'll,
just
explain
to
you
how
we
plan
to
the
project
initially.
So
initially,
what
we
decided
was
the
initial
schema
was
written
in
jelly
and
which
made
it
very
very
difficult
to
test.
So
what
we
decided
was
to
be
able
we
needed
a
better
testing
framework
for
the
schema,
so
I
mean
we
could
test
it
much
easier
because
it
was
a
pain
when
it
was
written
in
jelly.
B
Okay.
So
what
we
decided
that
we
would
split
it
up
in
two
phases:
phase
one
who
deal
with
this
in
a
three
design
and
phase
two
would
deal
with
the
plug-in
with
the
plug-in
development.
So
initially
we
we
said
on
supporting
a
set
of
different
plugins,
like
IntelliJ
I
mean
set
of
ID's
and
so
on,
such
as
Indonesia
vs
code
and
so
on.
But
we
decided
I
mean
your
time
constrains
and
it
being
it
took
a
lot
lot
of
time
to
actually
redesign
the
schema.
B
B
I'll
start
with
the
schema
redesign,
so
the
things
that
we
did
in
this
I
don't
want
to
go
too
much
into
technical
media
since
being
a
demo,
and
it
it'll
make
much
sense
the
users
that,
if
I
just
go
on
to
the
meet
so
one
of
the
things
that
we
did
was
we
rewrote
the
entire
schema
in
Java,
which
would
make
it
much
easier
to
test
and
I
mean
in
case
there
were
any
modifications
or
any
for
the
API
schema
that
we
want
to
develop.
On
top
of
this,
it
would
make
it
much
easier.
B
B
Okay,
so
one
of
the
things
that
we
I'll
come
to
the
disadvantages
data,
so
I
could
just
just
hold
on
a
second,
so
I
think
if
I
just
go
through
the
presentation
before
I
begin
with
phase,
it
would
make
it
much
easier
to
understand
so
so
once
we
redesigned,
the
schema
I
mean
made
it
much
much
better
to
use
we
decided
to
go
in
with
the
V
escort
plug-in
now.
What
the
plug-in
does
is.
B
Essentially,
what
have
to
do
manually
is
to
initially
insert
the
schema
and
then
write
your
Jenkins
Yammer
file
and
then
just
use
the
schema
for
validation
using
the
Red
Hat
plug-in,
which
was
developed
I
mean
the
Yammer
plug-in
developed
by
Red.
Hat
I'll
come
to
the
details.
Later,
don't
worry
so,
basically
what
we
decided
was
we
wanted
to
make
life
much
easier
for
even
much
easier
for
developer
so
that
they
don't
have
to
go
in
and
pull
your
work.
Jenkins
I
mean
if
you
go
and
look.
B
So
what
you
just
had
to
do
initially,
so
this
is
the
newly
generated
schema.
What
you
decide
to
do
initially
was
we
had
to
just
copy
this
entire
schema
onto
of
JSON
schema
JSON
file
and
then
use
a
red
hat
plug-in
to
validate,
so
we
decided
that
is
in
very
efficient
for
the
users,
because
then
they'll
have
to
just
keep
downloading
the
scheme
again
and
again
and
again.
B
B
It
takes
in
the
latest
changes
from
the
Jenkins
from
the
Jenkins
instance
and
then
downloads
the
scheme,
my
so
what
you
basically
has
user
have
to
do
is
just
just
right
in
your
Yama
file
or
make
some
settings
changes
and
then
you're
good
to
go,
which
I
will
show
you
okay,
so
so
what
does
the
vs
could
plug
into
exactly
so?
The
VA
sport
plugin
basically
just
downloads
your
instance,
by
using
your
username
and
token,
which
ensures
that
we
maintain
complete
security
and
there
is
no
half-hearted
attempt
in
ensuring
that
there
is
the
users.
B
Don't
I
mean
the
admin
of
Jenkins.
The
run
who's
running
the
instance
is
fully
secure.
So
what
we
decided
that
you,
the
vs,
plug-in
and
sure
that
you
don't
have
to
go
into
the
latest
ponta
creation.
So
that's
another
plus
point
because
you
don't
have
to
manually
go
in
and
navigate
using
a
bunch
of
UI
buttons
to
the
drink,
to
the
schema
file,
download
the
schema
file
copy
pasted
in
the
phylum,
in
the
order
that
you
don't
have
to
do
that.
You
just
give
us
the
URL
of
your
drink.
B
B
So
you
can
just
have
a
look
at
the
if
you
want
the
marketplace
URL
that
we
shared
with
with
you
another
point
that
I
wanted
to
touch
on
is,
if
you
want
to
read
more
about
I've,
not
gone
into
much
detail
about
how
we
implemented
the
phase,
one
yam
in
the
configuration,
but
if
you
the
scheme,
I'm
sorry,
but
if
you
want
a
rough
overview,
I
could
give
it
that
we
in
the
schema
redesigning.
Basically,
we
just
we
just
took
the
old
schema
that
was
being
that
had
been
written
in
jelly
and
not.
B
There
was
not
a
hard
coal
there's,
not
a
hot
food
conversion
that
we
did,
but
basically
we
made
made
sure
that
for
every
for
every
key
value
pair
that
we
generate,
there
is
a
corresponding
descriptor
and
no
descriptors
will
missed
out,
and
basically
it's
just
our
just
a
read.
It's
just
a
redesign
with
a
few
with
a
few
modifications.
Actually,
if
you
want
to
read
more
about
it,
I
have
a
blog
post.
So
for
this
I
shared
with
you,
you
can
just
read
the
blog
post,
and
that
is
that
is
quite
quite
informative
and
descriptive.
B
So
you
can
just
go
on
and
have
a
look.
Okay,
I
think
that's
about
it!
If
you
want
that's
what
for
my
presentation,
of
course,
they're
moving
company,
you
can
go
and
read
much
about
the
plug-in.
You
order
the
meeting
URL
you
can
just
hop
onto
our
guitar
and
kind
of
comment
over
there.
Any
feedback
would
be
very,
very
highly
appreciated,
so,
okay,
so
hoping
on
to
the
demo.
B
B
Sorry
jenkins
instance
running
say:
if
you
see
your
ID
computation
as
code,
you
have
the
json
schema
URL,
so
you
can.
If
you
want
to
manually
anytime,
check
out
the
schema
forward,
I
mean
what
are
the
content?
You
can
easily
go
ahead
and
check
it
out
so
step.
One
so
step
one
is
to
navigate
to
your
favorite
ID.
Currently
we
support
an
EVs
code,
so
I
mean
that
person
we
have
plans
for
IDs
for
that
one
yeah.
So,
okay,
so
step
one
would
be
the
fetcher
fetch.
Oh.
B
Yeah,
so
apologies
for
the
user
Docs
because
there
haven't
been
much
written,
but
you
will
get
a
detailed
user
dog
I
mean
how
do
you
use
the
schema?
How
to
use
the
plug-in
essentially
written
here
so
that
so,
once
you
install
the
plug-in
you
just
in
this
plugin
I
think
I
think
Joseph
just
added
a
fix
so
that
you
don't
have
to
download
the
plug-in
but
yeah.
Once
you
download
this
plugin,
you
need
to
make
sure
that
you
have
the
Red
Hat
plug-in
installed
as
well.
B
So
that
is
this
one
right
here
so
because
our
plugin
essentially
depends
on
the
photo
completion
and
the
intelligence
on
the
Red
Hat
yamen
support
because
they
have
the
language
level
implementation.
It's
no
point
in
reinventing
the
wheel,
so
we
start
with
the
yeah
mill
Red
Hat
plug-in
that
was
developed.
So
once
you
have
both
of
these
plugins
all
set
and
ready.
What
we
need
is
okay,
so,
first
of
all
your
Jenkins
instance
login
to
your
drinkin
and
obviously-
and
so
once
you
are
logged
in
you
will
be
able
to
generate
a
user
token.
B
We
need
this
user
token
to
be
able
to
maintain
complete
security.
So
if
you
see
here,
I
mean
you
can
generate
your
token
here
and
you
link
it,
you
can
even
give
it
a
user
name
and
you
get
the
token
generated.
So
what
are
you
basically
do
after
that
is
to
go
to
file
preferences,
settings
and
just
search
for
Jake?
Ask
because
okay,
so
you
enter
the
schema
URL.
That
is
the
URL
from
your
from
your
browser
and
you
enter
the
user
token.
B
So
our
generator
user
token,
as
you
can
see
or
their
user
name
is
Satan
I
did
and
even
got
your
user
token.
So
after
that,
what
you
do
is
you
you?
Basically
don't
you
activate
your
plugin
by
using
the
Rose
Heaphy
and
if
you
have
a
look,
you
can
see
it
right
at
the
top,
but
if
you
don't
find
it,
you
can
just
type
in
jenkins
and
it
will
auto
complete
it
for
you
and
you
hit
the
first.
You
obviously
click
it.
B
What
you
take
it,
what
the
plug-in
does
is
in
downloads
for
Jake
a
schema
dot
JSON
for
you
in
your
current
working
directory.
So
if
you
wanted
to
order
it
elsewhere,
I
mean
you
could
just
open
the
open.
The
editor
video
directly
on
this
download
the
schema
there,
the
different
schema.
So,
as
you
can
see,
this
is
the
schema
that
we've
downward
and
it
is
named
as
J
caste
schema
door
JSON
you
can
rename
it.
B
If
you
want
so
I
did
I
would
suggest
to
keep
it
as
it
is
now
I'm,
making
it
much
easier
for
it.
For
you
to
know
what
the
scheme
of
what
instrument
after
that
I
would,
after
that,
you
just
have
to
configure
a
couple
of
settings
now
why
you
need
to
configure
these
settings
is
because
we
need
to
tell
the
Red
Hat
Yai
a
plugin
that
hey
this
is
my
schema
file
and
I
want
all
files
with.
B
B
You
can
go
ahead
and
check
them
out,
so
what
you
would
essentially
do
is
to
ensure
that
this
name
and
the
name
phrase
schema
is
the
same,
because
this
is
essentially
your
key,
so
you
rename
it
to
whatever
you've
renamed
the
a
JSON
schema
to
recommend
key
to
the
same
or
you
could
keep
something
shorter
if
you're
not
fond
of
typing
like
me,
so
so
that
once
you
do
that,
you
can
essentially
go
ahead
and
create
your
I
mean
this.
Is
my
user
space
you
don't
need
to?
B
You
can
just
go
ahead
and
create
a
new
Jenkins
dot
yml
file,
and
once
you
create
a
Yaman
file,
I
think
that's,
basically
it
because
you
have
now.
You
have
your
editor
against
all
you
have
the
vehicle
plugin
installed.
You
have
your
schema,
and
all
that
is
left
is
I
mean
to
go
ahead
and
complete
I
mean
go
ahead
and
write
down
your
file
so
for
this
demo.
So,
as
you
can
see,
if
you
go
ahead
and
go
to
configure
or
basic
Jenkins,
for
example,
you
wanting
in
this
room
configurator
so.
B
B
B
B
We
have
it
considered
that,
because
I
mean
the
authentication
part
was
suggested
by
in
so
that
we
study.
If
the
user
didn't
have
any
informations,
it
will
make
it
much
more
secure
to
have
there,
but,
as
he
suggested,
I
mean
that
could
be
possibly
one
of
the
things
that
we
would
consider
making
a
VSO
plugin
for
authentication
in
general,
so
that
we
can
support,
because
every
time
the
user
would
have
to
configure
it
for
every.
A
B
B
B
A
C
C
B
C
E
Yeah,
so
to
begin
with,
thanks
for
this
work
piece
is
amazing.
I
think
it's
going
to
be
really
useful
and
my
question
is
in
well
it's
more
a
thought,
but
in
a
in
an
enterprise
context
you
usually
have
to
manage
more
than
one
Jenkins
instance.
A
have
you
thought
about
somehow
integrating
the
schema
URL
into
the
Jenkins
Channel,
so
everything
you
need
is
inside
the
Jenkins
Gavin
already
other
than
the
username
and
password
that
that
could
be
IDE
setting.
E
C
A
C
A
C
A
A
B
So
the
first
plan
was
to
actually
get
the
nested.
Actually
I
was
going
to
get
the
nested
schema
modes.
I
didn't
account
for
my
confidence,
appearance.
Actually,
I
wasn't
sure
there
were
others
going.
So
sorry
for
that.
But
during
that
time,
I
guess.
The
next
part
of
the
project
that
I
had
planned
was
to
fix
the
nested
schema,
because
that
is
the
entire
PR.
That
probably
will
let
us
work
with
almost
all
of
the
descriptors.
As
you
can
see
here,
we
don't
have
some.
B
B
A
C
Yes,
I
think
doubts
are
in
a
much
better
shape
than
what
we
were
before
previously
at
the
feature
for
the
configuration
of
scope.
Schema,
unfortunately,
didn't
work
at
all
so,
okay
to
throw
that
code
out,
and
we
now
have
a
much
easier
well,
the
codes
a
lot
easy
to
follow
this
test
around
it
and
it's
much
easier
to
extend
and
fix
bugs
around
on
a
case-by-case
basis
before
it
was
some
pretty
crazy
jelly
code
that
not
very
many
people
could
understand.
C
C
You
have
auto-completion
everything
you
want
all
your
into
all
your
intelligence
and
the
vs
code.
Plugin
doesn't
do
a
lot
at
the
moment,
but
it
does
make
it
easy
to
fetch
the
schema
and
update
it
without
having
to
go
into
the
DNC
UI.
So
it's
quite
useful,
but
it's
a
good
starting
point
for
further
extensions
as
well
and
in
the
ideas
are
greatly
welcomed.
C
A
Thank
you,
so
yeah
would
like
that
it
was
with
all
first
coming
into
bridge
project,
so
yeah
community
breach
is
a
new
project
and
produced
by
Linux
Foundation
just
last
thing,
and
our
idea
was
to
try
out
some
project
ideas
which
we
can
self-fund
as
Jenkins
project,
so
basically
we're
using
Jenkins
funds
for
this
particular
wrong
and
they
be
doing
community
based
projects
again
next
year.
So
we
have
thanks
a
lot
to
slide
in
to
him
for
running
great,
because
yeah
I
know
that
it
was
a
bumpy
road
because
we
just
started.
A
We
still
need
to
document
something
it's
not
like
jae-seok,
which
has
probably
too
much
documentation
for
everything,
but
it
will
definitely
improve
and
any
feedback
will
be
welcome
from
what
I
see
that
we
actually
were
able
to
get
some
good
outcome.
Yeah,
it
needs
to
be
polished.
It
needs
to
be
integrated,
but
the
major
things
I
until
ated-
and
hopefully
it
will
be
useful
for
generations.
Portfolium
users.
C
B
C
A
Do
we
could
schedule,
for
example,
Jenkins
online
meet
up
to
talk
about
generational,
Scott
I'm,
not
sure
what
would
be
other
time
and
maybe
bid
for
Jenkins
fault,
maybe
after
so
for
example,
if
we
could
get
to
talk,
certainly
to
the
Jenkins
configuration
escort,
I'm
happy
to
organizing
online
it
up.
For
that.
A
B
C
A
C
A
This
week,
yeah,
listen,
Bob,
moaning
in
pain,
sounds
okay,
then
I'll
just
oh
stop
doodle.
So
if
all
of
us
agree
that
we
do
online,
Meetup
I
will
see
what
we
can
do
for
the
second
topic,
because
yeah
it's
better
to
have
two
presenters,
oh,
but
we
can
adjust
one.
Oh,
my
/
all
overview
of
Jake
asked
advancements
over
the
past
year
because
we
haven't
done
that
yet
so
yeah.