►
From YouTube: Essentials: Open Planning Meeting (2018-05-21)
Description
This is a weekly meeting to discuss the progress and plan for Jenkins Essentials, an automatically updated Jenkins distribution.
Find us on GitHub: https://github.com/jenkins-infra/evergreen
Join our Gitter chat: https://gitter.im/jenkins-infra/evergreen
Jira board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=406
A
A
So
Batista's
out
so
Batista
and
I,
don't
really
have
stuff
that
we
can
discuss
if
he's
not
here,
so
I'll
have
to
catch
up
with
him
tomorrow
on
some
of
the
the
error
telemetry
stuff
I
just
wanted
to
give
a
quick
update
on
my
site
and
Jesse
I
know
I'm
behind
on
giving
you
an
example.
You
know
y'know
this
prototype
output
format.
That's
on
my
plate
today
now
that
I'm
finally
back
at
the
office.
Yes,.
A
A
C
A
Although
you're
there
things
that
I'm,
if
aside
from
from
this
ticket,
which
we
have
some,
we
might
have
some
overlap
on
whether
I
don't
see
things
here
that
are
related
to
you.
Are
there
things
that
I
should
be
in
keep
in
mind
when
batiste
and
I
get
started
tomorrow,.
B
B
So
this
is
one
thing
which
would
be
really
helpful
because
currently
break
the
base
and
successful
in
many
kisses.
Catcher
and
I
also
have
an
action
item
on
my
site
to
improve
packaging
of
the
course,
because
currently
there
are
issues
with
cost
loading
when
you
run
the
current
quarter.
In
my
take
the
comment
or
why
you're
going
to
be
revealed
into
the
portion
set
of
question
Josh
awkward
delivering
it
may
be
in
a
few
weeks,
but
yeah,
the
existing
food
requests
should
work
fine,
even
with
the
current
bit
of
GDP.
B
The
problem
is
with
installation
full,
so
in
ETS
you
can
say
that
a
particular
player
test
requires
the
plug-in
to
be
full
and
we
get
into
issue
because
custom
work
packages
we
already
said
use
the
word
file
which
oppose
this
plug-in,
and
it
means
that,
if
you're,
installing
new
version
just
due
to
dependent
yeah
whatever
you
need
to
devote
to
changes,
otherwise
it
won't
work.
And
although
he
should
sell
for
certain
budget
which
allows
Clinton
ended,
we
integration
in
pipeline
library
in
order
to
do
this
project
by
default.
D
And
be
really
helpful
and
roll
you
and
you
created
a
whole
bunch
of
tickets.
Yeah.
E
Yeah,
can
you
hear
me?
Yes,
we
can
okay,
so
basically,
for
the
quality
bar
I
have
impression
that
a
piece
of
the
ad
I
was
like
test
coverage
pink
or
something
a
that
is
a
little
bit
more.
So
it's
just
a
list
of
tasks
that
need
to
be
done
before
saying:
okay,
it's
safe
to
release,
so
we
have
created
a
track
for
that
and
I
have
created
tickets
for
every
task,
and
now,
with
a
page
that
lists
all
of
them.
E
So
you
can
have
a
very
quick
intro
to
the
current
status
and
all
the
tickles.
You
are
seeing
the
related
to
one
of
the
tasks
in
the
quality
where
I
have
created
so
I'm,
not
sure
which
one
assigned
those
tasks
at
this
moment.
I
think
this
is
something
to
decide
and
I
am
NOT,
also
not
sure
about
the
timing.
There
are
three
tasks
that
I
understand
are
mandatory
and
others
that
are
good
to
have.
Oh,
that
is
a
reason.
I
have
created
all
these
tickets.
I
have
put
them
on
my
someone.
E
A
E
E
E
It's
think
eternity
get
it.
Let
me
see
yeah
that
was
so.
That
is
a
draft
of
a
quality
bar
the
same
way
we
have
been
doing
and
they,
as
you
can
see,
that
has
are
more
like
anything's
and
the
tippet
are
just
track.
The
progress
of
them
so
take
a
look,
create
the
tickets,
and
if
and
if
you
got
to
do
my
one
all
all
of
this
is
obviously
open
to
discussion.
E
A
A
E
A
E
A
All
again,
I
sort
of
briefly
mentioned
it
and
get
her
just
before
this,
but
the
the
biggest
concern
that
I
have
and
just
to
give
you
a
summary
of
thread
is
I
was
thinking
about
backwards.
Compatibility
of
the
configuration
is
code
llamo
that
we
rely
on
and
how
we
would
know
from
one
version
of
a
plug-in
or
another
where
there
are
configuration,
fields
were
still
applicable
and
still
valid,
and
so
I
don't
know.
If
this
is
the
opinion
of
one
of
the
developers.
B
A
B
A
E
I'm
going
to
take
a
look
at
the
bridge,
I'm
thinking,
I
am
so
duty.
I
agree
with
you
see
here.
We
need
to
do
that
check
before
they
update
it.
I
think
it's
easy
to
check
on
P
on
a
periodic
basis.
We
can
use
the
custom
waka
here
and
try
to
to
Bill
Watterson's
and
after
that
188
or
even
PCT,
because
now
we
can
do
some
custom
work
for
the
j-th.
A
What
I'm,
what
I'm
most
interested
in
is
where,
where
we
can
apply
the
easiest
level
of
testing
just
because
I
think
like
if,
if
we're
relying
on
health
checks,
that's
a
little
bit
further
away
from
the
developer.
Making
the
change!
I
guess
then
then
I
would
like,
but
ACH
is
really
really
heavy
weight
and
I
understand
that
I
just
I
wanted
to
sister
to
defer
to
you
role
for
where
we
could,
where
we
could
add
testing,
to
make
sure
that
our
configs
are
correct.
C
I
mean
again
that
depends
on
whether
you're
considering
user
configurations
all
the
way
things
that
are
baked
into
the
essentials
itself,
but
in
general
I
think
we'll
assume
that
users
will
have
the
runs
declarative
configurations
in
place,
and
we
can't
know
exactly
what
they
might
have
configured
and
they
might
have
configured
fairly
exotic
features
and
plugins.
We
don't
pay
that
much
attention
to
so
I
think
we
just
need
to.
C
It
seems
most
straightforward
just
to
include
this
as
part
of
a
health
check,
although
I
mean
we
can
also,
you
know,
have
static
analysis
kinds
of
tests
that
cover
very
central
configuration
they
suppose
there's
generate
like
we
could
generate
an
example
configuration
using
some
earlier
snapshot,
and
then
you
know
check
whether
it
still
applies
after
some
of
day
or
something.
And
if
we
see
problems,
then.
A
So
we're
gonna
have
will
have
the
the
primary
configuration,
which
will
be
the
same
for
every
instance
provided
by
Jenkins
essentials,
but
there
may
be,
as
always,
pointing
out.
Users
may
also
add
their
own
yamo
based
configuration
I'm
less
concerned
about
that,
because
it's
sort
of
a
right
now,
there's
no
users.
First
of
all,
but
there's
it's
sort
of
infinite
possibility.
There.
B
E
B
C
Yeah
I
just
went.
They
just
want
to
point
out
that
configuration
is
code
plug-in
skips
over
in
applicable
configuration
sections,
but
logs
are
warning
about
them
the
system
log.
Then
we
don't
need
to
do
any
custom
development
for
this.
It
would
just
show
up
from
a
completely
generic
test
that
asserts
that
a
stock
essentials
instance
starts
up
without
warnings
for
the
same
for
the
upgrade
check.
If
your
upgrade
check
says
warning
forces
to
cancel
the
upgrade,
then.
B
Hit
counter
the
computation
is
cadenza
is
not
flexible
enough.
If
you
add
an
optional
see,
you
know
stairway
wait,
so
we
all
have
a
date
about
constructor.
You
have
been
used
to
duplicate
all
constructed,
create
a
new
one.
So
after
this
configuration
is
code,
plug-in
stops
working
for
you
and
it
happens
for
some
critical
to
already
2.16.
B
B
B
A
C
I
should
mention
that
I
just
recently
did
a
change
to
pipeline
step,
which
involves
compatibly
changing
the
groovy
form
by
which
this
step
may
be
invoked
without
touching
the
stapler
binding,
which
is
what
you'd
see
in
UI,
or
something
like
that.
That's
possible,
because
the
pipeline
API
is
defined,
an
abstraction
layer
which
you
can
override
for
them
finding
as
far
as
I
know,
I'm,
not
clear
or
whether
there
is
a
comparable
future
in
configurations.
We
know
there's
some
sort
of
custom
binding
mechanism,
it's
practical
to
use
the
other
than
the.