►
From YouTube: Online Meetup: Jenkins Configuration as Code: YAML validation and the Visual Studio Code Plugin
Description
Jenkins Configuration as Code (JCasC) plugin allows configuring Jenkins instances with declarative YAML files. These files may be quite complex, and hence it is important to have tools which help Jenkins users to create and verify such configuration files. During his Community Bridge project Sladyn Nunes has added a schema generator to the JCasC plugin and created a new Visual Studio Code plugin which provides auto completion and validation for your configuration files.
At this online meetup Sladyn will present his project and demo the new JCasC features he created. What will you learn?
* How to install the JCasC Visual Studio Code Plugin and connect it to your Jenkins Instance
* How to enable auto completion and validation for JCasC YAML files
* How to contribute further if you are interested
References:
- Slides: https://www.slideshare.net/SladynNunes/jenkins-jcasc-online-meetup
- JCasC Plugin for Jenkins: https://plugins.jenkins.io/configuration-as-code/
- JCasC Plugin for Visual Studio Code: https://marketplace.visualstudio.com/items?itemName=jcasc-developers.jcasc-plugin
- Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/268823268/
A
Okay,
hi
everyone
welcome
to
the
Jenkins
no
meet
up.
Today
we
have
a
presentation
by
our
slogan:
Yunus.
He
is
one
of
our
community
bridge
monkeys
who
was
working
on
Tchaikovsky
developer
tools,
in
particular
Visual
Studio
code
plug-in
and
a
llamo
computation
validation.
So
today
he
looked
isn't
his
work,
show
the
demo
and
then
we
will
have
a
lot
of
time
to
discuss
the
project
and
ask
questions.
A
B
Ok,
so
hello,
everyone,
I'm
Slaton
undergraduate
student
from
Mumbai
University
or
in
India
and
I've,
been
a
student
with
Jenkins
as
a
part
of
the
community
bridge
initiated,
and
the
main
aim
of
my
project
was
to
work
on
the
Jenkins
configuration
as
code
development
tools.
So
my
mentor
for
the
project
was
Tim
man.
He
helped
me
a
lot
in
the
project
so
shout
out
to
him.
Ok,
so
I
guess
basically,
I
can
just
dive
into
the
project
from
the
start,
and
then
we
can
maybe
go
on
to
questions
later
on.
B
So
if
you
have
any
questions,
you
can
put
it
in
the
chat
and
we
can
discuss
them
later.
So
I
would
begin
by
starting
out
as
to
what
the
project
is
about.
So
the
main
aim
of
the
project
was
to
enable
Jenkins
developers
to
validate
the
yamen
files
that
were
written
for
a
Jenkins
for
Jenkins
wire
Jake
asked.
So
if
you
are
familiar
with
configuration
as
code,
the
basis
of
it
is
to
be
able
to
configure
your
Jenkins
via
gamal
file.
B
So,
using
that
yeah
Mel
file,
you
can
load
in
into
Jake,
ask
a
basic
configuration
which
then
can
be
applied
to
your
instance.
So
we
sought
to
make
life
easier
for
those
users
by
developing
a
plug-in
so
that
they
can.
While
writing
the
Amal
file,
do
not
face
difficulties.
I
mean
that
is
basically.
We
are
so
used
to
programming
that
maybe
we
encounter
certain
problems,
while
coding
I
mean
using
auto-completion
or
maybe
getting
red
lines
on
to
the
editor,
so
that
we
know
that
hey.
There
is
something
wrong
with
our
file.
B
So
we
plan
to
bring
this
feature
in
to
Jenkins
configuration
s
code
so
that
when
developers
write
in
their
own
Yama
files,
they
are
very,
very
comfortable
and
they
can
go
out
of
the
box
and
just
write,
write
stuff
and
it
makes
it
a
seamless
experience.
So
so
that
was
part
of
my
project.
So
what
we
did?
B
We
went
and
made
some
sort
of
changes
to
the
configuration
data,
the
schema
generation,
so
that
the
schema
was
previously
being
generated
by
a
set
of
scripts
which
we
rewrote
in
Java
so
that
it
made
maintainability
and
modularity
out
of
the
box
so
that
we
could
I
mean
make
it
easier
for
us
to
debug
or
test.
So
that
was
part
one
that
was
part
one
of
the
project
and
by
the
end
of
phase
one
we
had
the
schema
developed
and
it
was
time
to
make
the
lives
of
developers
a
lot
more
easier.
B
Here
comes
in
the
plugin
that
we
wrote
for
Jenkins
configuration
as
code,
so
you
can
find
that
so
before
I
go
into
the
repository.
I
would
like
to
tell
the
users
more
about
what
we
thought,
while
developing
the
plugin.
So
basically,
we
went
and
developed
the
plug-in
so
that
it
pulls
in
your
leader
schema
file
from
your
Jenkins
instance,
and
then
using
that
schema
file
it
could
it
helps
you
in
Auto
completion
and
validation.
B
So
all
of
the
red
lines
and
all
of
the
auto
completion
he
just
come
in
with
in
Delhi
cells,
I
mean
in
vs
code.
So
there
is
no
separate
language
servant
of
Allah,
but
it
helps
us
but
I,
know
JAMA
file.
So
I
would
like
to
show
you
the
repository
for
the
extension.
So
this
is
the
tank,
its
configuration
as
code
extension.
This
is
the
source
code.
I
mean
if
I
would
come
into
how
to
contribute
later,
but
if
at
all,
you
want
to
I
will
be
publishing
these
lines
later.
B
So
if
you
need
any
links
or
any
any
sort
of
documentation,
resources
that
that
would
be
made
available
later.
So
this
is
the
entire
source
code
repository
and
we
have
the
documentation
which
explicitly
teaches
the
users
to
use
it.
The
user
guide
I
mean
some
basic
schema
and
what
are
the
features
that
it
provides,
how
to
run
the
script
on
the
plug-in
locally
and
some
screenshots
and
I
mean
which
tell
you
more
about
the
plug-in
and
how
to
get
it
activated.
B
So,
okay,
after
coming
after
finishing
with
this
over
score,
we
come
to
the
the
meat
of
it
yeah.
So
this
is
the
marketplace
for
Visual
Studio
code
I
mean
this
is
the
place
where
you
download
I
mean.
Obviously
you
can
download
the
plugins
in
built
from
your
from
your
vias
coordinate
it
up,
but
if
at
all
you
wanted
to
visit
the
plug-in
site,
you
can
do
that.
So
this
is
the
plug-in
side.
B
It's
called
the
Jake
ask
plug-in
you
can
I
mean
you
can
see
the
same
thing
that
it's
been
basically
pulled
from
the
repository,
so
you
can
find
any
sort
of
documentation,
resources
and
I
mean
if
you
want
to
install
it
locally,
the
number
of
downloads
and
stuff
the
latest
release
as
well.
So
this
is
the
place
you
want
to
be.
If
you
want
to
really
more
ever
the
official
plug-in
development,
so
yeah
so
moving.
B
What
is
the
plug-in?
Do
I
think
they
have
already
explained
to
you
what
the
plug-in
does.
Basically,
it
doesn't
need
you
to
doesn't
need
you
to
explicitly
configure
anything
apart
from
a
certain
user
name
token
and
a
URL,
and
you
can
find
the
plug-in
here.
So
I
already
showed
you
the
vs
code
marketplace
and
where
exactly
can
you
find
all
the
documentation,
SSA,
okay,
so
I
think
I
think
we
have
enough
of
documentation
and
enough
of
resources
here
to
begin
with
the
entire,
with
the
other
purpose
of
this
online
meetup.
B
That
is
the
demo,
so
I
guess
I
can
take
you
straight
into
it,
but
before
that
I
guess
one
of
the
prerequisites
you
need
to
have
is
a
Jenkins
instance
running.
So
so
what
I
have
done
is
just
sparked
not
or
basic
I
mean
basic
Jenkins
instance,
so,
with
all
of
the
most
commonly
used
plugins,
so
nothing
much
fancier,
just
basically
cloned
it
and
I
mean
I'm.
Sorry
just
downloaded
the
wall
file
and
just
ran
the
instance.
So
you
can
do
that
on
your
instance
as
well
and
with
the
new
schema
generation.
B
If
you
have
the
Jenkins
configuration
as
cloud
plug-in,
you
can
go
into
configuration
s
code
and
you
can
have
a
look
at
the
new
JSON
schema.
So
here
it
is
so
this
is
my
schema
if
I
can
go
scroll
down,
but
here
this
is
the
entire
schema.
So
if
you
have
your
instance,
you
can
check
this
out.
This
is
your
schema
file,
from
which,
in
vs
code,
we'll
use
this
to
generate
most
of
the
order,
completion.
So
yeah,
let's
get
right
into
it,
then.
B
So,
with
all
of
this
setup,
you
could
just
jump
into
your
editor.
Okay,
and
so
one
of
the
steps
would
be
first
of
all
is
to
obviously
have
the
Jenkins
plugin,
so
yeah
I'll,
just
so
for
demo
purposes.
I
would
install
the
plugin
yeah
I
mean
you
can
reload
your
file.
I
mean
your
vs
forward.
Instance
yeah,
but
that's
not
required
here.
B
I
guess,
okay,
I'm
moving
on
so
I
would
just
follow
in
with
the
guide
so
that,
if
at
all
you're
using,
if
at
all,
you
don't
refer
to
this
video
anytime
in
the
future,
you
can
just
refer
to
the
how
to
use.
So
what
you
need
basically
is
inside
the
Settings
tab
obvious
for
you
finding
the
plug-in
so
I'll
show
you
how
to
do
that.
So
you
want
to
find
you
go
into
preferences,
you
go
into
settings
and
then
you
so
much
for
I.
Think
it's
configuration
Astoria.
So
it
should
I
mean
apart.
B
If
you
have
any
other
vehicle
plug-in
from
Jenkins,
they
should
show
up
first.
So
if
you
have
the
matrix
authorization
or
you
have
any
sort
of
authorization
configured,
it
will
ask
you
for
a
username
and
a
token,
but
for
the
purposes
of
this
demo,
I
have
entered
the
basic
boilerplate.
I
mean
configuration,
use
a
token.
If
at
all
you
it
demands
for
a
user
token.
So
if
at
all
you
have
one
configured,
you
can
I
mean
you
can
enter
it
here.
We
are
working
on
making
this
use
experience
most
evilest,
which
I
will
discuss
later.
B
So
that's
in
the
future
scope.
So
what
you
do
is
basically
just
pull
in
your.
You
can
go
back
here:
okay,
yeah,
so
just
get
in
your
localhost
URL,
so
just
copy
paste
that
here
and
you
are
good
to
go
after
that.
So
yeah
the
next
step
would
be
to
use
to
activate
the
extension
so
on
my
Ubuntu,
so
I
can
use
control,
shift
and
P
that
would
open
up
the
I
mean
the
extension
list
which
I
want
to
accelerate
access,
so
Jenkins
fetch
configuration,
escorts.
Image
shows
right
up
because
I
recently
used
it.
B
If
at
all
it
doesn't
show
up,
you
can
definitely
go
ahead
and
type
it
yeah.
So
this
probably
nodes
in
the
configuration
you
might
see
a
progress
bar
to
your
bottom
left,
which
will
show
you
the
extension
getting
activated
and
that
would
load
in
I
mean
you
give
it
a
couple
of
seconds
and
that
should
that
should
probably
give
you
the
Jenkins
the
Jake
a
schema.
B
So
if
you
go
into
your
working
directory,
you
will
notice
an
entire
J
cast
schema
being
pulled,
so
the
plug-in
I
won't
go
into
the
detail
since
it's
a
more
of
a
hands-on
demo,
but
if,
at
all
any
of
the
users
are
concerned
with
this,
you
will
have
a
Jake
ask,
schema
or
JSON
generated,
and
if
you
want
to
know
more
about
it,
you
can
visit
the
editor.
I
mean
the
settings
or
JSON
which
will
automatically
pull
in
the
that
that
is
used
to
I,
mean
detect
dot
yml
file.
B
So
if
at
all,
you
want
to
change
that
configuration
I
mean
if
you
want
it
to
detect
some
sort
of
any
other
file,
I
mean
you
can
use
that
as
well,
but
for
the
purposes
of
this
demo
and
since
Jake
asked
opposed
by
ml,
we
have
this
already
put
in
so
yeah,
so
yeah,
so
I
can
begin
with
the
demo.
Okay,
so
first
of
all,
just
give
me
a
second
yeah.
So
first
of
all,
I
would
like
to
I
would
be
putting
headings
into
the
our
demo.
B
I
mean
the
headings
into
the
ml
file
as
to
what
I'm
going
to
be
showing
you
so
that
you
know
what
what
features
does
the
plug-in
provide
you
out
of
the
box?
So
I
would
like
to
begin
with
the
first
part,
that
is
the
correct
use
of
integers,
and
so
I
would
like
to
type
it
out
so
that
if
I
am
going
to
share
I
mean
you
can
manually
form
in
this
video,
it
makes
it
easier
for
you
so
configuration.
B
Yeah,
okay!
So
let's
begin
so,
if
you
hit
ctrl
P,
you
might
for
that,
okay
yeah!
So
if
you
go
on
right
here,
you
can
see
Jenkins
and
if
you
control
t
you
can
get
all
of
the
all
of
the
sort
of
I
mean
subcategory
that
you
can
configure
so,
for
this
have
chosen
number
of
executors.
So
if
you
check
it
out,
you
can
have
number
of
executors.
So
your
if
I
don't
know
what
now
execute.
B
As
this
is
and
I
just
a
hello
world,
it
will
tell
me:
hey:
that's
not
what
I'm
expecting
I'm
expecting
an
integer,
so
yeah
that
would
immediately
throw
up
in
here.
So
you
can
say:
okay,
yeah
number
of
executors
should
be
three
okay,
so
I'm
moving
on
to
system
message,
so
hit
control,
V,
again
system
message
and
now,
hey
I,
don't
know,
maybe
I
just
type
in
four
bit
for
some
reason
and
says:
hey:
no!
You
can't
do
that.
That's
not
allowed!
You
I'm
expecting
a
string
up
so
yeah.
B
So
that
would
give
you
the
another
word
and,
for
example,
you
might
get
confused
with
the
SCM
recount.
Try
and
maybe
I,
don't
know
what
that
is,
and
maybe
I
just
end
up
some
random
string,
value
or
whatever,
and
then
it
just
tell
me
hey,
no,
that's
not
what
I'm
expecting
I'm
expecting
an
integer,
so
yeah
that
you
can
end
up
and
one
of
the
things
one
of
the
most
important
ones
here
is
the
the
use
of
enumerations.
B
So
as
a
normal
user,
if
at
all
I
don't
know
what
mode
is
I
might
be
tempted
to
enter
something
like
hey
I
mean
mode
here,
and
it
immediately
throws
us
and
every
value
is
not
accepted.
Your
valid
values
are
normal
and
exclusive,
so
the
configuration
the
plug-in
automatically
tells
you
that
they
are
and
allowed,
and
it
also
may
tell
you
in
certain
instances
what
kind
of
values
are
not
if
they
are
enumeration.
So
in
this
case
my
mode
is
normal
or
exclusive.
Any
other
value
won't
be
accepted.
So
it
saves
you
time.
B
Writing
this
Yama
file,
so
you
can
go
in
with
normal
and
then
yay.
Now
the
the
plug-in
will
tell
you
hey,
everything
is
fine.
Okay,
so
I
would
like
the
next
part.
I
would
like
to
demo.
Is
the
use
of
documentation
now
this
feature
is
not
entirely
flawless
because
we
have
been
working
on
making
documentation
more
available
to
the
that
there
are
certain
instances
where
it
isn't
well
documented,
so
certain
parts
of
your
code
might
not
have
documentation
and
you
might
not
know
what
each
and
every
of
those
values
mean
but
hey.
B
We
have
tried
it
so
far
and
this
part
tells
us
about
more
about
how
can
you
learn
more
about
what
configuration
to
use?
So
forgive
me
Polly,
Spelling's,
the
documentation,
yeah,
okay,
so
yeah!
So
if
you
go
into
security
and
you
go
into
API
token,
so
it
should
give
us
yeah
here
it
is
so
this
should
give
us
creation
of
legacy
token
in
April,
so
yeah
it
is
more
about
what
it
is.
What
legacy
token
is
what
new
you
API
to
what
what
accepts
and
more
about
how
the
developer
has
written
more
about
it.
B
B
There
are
certain
times
where
you
may
not
get
this
feature,
but
we
have
tried
our
utmost
best
are
including
it
wherever
possible
or
where
there
is
an
open
issue
in
Jake
as
to
be
able
to
include
more
of
this,
so
that
we
can
I
mean
get
this
four
out
of
the
box,
so
that
users
can
know
I
mean
what
what
what
what
are
they
writing
exactly
and
what
eats
what
each
sub
configuration
does
mean
so
yeah
this
would.
This
would
demonstrate
more
of
the
documentation
aspect
of
it.
B
I've
chosen
this,
you
can
chew,
you
can
by
writing
your
files.
If
you
don't
get
documentation,
you
can
open
up
an
issue
and
maybe
look
into
it.
Okay.
So
for
the
purposes
of
this
demo,
these
are
the
two
main
uses
of
it.
I
mean
since
there
isn't
I
mean
explicitly
any
use
case
which
we
would
like
to
demo.
But
what
we
were
trying
to
overcome
is
the
nesting
of
nesting
of
configuration,
so
that
has
been
well
achieved
here
and
your
so
you
can
enter
whatever.
B
So
if
I
was
a
developer
and
I
wanted
to
write,
maybe
a
configuration
file
for
the
get
SCM
I
would
just
jump
into
it
directly
and
just
begin
I
mean
so
so
we
have
so
as
a
developer.
Maybe
I
know
that
there
is
one
of
shin.
Okay!
Sorry
for
that
yeah
there
is
just
something
called:
is
unclassified,
so
hey
so
that
it
has
me
okay,
unclassified
and
now
I
I
would
like
to
choose.
What
is
the
next
value
so
I
realize?
B
Okay,
I
need
get
SCM,
so
yeah
cute,
oh
hey
yeah,
so
that
shows
me
get
SCM
and
now
I
would
like
to
know
what
other
fields
I
can
configure
under
it.
So
if
you,
if
you
were
probably
writing
this
Yama
file
before
this
plug-in,
was
developed,
you
would
probably
have
to
look
up
the
documentation
or
look
up
the
demo.
But
hey
we've
solved
all
of
that,
so
no
hands
so
yeah.
B
Basically,
you
can
use
the
global
config
email
and
enter
your
email,
and
then
you
can
okay,
so
a
friendly
you
made
you
say:
hey
I
need
maybe
a
global
configuration
name
and
so
yeah.
You
can
enter
that.
So
there
isn't
in
just
for
purposes
of
this
demo
and
okay.
So
then
I
realize
create
account
based
on
email,
no
wife.
Maybe
if
I
don't
know
what
the
value
is
and
I
enter,
something
yes
and
then
I
realize
no
hey
I
mean
it
requires
a
GUI,
so
yeah.
B
If
I
wanted
any
other
use
case
such
as
use
existing
account
to
it,
email-
and
it
would
tell
me-
I-
need
a
boolean
again
so
yeah,
so
you
can
just
yeah.
That
would
probably
give
you
the
entire
gate.
Scm
configuration
right
out
of
the
box,
and
here
so
it's
validate
and
you
load
it
into
your
Jake,
ass
and
boom.
You
have
a
running
Jenkins
instance,
and
that
saves
us
a
lot
of
time.
I
mean
rather
reloading
it
again
and
again
so
yeah.
So
this
was
the
entire
demo
section.
B
I
mean
where
I
take
in
some
files
are
never
attended
yeah.
So
this
was
basically
the
entire.
The
entire
I
mean
meet
of
the
demo.
If
you
would
say
that
is
about
it,
but
moving
on
from
that
I
mean
I
would
like
to
tell
uses
about
what's
next
for
the
plug-in,
but
just
before
I
get
into
what's
next,
for
the
plug-in,
I
would
like
to
tell
users
how
they
could
basically
contribute
to
this
plugin,
so
I
would
be
including
links
in
the
online
mean
in
the
meat
I
mean
in
the
slide.
B
B
We
don't
have
a
lot
of
issues
here,
but
if,
at
all,
you
have
any
feature
requests
or
any
sort
of
issues
that
you
would
like
to
raise,
feel
free
to
just
jump
in
and
open
a
new
issue
and
we'll
definitely
look
into
it,
and
so
this
is
how
we
would
love
to
except
we
would
have
to
see
some
pull
requests
from
you
on
some
of
the
most
desired
features
for
this
plugin.
We
have
a
cuter
channel
as
well,
which
will
be
linked
into
the
online
meetup
sites.
B
You
can
jump
in
there
and
I
know
me,
ask
questions,
requests
for
features,
and
we
would
definitely
look
into
it.
Apart
from
that,
I
mean
just
before
I
jump
into
this.
This
is
more
of
a
open
discussion,
but
I
included
a
what's
next
for
the
plug-in.
So
we
wanted
to
address
some
of
the
existing
issues
and
bugs
that
we
have
with
the
plug-in
like
it,
doesn't
provide
some
user
feedback
on
certain
cases
and
there
was
a
common
configuration
for
use
by
other
ways
for
plugins
open,
and
we
could
be
more
having
a
look
at
this.
B
So
this
is
I
mean
this
is
the
direction
we
want
to
take
the
plug-in
into,
and
it's
more
of
an
open
focus
on
new
features.
I
mean
if
at
all,
we
could
develop
some
sort
of
an
interface
where
we
can,
where
users
don't
have
to
configure
their
settings
again
and
again
for
different
vs
code
plug-in.
We
would
be
working
on
that.
So,
if
I
told
you
have
any
idea,
suggestions
feel
free
to
join
in
the
get
a
charter
feel
free
to
I
mean
free
free
to
open
issues.
A
Thanks
a
lot
for
a
presentation,
it
was
really
interested,
so
one
command,
mostly
for
the
record
that
we
apparently
go
to
the
application
of
meetings.
So
we
had
something
like
15
to
20
people
strangulated
another
call
with
the
same
arrow
and
basically
we're
unable
to
do
anything
with
it.
So
we
will
be
publishing
the
recording
call
this
meetup
and
we
will
be
a
cop
if
needed.
So
my
apologies
to
everyone
who
was
affected.
C
A
Right
yeah
welcome,
as
I
said
in
the
beginning,
it
was
our
first
experiment
with
community
bridge
mentorship,
so
just
explain:
Jenkins
gets
funding
and
state
funding
through
donations,
and
we
use
this
money
to
project
on
our
work
pretty
well.
So
we
hope
to
keep
you
it's
all
thanks,
pardon
or
all
your
hard
work.
It's
not
only
related
to
Jake
asked
studying,
also
help
us
to
stuff
some
things
for
google
Summer
of
Code
for
plug
in
documentation,
immigration
and
for
many
others.
So
thanks
a
lot
for
all
your
contributions.
A
A
B
B
It
might
not
give
you
the
feedback
that
you
require,
so
that
would
be
one
limitation
and
I
mean
the
other
limitation
is
the
documentation.
So
if
you're
expecting
this
schema
to
throw
up
documentation
for
every
single
configuration
file
that
you
write,
you
might
be
disappointed
to
see
that
it
isn't
included,
because
that
is.
That
is
an
area
that
we
found
out
where
development
that
there
isn't
enough
documentation
for
the
part
of
the
fields
I
mean.
So
we
have.
B
Yeah,
so
the
best
way,
if
you
have
any
other
limitations,
the
best
way
to
the
food
issues
is
on
the
the
Jake
ask
we
escort
extension
I
mean
the
source
code
repository
or,
if
you
are
in
much
of
I
mean
if
you
aren't
comfortable
with
reporting
issues
here,
you
can
definitely
drop
into
our
get
a
chat.
So
what?
If,
once
I
publish
these
slides?
You
can
definitely
look
into
our
guitar.
B
Just
hop
in
there
ask
questions
report
issues
throw
up,
throw
up
any
I
mean
anything
that
you
want
to
know
about
it
or
contribute
or
whatever
feel
free
to
jump
in.
We
would
love
your
contribution
so
yeah,
that's
that's
the
best
way.
I
mean
to
get
involved
with
the
plug-in
development.
If
you
have
any
more
new
ideas,
you
can
definitely
post
it
on
the
Jenkins
developers,
group
or
even
come
to
come
visit
a
get
a
Chad.
We
would
be
really
excited
to
meet.
You.
A
For
the
future,
we
can
have
more
features,
for
example,
yeah
the
JSON
specification,
which
is
generated,
it's
just
the
first
step
and
it
can
be
consumed
not
only
by
Jake
asked
plug-in
provisions
to
do
code
by,
but
by
other
plugins.
So
maybe
somebody
would
like
to
create
an
online
service
which
believeit,
so
the
contracts
may
be
as
a
part
of
the
Jenkins
instance.
So
there
is
still
a
lot
of
opportunities
to
contribute
if
you're
interested
in
such
topics,
yeah.
A
If
now
I
think
we
could
close
down
the
meetup
schüttler,
are
you
thinking
about
doing
a
second
presentation
about
read-only
system
configurations,
so
the
hitch
which
was
just
released
in
this
weekly?
Okay,
since
the
rate
image
icon,
also
is
unable
to
connect
to
the
core.
You
have
to
postpone
it
to
the
next
yeah.