►
A
C
C
So
since
the
last
office
hours
we've
had
two
releases,
1.21
and
1.22
I
think
1.21.
There
was
no
user
facing
changes,
but
there
was
for
anyone
using
the
EMH
benchmarks.
Support
was
added
two
people,
depending
on
the
configuration
of
code
plugin
to
configure
jmh
benchmarks,
using
configuration
as
code
and
in
1.22
there
was
a
few
fixes,
so
lisa
started
the
blog
to
the
meeting
notes
of
how
to
do
the
jmh,
pin,
tucks
and
1.22.
C
C
Here
we
go
expected
names
of
parameters,
expected
type
of
parameters
and
I
think
that's
now
been
combined
in
line
as
well.
Hopefully
that
makes
it
easier
for
users
we've
also
added
some
support
for
I,
think
subclass
field.
So
we
had
two
on
the
descriptor,
so
get
plug-in
ahead
was
doing
this
and
there
was
grout.
C
You
can
add
browsers
to
the
get
plug-in
in
some
way,
and
that's
now
supported
thanks
to
Oleg
had
some
demo
fixes
for
the
ec2
plugin,
which
is
now
compatible
again,
and
we
have
a
test
now
pass
with
Windows
again
as
we
don't
we're,
not
testing
every
build
on
Windows
because
of
the
Jenkins
infrastructure
windows
tests.
The
windows
structure
is
a
lot
slower
and
not
as
reliable,
and
we
had
a
lot
of
issues
with
us,
so
we
don't
test
continuously.
So
every
now
and
then
issues
are
introduced.
C
So
that's
that's
something
that's
used
for
the
UI
which
was
being
exported
and
it
was
preventing
you
from
be
able
to
export
your
config
and
then
import
it
again
without
any
modifications.
So
now,
in
a
lot
of
cases,
you
should
be
able
to
export
your
configuration
and
INRI
important
and
it
should
work
previously
before
this
change.
It
wasn't
possible.
We've
also
added
a
a
black
listing
method
inside
of
the
plugin
for
now,
which
you
can
add
to.
If
you
don't
want
certain.
C
To
the
one
that
we
had,
the
one
that
we
have
like
this
is
currently
is
default:
properties
on
hudson
tools
to
property,
we're
open
to
extending
this,
to
making
it
sir
plugins
key
and
contribute
it
themselves.
But
we
just
need
to
say
that
there's
a
need
wouldn't
be
too
much
of
a
change
given
that
and
give
200.
C
The
similar
has
a
similar
sort
of
functionality
and
we
may
move,
and
we
are
looking
into
removing
the
we
currently
have
a
restricted
annotation
which
isn't
really
meant
for
us
to
use.
But
currently
we
ignore
anything,
that's
restricted
and
we're
looking
at
removing
that
behaviour
requested
by
a
couple
of
users
and
then
using
the
blacklist
functionality
instead,
but
that's
ongoing
work
that
will
look
into
soon.
Hopefully,
I
think
that's
all
from
the
release
updates
unless
anyone's
got
anything.
To
add
on
that.
A
Easy
to
plug
in
in
which
was
normal
to
dimension.
Now
it's
compatible
with
Jake
asked
so
few
bucks
fix
today
and
released.
Then
in
each
plug-in.
We
now
have
support
of
sub
module
definitions.
They
still
waiting
for
the
final
release,
but
it
should
land
soon
and
yeah.
There
is
a
lot
of
other
politically
switch
staged,
for
example,
log
Parcells
plugin
requested
by
joseph
try
to
conquer
it.
It's
also
staged
for
the
release,
so
yeah,
maybe
for
the
next
meeting.
It
makes
sense
to
just
put
a
list
of
such
new
integrations
yeah.
C
C
A
Chase
sub
projects,
which
means
that
it's
Jake
asked
but
the
sample
every
day
all
Italy
needs
some
purchase
for
conformance
testing,
because
system
and
Natasha
is
also
interested
in
today.
20
manager
so
still
really
have
a
lot
of
activities
related
to
Jae,
Seok,
Jake
asked
and
ingenious
of
projects
all.
B
D
Yeah
sure
so,
as
I
discussed
with
Oleg
I
think
we
we
thought
about
I,
actually
read
the
community
bridge
kind
of
application
form
that
was
there
and
Oleg
said
that
you
could
apply
there
formally
and
they
had
a
ji-suk
g-dcast.
They
had
all
of
the
I
mean
all
of
the
configuration
ready
to
actually
under
extort
this
project.
So
no,
he
told
me
to
pick
you
guys
on
the
channel
and
take
some
beginner
will
request.
A
A
caddy,
so
maybe
it
makes
sense
to
open
if
introduced
from
in
generation.
Actually
this
is
Jesus
offers
a
service
program
in
Iran
by
a
Linux
Foundation
Jenkins
project
moved
to
continuous
delivery
foundation
and
continuous
delivery
foundation
is
a
part
of
Phoenix
foundation.
So,
basically
we
get
access
to
this
platform
and
we
can
use
it
for
our
projects
yeah
one
months
ago.
So
there
was
a
discussion
at
that
box
and
all
three
she
seek
meetings
about
using
the
platform.
You
have
created,
stop
project
today
and
yeah.
A
A
The
vocational
cliche
meeting
recordings
to
be
published
so
I
cannot
refer
anything
specific
and
yeah.
If
you
want
I
can
just
screen,
share
and
show
this
problem,
but
yeah.
Basically,
nothing
is
really
settled
to
there.
So
we
just
have
opened
a
way
to
apply,
and
yet
we
don't
have
strictly
defined
process
and
strictly
defined
timelines.
C
D
I
mean
anything
that
you
guys,
if
you
guys
have
any
project
in
mind
of
regarding
asked
I,
would
love
to
take.
Maybe
we
could
set
up,
maybe
I'll
get
a
channel
or
something
where
we
could
just
focus
on
this.
A
particular
project
like
this
I'm
this
system
just
beginning
to
solve
some
issues,
I'm
getting
a
feel
of
it.
So
if
you
guys
have
any
any
sort
of
a
specific
project
that
you
want
one
to
undertake,
we
could
actually
iron
out
the
details.
F
D
C
C
Yeah
I
mean
for
us
it's
really
what
you're
interested
and
working
on.
Certainly
so,
certainly
some
nice
missing
features
around
the
IDE
and
the
schema.
That
would
be
quite
nice
to
fix,
fix
and
enhance,
because
the
schema
doesn't
really
work
properly
right
now,
so
you
can't
validate,
and
you
can't
you
can't
use
a
JSON
schema
or
IDE
auto-completion
will
be
quite
nice.
D
C
A
Yeah,
yes,
oh
if
you
want
to
have
a
bigger
problem
statement,
so
what
came
was
a
reference
in?
It
would
be
integration,
development
tools.
We
have
development
tools,
sorry
integrations
that
may
be
of
inundation.
It
might
be,
for
example,
a
Jenkins
pipeline
step,
so
whatever
we
should
be
able
to
unify
that,
so
that
somebody
could.
A
Whatever
integrations
with
new
features,
for
example,
we
yuffie
was
interested
in
adding
support
of
providing
configuration,
is
not
from
file
system
but
from
a
stream
and
then
would
they
also
require
some
architecture.
Changes
put
some
extension
porn
site
additional
providers.
So,
if
you're
interested
in
such
work,
it
could
build
stable,
yeah.
D
E
A
D
D
D
A
D
A
Financial
side,
so
jisub
students,
a
bit
is
depend,
and
you
know
invoke,
we
see
and
the
outreach
special
interest
group
about
having
a
kind
of
step
and
for
community
bridge
participants
so
right
now
it's
not,
but
initial
do
so
so
I
would
be
just
interested
to
know.
What
is
your
expectation
so
that
I.
D
D
A
A
E
E
E
B
D
A
A
G
Yeah
so
I
just
kind
of
wanted
to
see
I
guess,
I
kind
of
how
this
would
fit
into
configuration
is
code
and
trying
to
better
understand
like
how
those
two
will
fit
together
and
then
click
yeah.
How
I
can
configure
like
my
project
to
fit
in?
What's
existing
and
I?
Guess
like
how
configuration
is
code
would
want
to
use
the
plug-in
library.
G
Hello,
did
you
okay,
so
I
don't
know
if
you
caught
that
I
guess
so,
maybe
just
for
like
this
is
kind
of
just
like
really
basic
stuff,
but
like
so
I
guess,
like
first
question
is
like
like
how
would
like
configuration
is
code
want
to
use
my
the
plug-in
library
and
then
I
know
that
this
was
kind
of
done
before,
but
there
were
some
issues
so
I
just
want
to
try
to
understand
that
better.
So
it's
wondering
if
you
guys
could
explain
that
a
little
in
a
little
bit
more
detail
so.
C
I
can
say
what
the
problem
with
the
previous
implantation
implementation
was
was
two
problems
with
it.
One
was
that
there
was
no
guarantee
that
the
plugin
would
be
installed
before
the
configuration
was
loaded
that
required
it
and
the
other
one
was
that
sometimes
it
needed
to
be
a
restart
when
plugins
were
installed
and.
F
A
There
are
multiple
issues
with
it.
Basically,
there
are
many
ways
that
is
alteration
for
installing
a
new
plug-in,
but
the
real
problem
starts
with
a
beating
plugins,
because,
firstly,
you
cannot
update
plug-in
without
restart
and
always
just
referenced
by
Tim
and
Rosa,
and
if
you
restart
there
is
no
guarantee
that
the
instance
will
start
up
at
all
after
flying
the
webpage,
because
Jake
ass
doesn't
verify
that.
A
So,
unless
you
have
whatever
automatic
disaster
recovery,
integrated
updating,
plugins,
wedging
durations
code
is
pretty
complicated
and
what
we
were
talking
about,
the
decision
for
the
tickets.
Actually,
the
consensus
was
that,
instead
of
doing
it
by
a
plug-in,
we
would
rather
do
it
over
a
library
because
in
Jenkins
it's
here,
it's
possible
to
inject
a
library
which
works
on
whether
startup
and
does
something.
For
example,
we
could
inject
it
using
customer
packager
and
doing
its
authorization
of
plugins
before
Jenkins
even
starts.
We
begin
building
group.
G
I
think
so,
and
then
so
like
right
now,
I
guess,
like
my
understanding
of
current,
like
current
functionality
and
core,
is
like
there's
sort
of
two
steps.
It's
like
a
the
plugins
have
to
be
downloaded
and
then
B
they
have
to
be
installed
or
they
so
like
I
think
right
now
like
right
now.
Basically
what
the
library
does
is
it
just
downloads
them?
So
is
this
something
where
like
it
would
also
have
to
install
them,
or
that
would
just
be.
A
The
existing
code,
okay,
yeah,
what
would
could
we
really
do?
We
could
just
make
the
library
or
a
part
of
Jenkins
core,
so
I'm,
not
sure
whether
other
contributors
would
agree
with
that.
But
basically
we
could
inject
support
of
plug-in
walking
directly
into
Jenkins,
or
it's
not
a
problem
to
do
it
for
docker
images,
for
example,
because
product
images
it's
much
more
trivial.
So
now
install
plugins
SH
words
only
when
you
build
the
image,
but
basically
you
can
invoke
with
a
script
or
your
tool.
A
So
for
me,
the
best
way
to
get
Jake
asked
integrated.
This
plug-in
management
is
to
not
do
any
changes
on
the
Jake
asked
plug
inside,
but
implement
would
have
a
library
which
can
read
from
Jenkins
llamo
and
which
installs
the
plug-in
according
to
that
when
Jake
starts
up.
So
basically
you
already
support
plugins
60.
If
you
had
support
off
Jenkins
llamo
as
an
input
and
if
we
can
ensure
that
well
basically,
we
can
then
use
a
single
llamo
definition,
so
it
will
be
read
in
two
places:
okay,
I
see.
A
A
There
was
a
pull
request
by
a
con
secured
at
some
point
to
have
pluggable
core
components.
So
basically
the
idea
was
to
be
able
to
load
for
companies
like
step
origins,
remoting
from
a
flag,
even
though
there
was
a
prototype
for
that.
But
this
prototype
has
never
been
completed
and
integrated,
but
hey.
If
we
had
this
prototype
in
the
course
we
could
have
done
something
like
that
from
plugin.
Codebase,
basically
does
exactly
the
same
as
just
injecting
library.
A
G
A
G
Ok,
I
I
think
right
now,
so
that
my
main
focus
at
least
like
for
the
like
most
immediate
features,
just
getting
things
working
with
soccer,
but
I'm
just
trying
to
kind
of
figure
out.
You
know
what's
next
in
the
pipeline,
so
I
don't
know.
Maybe
we
can
talk
a
little
bit
more
about
like
kind
of
some
of
those
options
when
I
actually
start
trying
to
work
on
that.
A
It
sounds
totally
right
and
yeah,
so,
basically,
once
you
have
something
working,
a
full
plugin
manager,
maybe
it
makes
sense
to
create
sample
repository
where
you
use
your
configuration
tool
to
manage
plugins
and
J
cast
plugins
to
manage
configurations,
and
then
you
can
use
this
repository
to
incrementally
do
changes
and
make
them
closer
together.
So
it
will
be
a
kind
of
reference
implementation
for
using
tools.
Then
all
indications
can
be
just
showcased
today.