►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay
in
real
life,
all
right!
Well,
thanks
everyone
for
sticking
around
here
to
the
end
of
the
contributor
summit.
It's
been
a
lot
a
long
day
with
lots
of
good
talks
and
what
I'll
be
showing
today
is
mostly
live
demo.
So
no,
no
slideshows
or
anything
like
that
and
we'll
be
looking
at
hyper
modern
pipeline
development
using
visual
studio
code
and,
in
particular,
we're
going
to
be
looking
at
three
different
extensions
that
will
really
take
your
pipeline
development
to
the
next
level.
A
All
right,
so,
if
you're,
you
know
new
to
the
visual
studio
code
and
the
extensions
you
can
usually
go
to
their
marketplace
online
and
google
for
what
you're
looking
for,
like
you
know
what
you
might
google
for
jenkins
or
you
might
google
for
groovy
and
click
the
install
button,
and
it
will
install
and
also
there's
an
extension
pane
that
you
can
also
do
the
same
thing.
A
You
can
search
for
the
extensions
that
you
want
and
it
will
pull
them
up
and
allow
you
to
install
them
so
starting
out
right,
you're
wanting
to
write
some
kind
of
pipeline
and
we
almost
always
start
with.
Like
the
you
know,
the
node
block.
So
as
I
start
typing,
we
instantly
start
seeing
some
auto
completion
of
steps
that
are
available
inside
of
jenkins.
A
So
we
get
the
node
block
and
we
see
in
the
far
right
corner
that
it's
part
of
the
workflow
durable
task,
step
plugin,
and
it
tells
us
exactly
what
this
particular
block
of
code
can
do
for
us
and
if
we
use
the
auto
completion
to
complete
it.
For
us
we'll
get
these
wrench
icons
and
these
are
going
to
be
for
the
parameters
that
this
particular
step
can
take.
A
So
here
we
see
that
it
takes
a
label
and
we
get
all
kinds
of
detail
inside
the
id
ide
about
what
the
label
can
do
and
how
we
can
use
this
label.
B
A
And
so
a
lot
of
this
code,
I'm
actually
going
to
reuse
for
some
other
plugins.
So
that's
why
it's
important.
A
All
right-
and
so
we
might
want
to
throw
an
error
right,
so
the
first
thing
I
did
was:
I'm
checking
just
to
make
sure
that
the
variable
message
isn't
null
so
just
doing
a
null
check,
and
then
you
know
if,
if
this
get
result,
is
some
kind
of
test
result
we
might
want
to
check
to
see
if
the
test
result
is
a
failure.
So
I'm
checking
for
that
and
if
it
is
a
failure,
we
probably
want
to
stop
the
pipeline.
A
So,
as
I
type
error
we're
going
to
get
some
more
help,
all
these
again
are
steps
that
can
be
run
inside
the
pipeline
and
we're
seeing
that
you
know
we
can
signal
an
error
and
it's
it's
the
same
as
throwing
an
exception
right,
but
this
won't
print
a
stack
trace,
which
I
don't
want
for
this
particular
message.
C
A
And
then,
at
the
end,
right
of
my
pipeline,
so
I've
gotten
my
test
result:
I've
thrown
some
kind
of
error
to
kill
the
build
if
the
test
result
is
not
good,
and
now
I
want
to
echo,
maybe
the
results
right
or
I
want
to
print
the
results.
So
here
again
we
can
use
the
auto
completion
to
figure
out
exactly
what
we
need
to
do
and
what
I
really
like
about
the
jenkins
doc
plug-in
is.
It
allows
me
to
find
so
many
steps
inside
of
jenkins
that
I
didn't
even
know
existed.
A
So
if
I
want
to
look
like
if
I
type
right,
I
get
all
these
different
things
that
I
might
not
have
known
about.
I
knew
about
json
and
yaml,
but
I
didn't
know
there
was
xml
and
csv,
and
these
kind
of
things
same
thing.
If
I
want
to
type
like
build,
we
start
seeing
all
these
different
things
that
I
just
didn't
know
was
possible
inside
of
a
jenkins
job
again,
and
most
of
these
are
plugins.
A
You
probably
don't
have
them
on
your
jenkins,
but
this
will
also
tells
you
the
plugins
themselves
and
how
to
get
to
them
or
which
ones
to.
A
I
download
to
use
some
kind
of
environment
variable,
but
I
forget
maybe
the
exact
syntax
or
the
exact
variable
I
want
so
here
it's
giving
me
a
bunch
of
predefined
variables
that
I'm
most
likely
going
to
have
access
to
inside
of
my
pipeline.
A
And
so
this
has
been
a
really
great
plug-in
for
me,
just
in
day-to-day
building
pipelines
at
work.
A
So
moving
on
to
the
next
one,
we'll
talk
about
groovy,
lint
format
and
fix-
and
this
is
a
really
good
plugin,
because
it's
not
just
going
to
make
your
code
more
consistent,
but
it
actually
helps
me
find
bugs
all
the
time
little
little
things.
I've
done,
that
is
incorrect.
That
was
was
not
going
to
work
correctly.
This
will
usually
find
it
and
warn
you
in
some
type
of
way.
A
So
going
back
into
my
editor,
I
actually
disabled
some
of
these
so
that
they
would
not
interfere.
So
I'm
going
to
enable
this
one
all
right,
it
should
run
and
I
actually
have
some
pre-configured
jobs.
So
this
is
going
to
be
the
same
code
that
we
just
wrote.
A
Now
I'm
hoping
this
plugin
kicks
in,
I
might
reload
my
window
just
to
make
sure
that
the
plugin
is
going
to
work.
A
C
A
Yeah
so
now
it's
reporting
47
problems,
but
most
of
the
problems
are
just
the
blank
lines.
So
it's
going
to
highlight
issues
that
it
finds
inside
your
code
and
if
you
hover
over
them,
you're
going
to
get
a
little
bit
of
a
sneak
peek
of
why
it's
throwing
an
error.
So
here
it's
telling
me
that
this
string
is
really
just
a
regular
string
and
it
doesn't
have
to
be
wrapped
in
double
quotes
like
a
groovy
string
that
has
variables
in
it
and
what
I
really
like
is.
A
If
we
go
to
quick
fix,
it
will
automatically
fix
some
of
these
things
for
you.
So
if
I
want
to
replace
just
this
example
or
all
examples
in
this
file,
it'll
do
that.
I
can
also
disable
things
which
I'll
show
you
in
a
second.
A
But
what
I
really
like
is
when
sometimes
it'll
show
me
an
error
that
with
the
code
that
it
doesn't
like-
and
I
don't
understand
it,
but
if
I
click
the
link,
it
will
say
it'll
give
me
a
little
bit
more
in
detail
about
why
you
wouldn't
want
to
do
what
you're
doing
and
even
more
detail.
If
you
actually
click
the
link,
it
will
take
you
to
the
codenark
webpage,
which
is
the
actual
underlying
tool.
That's
doing
this,
which
is.
A
I
can
talk
about
that
as
well
about
the
hierarchy
of
open
source
projects
which,
which
kind
of
make
this
possible.
So
at
the
very
bottom
of
the
layer
we
have
the
codenart,
which
is
what's
actually
doing
the
linking
and
then,
if
we
go
back
to
the
marketplace
page,
there
is
a
packaged
version
of
codemark
using
npm.
A
So
someone
has
packaged
up
codenark
and
npm
and
then
the
visual
studio
code,
groovy
lint
extension,
is
using
that
package
code
server.
So
that's
kind
of
the
hierarchy
there,
but
yeah.
Not
only
does
it
show
you
lots
of
different
warnings,
but
it
usually
has
pretty
good
detail
on
why
it's
complaining
and
it
allows
you
to
really
understand
hey.
Should
I
ignore
this,
or
should
I
enforce
this,
you
know
and
those
kind
of
things.
A
So
if
you
want
to
enforce
something
you
you
know
like,
I
said,
there's
the
quick
fix-
and
you
can,
you
know-
fix
just
this
example
or
all
examples,
but
what
you
can
do,
there's
two
different
things.
You
can
run
format,
format
will
fix
everything,
but
you
can
also
run.
I
think
it's
yeah
fix
all
autofixable
problems,
and
that
does
the
same
thing.
A
So
if
I
click
this,
the
code
is
going
to
get
formatted,
so
it
took
away
all
the
extra
space
that
I
did
when
I
when
I
hid
this
function
from
you
guys
it
fixed.
I
had
weird
spaces
here.
I
had
double
quotes.
Actually,
if
I
go
back,
we
can
see
it
right.
So
there
was
just
some
spacing
issues
that
it
didn't
like
some,
quoting
issues
that
it
didn't
like,
but
it
will
fix
all
those
and
then
one
of
the
things
that's
left
is
this,
which
I
find
really
unique.
A
A
Like
this,
so
it's
the
same
code
just
without
the.
If
and
so
those
are
the
kind
of
fixes
that
you
can
expect,
there's
actually
literally
thousands.
So
I'm
not
going
to
show
you
every
single
kind
of
fix
that
you
can
get.
Let's
see,
what
do
we
got
down
here
yeah,
so
this
is
saying:
hey
this
could
be
a
fill.
You
don't
need
to
write
a
getter
for
this
that
thinks
it's
a
getter.
A
I
can
go
to
quickfix
and
I
can
say
well,
let's
disable,
that
for
this
file
and
when
I
do
that,
I'm
going
to
get
a
a
comment
block
at
the
top
and
that
disabled
that
warning
this
is
saying:
hey
you
have
a
you,
have
a
duplicate
duplicate
string
literal.
So
I
have
failure
here
and
I
have
tell
you
here
I
can
get
rid
of
that
and
I
can
do
this
by
doing
it
per
line
like
this
or
what
you
might
find
for.
A
Some
of
these
things
is
to
you
want
to
enforce
it
in
your
entire
project
and
so
for
that,
if
I
it
will
automatically
create
the
file
for
me,
but
I'm
using
an
existing
repository,
but
it'll
create
this
groovy
lint
file
and
here's
the
things
that
I'm
enforcing
or
not
enforcing
for
my
entire
project
so,
like
I
said,
it'll
create
this
file
for
you.
If
you
right
click
or
do
the
quick
fix
and
do
disable
for
entire
project,
it'll
go
ahead
and
and
put
it
in
here,
put
it
in
your
file
for
you.
A
Yeah,
so
that's
it
I
mean
there's
lots
and
lots
and
lots
of
fixes
that
it's
going
to
have
that.
I
didn't
show
here
today,
but
yeah
you
can.
You
can
get
more
information
about
these
errors
or
you
can
just
ignore
these
errors
completely.
A
And
then
the
third
thing
I
would
extension
I
would
like
to
show
today
go
away
there.
A
We
go
is
groovy
guru,
and
so
what
groovy
guru
is
is
it
provides
auto
completion
and
intellisense
for
your
groovy
code,
so
not
the
pipeline
steps,
but
the
actual
groovy
code,
so
groovy
classes,
groovy
primitives,
like
lists,
and
things
like
that-
and
this
is
also
built
on
a
bunch
of
open
source
projects
so
powering
it
is
the
open
source,
groovy
language
server,
which
has
been
open
source
and
brought
to
you
guys
by
a
company
called
moonshine
ide
that
builds
some
kind
of
java
based
ide.
A
So
it's
pretty
cool
that
they
have
open
source
that
and
they
also
provided
the
starter
extension
code
for
the
groovy
guru
extension,
and
so
what
we'll
do
is
we'll
turn
this
on,
and
I've
actually
been
having
a
lot
of
problems
in
a
recent
update
with
with
docker,
where
it's
been
crashing
and
taking
out
my
entire
wsl.
A
All
right,
so
this
is
the
exact
same
code
that
we
had
before
the
code
that
we
linted
and
set
up,
and
so
one
of
the
things
that's
interesting
is
with
the
groovy
guru
extension.
A
We
can
get
more
information
about
the
exact
method,
that's
being
called
in
the
type
that
it's
returning
so
here
the
get
result
function
returns
a
string,
and
we
can
see
that
in
the
editor
that
it's
returning
a
string,
but
even
though
that
we've
defined
message
as
being
an
object,
you
know
we
use
the
define
keyword.
A
It
still
understands
that
message
is
a
string
right,
so
we
haven't,
we
haven't
confused
it
because
we
didn't
type
it
inside
of
our
pipeline
job.
As
long
as
the
function
is
typed
correctly,
the
groovy
language
server
is
going
to
understand.
What's
going
on
here,
one
of
the
things
we
can
do
is
you
know
we
have
this
test
result
that
comes
back
as
failure,
but
you
know
someone's
eventually
going
to
change
that
and
they're
going
to
say.
Well,
it's
a
test
failure
and
then
our
job
is
going
to
break.
A
So
one
of
the
things
we
can
do
is
we
can
come
in
here
and
and
fix
that
by
getting
all
the
different
methods
that
can
be
called
on
a
string
inside
a
groovy,
so
we
can
come
through
here
we
could
look.
Most
languages
have
some
kind
of
contains
message
where
we
can
contain
a
substring.
So
here
it
is,
and
then
we
can
put
our
failure
in
this
right
and
we
can
look.
A
We
can
see
that
message
or
contains
is
is
going
to
return
to
us
a
bullying
and
it's
going
to
take
some
kind
of
character:
sequence
as
a
parameter.
A
Some
other
things
that
you
can
do
with
with
goofy
gru
is.
It
will
also
do
doc
strings.
So
if
we
come
down
here.
A
We
can
write
some
kind
of
doc
stream,
actually
I'm
gonna
copy
and
paste,
because
I
already
have
one
one
ready.
A
So
we
we
can
write
this
doc
stream
and
then,
when
we
hover,
we
get
the
docs
string
inside
of
our
ide
right.
So
if
you're
using
jenkins,
shared
libraries
and
you're
writing
docs
strings,
but
maybe
you
don't
get
to
really
use
them
inside
of
your
ide
when
you're
writing
your
jobs.
Now
those
dot
strings
are
going
to
be
available.
A
The
other
thing
that
goofy
guru
can
do
for
you
is
help
you
with
your
imports.
So
I'm
inside
my
shared
library
right
now
and
hopefully
yeah.
This
will
pull
up
all
the
different
classes
and
things
that
I
can
use
inside
of
this
job.
A
So
we
can
do
something
like
system
dot,
I'm
looking
for
platform
there.
It
is
so
we
can
import
something
like
this
another
way
you
can
import
things.
If,
if
you
start
typing
the
class
name,
it
will
also
import
it
automatically.
A
A
A
Let's
see,
did
I
miss
anything,
I
think
that's
about
it.
So
that's
three
different
plugins
that
you
can
use
inside
of
visual
studio
code
that
will
make
your
jenkins
pipelines
faster
to
write
and
for
me
it
catches
a
lot
of
bugs
and
gotchas.
I
guess
that's
one
thing
I
didn't
cover
with
the
linting,
but
if
I
return
something
right
here,
it's
going
to
detect
that
this
code
is
all
dead
code
that
this
code
can't
be
reached.
So
these
are
the
kind
of
little
fixes
that
the
linter
can
find
for
you.
C
It
looks
really
great,
though,
when
I
was
preparing
my
presentation.
I
did
presentation
about
visual
code
development
flow
on
tuesday
and
there
I
had
a
lot
of
issues
with
plug-in
response
times,
because
sometimes
they
seem
to
be
hanging
for
something
like
minutes
before.
Producing
results
and
suggestions.
C
A
Are
these
visual
studio
code
plugins?
Yes
yeah?
I
don't,
I
haven't
used
them.
I
don't
think
so.
The
ones
I
showed
today
was.
Are
you
talking
about
the
ones
I
showed
today.
C
Or
different
for
static
analysis,
not
for
static
analysis.
I
use
another
plugin.
A
Yeah,
so
I
think
for
the
groovy
lint,
I
think
they've
acknowledged
that
for
very
large
jobs
for
or
for
lots
of
code
it
can
be
slow
and
I
have
I
have
found
it
to
be
slow,
but
I
find
that
it's
better
if
I
don't
open
up
too
many
tabs,
so
just
like
chrome,
if
I
don't
have
15
or
20
groovy
files
up,
it
seems
to
know
to
only
link
the
one.
That's
open.
D
I
I
have
a
question
levy
sure
you
said
when
you
started
the
demo
for
the
groovy
guru,
which
uses
the
groovy
language
server.
Does
that
mean
that
the
code
I'm
editing
gets
uploaded
to
a
server.
A
A
A
There
we
go
so
it's
pointing
to
the
groovy
language
server,
dot
jar
so
that
it's
all
running
locally.
A
Yep
and
most
of
the
auto
completion
that
you're
going
to
have
in
visual
studio
code
is
all
using
most
of
it,
as
far
as
I
know,
is
using
the
same
kind
of
format,
the
the
groovy
or
I'm
sorry,
the
microsoft
language
server
specification
so
like
node
and
python
all
use
some
kind
of
binary
or
application
to
actually
handle
it,
handle
the
duties
of
auto,
auto
completion.
You
know
and
and
displaying
comments,
and
things
like
that.
D
So
this
cannot
know,
which
instance
of
jenkins
you're
targeting
so
when
you,
when
you,
when
you
use
methods
in
here
that
you
you
need
to
install
the
plugin,
and
you
pointed
out
that
it
will
tell
you
which
plugin
the
step
comes
from,
so
you
could
install
it.
Does
it
have
any
ability
to
give
me
a
list
of
the
plugins
that
I'm
sort
of
implying
in
my
file
after
I'm
after
I'm
done.
Writing
my
my
beautiful
jenkins
file.
A
No,
no
not
currently.
I
think
that
would
be
a
good
feature
enhancement
for
it
to
maybe
leave
a
comment
at
the
top
of
the
file
that
these
are
the
required
plugins
for
this
job.
I
think
that
would
that
would
definitely
be
a
great
enhancement
to
it,
but
yeah
currently,
I'm
not
sure
how
they
get
all
the
steps
and
stuff
inside
of
the
plug-in
I'm
guessing
they
are
creating
it.
Just
like
the
jenkins
plug-in
pages
where
they,
you
know,
every
plug-in
step
has
that
kind
of
self-built
documentation.
C
A
Sure
so
yeah
every
plugin,
that's
in
like
the
plugin
documentation,
is
going
to
be
represented
here
regardless.
If
it's
on
your
jenkins
instance
or
not,
I
think
oleg
you
had
mentioned
in
the
past
that
it
would
be
cool
to
connect
it
to
a
running
jenkins
and
only
show
what's
approval
to
you.
That's
definitely
something
that
could
be
done,
but
yeah.
I
think
a
good
first
step
would
be
to
have
some
kind
of
command
inside
of
visual
studio
code.
A
C
Yeah,
unfortunately,
it
misses
one
of
popular
cases
pipeline
libraries,
because
right
now
a
language
server
doesn't
retrieve
any
information
from
your
local
instance
and
the
additional
additional
would
be
not
only
filtering
out,
what's
not
there
but
adding.
What
is
there.
A
C
We
also
did
a
presentation
on
tuesday,
but
we
were
focusing
rather
testing
pipelines,
so
we
spent
more
time
on
pipeline
test
unit
and
other
beats,
but
we
also
briefly
talked
about
the
visual
studio
code
setup.
A
There
was
a
conversation
in
the
jenkins
discourse
about
what's
the
best
way
to
do
pipeline
development
nowadays,
and
so
everyone
was
talking
about
how
they
do
it,
and
I
learned
a
lot
from
that
and
then
again,
like
you,
said,
oleg
you
presented
kind
of
the
same
thing
as
this,
but,
except
for
you
didn't
go
into
much
detail
about
the
actual
writing
of
the
code,
but
more
of
how
do
we
take
this
code
and
then
test
it
and
get
it
into
a
running
jenkins
as
quickly
as
possible
or
or
like
shortening
that
feedback
loop.
A
So
that's
kind
of
what
I
got
going
on
here.
It's
really
not
a
part
of
this
talk,
but
this
entire.
This
entire
editor
is
running
inside
of
a
jenkins
container,
with
a
full-fledged
jenkins
and
there's
nothing.
Anyone
has
to
do
to
get
that
running
themselves
if
they
have
docker
and
visual
studio
code
and
they
open
this
repo
they'll
automatically
run
their
job
inside
of
that
jenkins
container.
A
Yeah,
so
it's
doing
what
it's
supposed
to
do.
It's
it's
erroring
failure,
but
if
we
come
back
into
here-
and
we
change
this
message
in
this
function
at
the
bottom-
from
failure
to
hello,
jason,
cs
jenkins,
contributor
summit-
if
we
go
back
into
jenkins
and
rerun
this
by
hitting
build,
I'm
hoping
we
get
the
updated
changes
we'll
see
in
a
second.
A
No,
no,
I
didn't
get
the
updated
changes,
so
I'm
not
sure
what
that
is,
because
this
usually
works
did
I
change
the
wrong
file.
B
A
Okay,
yeah,
I'm
not
sure
why
it's
not
working,
but
the
way
it
usually
works
is
it's
using
the
what's.
It
called
that
that
checkout
step
the
file
checkout
step.
A
B
A
A
Oh,
I
know
why
so
at
the
top,
it's
only
loading
libraries.
So
if
I
would
go
into
a
library
right
now
and
make
a
library
change,
the
library
change
is
going
to
be
live
on
every
build.
So
if
I
go
into
my
shared
library
and
add
something
it
would
be
live,
the
job
itself
is
created
when
the
jenkins
container
is
created,
so
it
points
to
a
static
file.
So
if
I
go
to
configure
it's
never
going
to
change
right,
it's
whatever
the
job
was
when
it
was
created
when
the
container
started.
So
that's
my
bad.
A
A
C
It
totally
does
so
yeah
thanks
for
the
inter
introduction.
Yeah,
the
visual
studio
code,
developer,
tooling,
is
very
promising.
So
I
guess
it's
right
now:
it's
the
best
stack
available
for
jenkins
pipeline
development
and
yeah.
I
believe
it
will
retain
the
best,
at
least
until
somebody
implements
pipeline
debugger.
D
A
D
And
perhaps
libraries
do
you
remember
which
yep.
A
Yeah,
this
is
kind
of
someone
just
asked
hey,
you
know
how
do
how
are
people
doing
their
pipeline
development
and
lots
of
people
kind
of
weighed
in
with
all
the
different
ways
that
they
get
their
code
quickly
into
jenkins
and
yeah?
It
was.
It
was
a
great
starting
point
and
then
a
leg.
I
haven't
seen
your
recording,
but
I
know
you
shared
the
slides
on
your.
C
Yes,
all
my
recording
won't
be
particularly
useful
because
it's
in
russian,
oh
yeah,
consider
doing
presentation
again,
but
at
the
same
time
you
presented
the
entire
development
tools.
Part
basically
more
details
than
me,
but
maybe
we
will
cover
it
with
stanislav
of
charge
to
present
something.
B
C
Yeah,
so
for
me
a
question
is:
do
you
have
roadmap
for
extension
park?
Do
you
plan
to
integrate
any
additional
plugins
and
use
cases
there?
The
visible
future.
A
Sure,
yeah
so
yeah.
Anyone
that
wants
to
see
an
extension
at
it
is
is
happy
to
either
raise
a
pull
request
to
add
it
or
you
know,
create
like
a
feature
request
for
it.
I
would
like
to
I
guess:
I
chose
the
wrong
name
for
it.
Jenkins
extension
pack
is
pretty
bland.
I
want
something
specifically
for
developing
pipelines.
A
I
was
probably
be
my
only
prerequisite
and
I
want
I
I
just
kind
of
want
to
keep
it
to
things
that
I
feel
like.
I
can't
live
without.
I've
tried
a
bunch
of
different
extensions
and,
like
you
said,
some,
don't
work
so
great
and
they're
more
frustrating
than
they
are
rewarding,
but
yeah.
I
would
love
to
find
and
keep
discovering
better
and
better
pipeline
extensions
or
things
that
will
help
me
be
better
and
quicker
day
to
day,
because
I
write
a
lot
of
pipelines.
C
C
I'm
not
sure
whether
you
would
consider
having
the
jenkinsfeld
runner
plugin
in
the
extension
pack,
because
I
think
that
it's
not
a
good
use
case.
But
maybe
at
some
point
too.
A
I
mean
it
would
certain
certainly
be
interesting
in
the
visual
studio
code
api
for
testing.
I
don't
have
a
thing
up
right
now
here
that
is
running
debug.
No,
that's
not
testing.
Usually
there's
like
the
testing.
There's
like
usually
a
like
a
beaker
like
a
scientific
beaker
here
that
represents
testing
and
they
actually
let
you
show
test
status
like
in
here
in
the
gutter.
A
They
call
it
over
here
where
the
lines
are
so
there's
lots
of
cool
things
that
can
be
done
around
testing,
and
I
know
you
kind
of
outlined
some
rough
steps
to
get
jenkins
file
runner
into
visual
studio
code.
You
were
talking
about
some
kind
of
java
thing
that
lets
you
package
java
as
like
a
standalone
binary
and
things
like
that.
A
Yeah,
I
think
that
would
be
really
interesting.
I
think
the
problem
goes
back
to
plugins
in
shared
libraries,
so
there
would
have
to
be
some
kind
of
setup
in
my
repo
so
that
we
can
install
the
right,
plugins
and
the
right
shared
library
into
the
runner
so
that
when
I'm
in
this
file
you
know
I
can
pull
up
a
command
and
say
like
run
file,
run
jenkins
file
and
it
will
execute
it.
C
D
So
testing
testing,
jenkins
files
and
pipeline
libraries
is
still
I
I
don't
know
if
I
should
say
it's
still
an
unsolved
problem
because
there's
different
ways
of
doing
it,
but
having
a,
I
guess,
expedient
way
or
streamlined
way
of
doing
it
is
not
it's
still.
The
holy
grail.
A
If
we're
talking
about
the
job,
I
mean
the
best
way
to
run
the
job
is
either
you
know
doing
your
developments
directly
in
the
ide
by
using
replay
or
by
using
the
jenkins
file
runner.
So,
for
instance,
I
have
all
these
jobs
that
you
see
listed
and
we
can.
We
can
test
those
pretty
easily
using
the
jeans
file
runner
to
run
those.
A
I
can
show
you
that
in
a
second
or
I
can
show
you
when
oleg
is
doing
his
presentation
on
the
jenkins
file
runner
next
and
then
the
second
thing
is
like
for
shared
libraries,
so
I
just
ran
this
job
and
you
can
see
it
says
you
know
hello
from
bash,
echoing
that
using
the
shell
step.
A
A
D
And
how
is
that?
Is
that
part
of
I'm
I'm
not
I'm
not
following.
I
guess
I've
missed
I've
been
away
for
too
long.
So
I'm
I've
missed
how
that
all
gets
set
up.
A
A
Right
so
there's
the
legacy,
scm,
retrieval
message
and
I'm
using
the
file
system
plugin
and
then
so.
It's
actually
loading
the
code
from
here,
and
so
when
I
change
that
file,
it's
in
a
subdirectory
of
this
repo
and
then
what
the
plugin
does
is
whenever
your
job
starts,
it
just
loads
every
file
up
as
if
you're
on,
like
the
master
branch
of
a
repo,
and
so
that's
how
the
change
gets
loaded
live
or
on
the
fly.
I
should
say.
A
C
A
Yes,
I
haven't
checked
it
out
either,
probably
because
very
early
on
when
I
was
looking
for
plug-ins
and
things,
like
extension,
for
visual
studio
code,
I
found
the
groovy
lint
extension,
but
I
will
definitely
check
this
out.
I
believe
this
uses,
like
a
built-in
linter
to
jenkins
right.
The
jenkins
engine
have
a
lumpkin.
C
Yes,
so
it
connects
to
linter
on
jenkins
and
verifies
that,
so
the
main
downside
is
that
it
supports
on
the
declarative
pipeline.
Hence
it
hasn't
been
much
of
a
use
for
me
personally,
but
yeah.
I
was
able
to
get
it
running
just
for
the
demo
on
tuesday.
C
A
It's
very
popular
77000
installs
is
a
lot.
No,
I
think
yeah
same
here
I
mainly
use.
I
I
only
use
scripted.
I
don't
know
the
declarative
pipeline
syntax
that
well,
but
I
don't
think
the
declarative
syntax
would
work
very
well
with
groovy
lint,
so
definitely
if
you're
using
declarative.
This
seems
like
the
way
to
go.