►
Description
Regular project meeting in the Jenkins Configuration as Code subproject: System Read permissions, Plugin Bill of Materials etc. Full agenda and meeting notes: https://docs.google.com/document/d/1Hm07Q1egWL6VVAqNgu27bcMnqNZhYJmXKRvknVw4Y84/edit#heading=h.jek9n5l0w6g1
A
Well,
welcome
to
the
regular
agenda.
Configuration
is
called
Project
meeting
today's
many
six
and
we
just
run
the
common
agenda.
We
will
talk
about
news
about
Jake,
asked
releases
and
fighting
ability
fixes
and
then
everything
about
ongoing
development
and
other
project
stories.
So
we
have
four
participants
on
the
call:
it's
John
team
organ
and
me
yeah.
Unless
there
are
more
topics
to
the
agenda,
I
suggest
to
just
go
through
these
ones.
Actually,
I
have
one.
A
A
Guess
the
current
version
is
1.39
right,
so
yeah.
Basically,
we
had
known
since
there
was
meeting,
though
there
are
some
ongoing
changes
from
what
I
see
if
finally
integrated
bomb,
all
those
zero
into
the
plug-in
yeah
thanks
what
came
for
makin
today,
a
bill
of
materials
integration
in
place?
Guess
we
will
still
need
to
integrate
this
fashion.
A
A
Okay,
it
was
a
quite
solid
week
and
some
people
busy
with
google
Summer
of
Code
other
people.
We
were
just
pulling
corrilesa
donation
and
someone
going
so
yeah.
Regarding
ongoing
development.
We
had
a
bunch
of
stories
they
discussed
at
the
last
meeting,
so
I
guess
all
of
them
are
still
going
on
so
bill
of
materials
system,
Reclamation's.
A
B
A
Well,
I
think
that
so
we
still
got
a
number
of
changes
in
this
week,
so
why
it's
important
that
this
weekly
dislike,
giving
you
LCS
baseline
but
yeah.
You
just
keep
working
on
this
and
other
changes
in
the
next
three
leaders.
There
is
still
a
lot
of
things.
We
could
do
what
enhance
system
written
permission,
and
this
is
actually
one
of
the
reasons
why
I
brought
up
the
your
aux
online
hackathon
and
because
it's
our
back
unity
to
facilitate
some
contributions
around
this
story.
A
So
long
story
short,
we
would
like
to
have
online
hug
fest
in
wait
me
so
tenderly,
starting
on
May
25th
and
it's
likely
to
be
a
five-day
event
or
maybe
new
olive
oil
over
the
weekend.
So
it
would
be
seven
or
eight
days.
The
idea
is
to
facilitate
contributions
around
user
experience,
so
what
it
means:
user
interface,
user
documentation
and
also
connecting
success
stories
both
from
Jenkins
users
and
share
their
experiences.
So
there
is
a
proposal
in
the
developer
mind
increased
about
that.
A
And
my
interesting
question
is
with
stories
we
could
address
and
for
me
one
of
the
interesting
stories.
Configurational
scott
is,
of
course
read-only
interface.
So
it's
not
read
on
the
interface
for
system
configurations
and
also
for
job
configurations.
So
one
of
the
changes
team
did
one
months
ago.
He
applied
the
same
job
to
to--for
engine
to
job
configurations,
and
actually
we
could
continue
working
on
this
topic.
A
A
A
B
A
Jealous
and
yeah
another
story
which
was
recently
well
revealed
by
a
Daniel
bag
and
King,
is
extended,
read
for
agents
because
yeah
technically
we
have
support
of
that
inside
the
Bujinkan
score,
but
yeah
as
far
as
I
know.
Nobody
has
ever
used
to
that.
We
have
extended
free
plug
in
and
he
also
doesn't
enable
this
admission.
So
yeah.
A
Yeah
so
most
likely
it
doesn't
work
almost
like
it's
Pandora
boats,
but
if
somebody
is
willing
to
test
that
and
maybe
get
it
fixed,
it
would
be
also
nice.
So
the
reason
is
not
permanent
agents.
It's
quite
rare
that
people
have
access
the
configuration
without
being
able
to
them
to
do
it,
but
for
cloud
agents
it
would
totally
make
sense.
A
A
A
A
A
Sleepy
changes
thing,
so
the
next
story
is
Bill
of
Materials
I
just
checked
this
morning.
We
still
have
a
pull
request
with
Jenga
configuration
as
code
plug-in
update
this
one
and
my
understanding
that
they
still
blocked
by
Jake
asked
test
harness
the
dependencies
and
other
fun
stuff.
Hysterectomy
yeah.
B
A
Yeah
you
briefly
discussed
at
the
last
meeting.
I
was
thinking
about
doing
so
we
will
need
to
fix
a
flag
in
compatibility
tester.
So
it's
the
development
utility
which
verifies
flag,
incompatibility
and
I
guess.
The
main
problem
for
us
is
to
have
the
operations
code
test
harness
manageable
this
PCT,
and
in
order
to
do
so,
we
will
likely
need
to
include
it
in
tagging
pom.
So
this
part
is
doable
and
I'm
here
to
help
with
it,
but
the
resource
a
separate
part.
A
We
will
need
to
update
all
plugins,
which
explicitly
include
dinkus,
sorry
Jocasta,
test
harness.
We
will
need
help
on
delayed
them
to
the
new
plug-in
phone
version
and
begins
that
we
will
need
a
table
rhythm
to
photo
zero.
So
I
just
wanted
to
have
a
sanity
check,
whether
it's
possible,
whether
we're
ready
to
invest
time
in
that
I.
B
A
So
assuming
that
Jake
asked
us
humus
is
stable
enough
so
that
the
library
can
test
multiple
versions
of
Dicker's
plugin.
It
should
be,
it
should
work.
Well,
it's
basically
the
same.
We
hit
with
Jenkins
harness
eight
years
ago,
or
so
because
originally
it
was
also
highly
tied
to
Chinese
corporations.
But
now
you
can
use
Jenkins
test
harness
use,
multiple
core
versions
and
the
wrench
is
actually
pretty
wide.
Yeah.
B
And
I
think
I
think
this
is
just
quite
a
special
case
really.
It
could
also
be
fixed
by
just
changing
scope
babe.
If
we
release
to
back
a
back
ported
version
with
the
slake
gem
will
change
and
then
bumping
script
security
to
use
that
version
it
just
needs
to
be.
Have
it
just
needs
a
version
of
jks.
That's
compatible
a
snake
general
API,
plug-in.
B
C
Good
way
to
do
it
is
to
split
the
two
things
as
apart,
because
there's
no
and
I
know
we're
using
it
for
test
sources
ourselves,
but
what
we
could
probably
do
is
spit
it
out
so
that
the
Honus
is
it
separated
out
there
so
separate
release,
so
they
don't
follow
inversions.
We
don't
really
change
the
source
that
much
well.
C
A
Harness
right
hand,
side
jenkins,
test
harness,
because
why
not
we
all?
We
already
had
some
cases
of
it
when
you
know
at
all
strategic
performance
so
which
play
jenkins
test
harness
include
some
extensibility
engine
which
can
be
extended
by
Rodriquez
plugin
for
doing
benchmarking
of
plugins.
And
theoretically,
we
already
depend
on
some
plugins
here.
A
C
B
Yeah,
we
might
need
a
separate
test
package
for
us
created
because
I
think
I
think
we
have
a
number
of
tests
inside
of
the
test
harness
module
which,
because
of
because
we're
testing
stuff
that
requires
the
test
harness
functionality.
But
we
don't.
We
don't
want
circular
dependencies
inside
of
our
card,
because
test
harness
depends
on
Jake
asked,
so
we
might
need
iron
test
module,
which
depends
on
chef,
Donna's,
okay,.
A
It's
a
separate
repository
because
in
such
case
you
would
also
have
separate
release
cycle
and
we
also
have
dependent
boat
or
whatever
picking
it
up,
yeah,
so
yeah
we
could
convert
Genesis
harness
to
mod
model
repository
but
and
I.
Don't
think
we
would
improve
situation
a
lot.
So
if
we
really
cannot
avoid
circle
dependencies
then
separate
model
I.
B
C
A
A
B
A
A
A
B
A
Okay,
maybe
I
check
so
I.
Think,
let's
see
I
wanted
to
discuss
switches.
Can
you
zoom
account
so
just
to
clarify
retinal,
we
use
an
experimental
ACDF
zoom
account,
but
we
got
a
separate
one
for
the
junkies
project
and
I'm
currently
working
on
photos
updates.
So
we
can
give
project
either
sick
readers
access
to
the
zoom
account
which
case
we
want
to
need.
A
A
So
yeah,
maybe
a
quick
update
from
me,
so
we
have
to
go
to
number
of
employ
Summer
of
Code
projects
announced
just
on
Monday
and
there
were
some
projects
which
actually
related
to
James
configuration
s
code.
For
example
Laden.
He
was
our
community
breach.
Monkey
working
on
J
cast
their
tools.
At
least
someone
here
is
bill.
He
will
be
working
on
a
custom
and
Jenkins
distribution
bill
service,
so
a
service
which
allows
to
define
the
configuration,
including
Jake,
asked,
and
you
ready
to
file
a
images
or
don't
get
forward
files.
A
So
basically,
like
customer
packaging
works,
but
they
share.
It
will
be
some
changes
to
like
to
Jake
asked
there,
and
also
there
are
other
projects
that,
in
their
prints,
github
checks,
APA
machine
learning,
which
you
like
encode
some
level
of
geographically
the
changes
there
may
be
more
so
maybe
some
you
like
to
get
some
contributions,
and
maybe
even
a
more
optimistic
topic
is
about
Jenkins
Windows
services
llamo,
because
once
we
switch
to
llamo,
we
will
be
able
to
use
the
same
Jenkins
remote
contribute,
there's
a
service.