►
From YouTube: Essentials: Open Planning Meeting (2018-05-14)
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
Guess
we
might
as
well
get
going
on
this
a
couple
things
that
I
wanted
to
accomplish
today,
just
because
I've
been
a
bit
out
of
the
loop
with
some
events
yesterday.
A
Who
was
that?
It's
that
he
said
just
making
noise.
A
So
I
just
wanted
to
go
over
quickly,
really
just
for
my
benefit.
More
than
yellow,
since
y'all
are
all
around
last
week
when
I
wasn't
just
where
some
things
are.
I
wanted
to
catch
up
on
where
the
Bill
of
Materials
discussion
was
and
then
just
towards
the
end.
Batiste
I
wanted
to
talk
about
that
that
update
levels
pull
request,
number
70,
and
if
we
can,
if
we
can
get
some
time,
then
so
maybe
Raul
do
you
want
to
go
ahead
and
start
like
how's
the
house,
the
a
th
in
PCT,
Python
library,
stuff
coming
home.
B
Yes,
so
if
I
can
everybody's
already
able
to
run
PCT,
it's
without
problems
all
the
custom,
an
incredible
job,
a
christineanne
essentials,
test
step,
which
basically
runs
everything
and
now
I
am
implementing
that
on
the
plane
I'm
having
some
issues,
because
some
implementations
are
not
yet
a
fully
functional.
For
example,
I
need
to
a
customer
to
be
able
to
install
blue
ballons,
which
is
some
of
the
plugins
we
want
to
run
forward.
Get
a
I
have
also
find
that
the
dr.
P
city
image
is
not
honoring.
B
A
B
B
C
B
I
will
be
very
happy
to
close
this,
so
if
this
is
my
fellow
which
is
important,
probable,
then
are
some
things
that
we
need
to
roll
to
fix.
For
finish,
the
heat
flow
I
mean
a
complete
flow
with
custom
work
package
era
and
all
the
things
which
is
there
are
some
plugins
like
pick
up
that
don't
pass
the
visiting
at
this
moment.
A
D
B
B
A
C
One
interesting
topic
is
essential
space,
and
so
we
have
utility
meters
in
Python
library
which
allows
running
to
was
packaged,
FCC
key
and
then
harness
in
a
single
phone
and
I
have
already
created
a
bunch
of
food
requests
for
two
different
sizes.
It
orbits
like
a
Jenkins
death
layers
of
platinum
interest,
free
plugin,
not
this
one
essential
stuff
is
already
in
the
new
array,
so
you
can
just
open.
C
Yeah,
what
everything
does
is
actually
Terry
run
integration
test
in
a
single
flow,
so
within
their
own
great,
with
run
cgpm
running
in
each
created
by
a
dog
and
the
it
consumes
essentials,
a
llamo
as
a
single
input.
You
can
define
everything
in
a
single
file
and
just
second
I
will
provide
an
example.
One
of
our
main
components,
for
example,
was
subset.
Integration
system
and
I
have
created
a
pull
request
for
this.
Using
to
this
essential
stressful,
we
have
written
getting
to
the
church.
A
C
C
C
A
C
So
you
Needham
what
would
be
she's
also
in
life,
but
the
omen
spot-check
tetran,
which
takes
something
like
20
minutes.
If
we
were
able
to
realize
watches
that
would
be
much
more
effective,
but
the
air.
Currently
we
can
switch
Piketty
and
the
heat
you
just
go
change.
Why
militants
are
being
rounded.
C
A
Know
the
faster
more
readily
applicable
tests
moving
to
the
front
of
our
pipelines
and
then
getting
you
know
going
up
that
testing
pyramid
to
our
smaller
suite
of
acceptance,
tests
that
take
a
long
time.
Those
should
be
last
so
that
if
there
is
going
to
be
a
failure,
we
don't
spend
so
much
time
running.
F
In
the
case
of
yeah,
in
the
case
of
core
not
sure
what
you're
looking
at
here,
I
think
this
is
Corey
I
mean
in
the
case
of
core
this
one
of
the
slowest
things
is
actually
the
functional
tests
in
the
core
repo,
so
I
mean
either
way
we're
going
to
have,
or
we
should
have
the
fill
fast
mode.
So
as
soon
as
you
get
some
test
failures,
just.
C
F
A
A
C
F
Yeah
by
the
way,
I'm
I
mean
sure
fire
has
some
features
to
do
things
like
run
recently
failed
test
sooner
and
stuff
like
that,
they
don't
think
it
would
work
all
that.
Well
in
this
case,
because
we
have
so
many
different
test,
Suites
with
different
infrastructures
and
so
on,
but
I
mean
we
might
need
to
spend
some
time
develop,
developing
or
finding
and
integrating
some
tools
that
try
to
predict
the
you
know
most
likely
points
of
failure
based
on
which
files
are
changed
in
the
particular
pull
request.
D
A
D
F
B
D
F
A
F
Well,
the
basics
are
pretty
much
working,
I
mean
they
I.
Think
the
interesting
things
at
this
point
are
going
to
be
around
like
the
stuff.
I
was
talking
about
and
figuring
out
exactly
what
evergreen
is
publishing
when
and
how
we
validate
those
those
things
for
pests
and
so
on.
So
that's
sort
of
higher
level
work.
D
D
Okay,
so
last
week,
I
almost
would
say
finalize
the
service
size
of
the
telemetry
era.
Telemetry
thing
and
the
jab
I
would
say,
is
now
ready.
I'm
gonna
file,
the
PR,
because
so
for
outside
people
work.
Looking
at
what
I'm
saying
yet
so
this
one
is
not
yet
filed
as
PR
as
a
PR,
because
it
was
sent
to
the
developers
mailing
list
for
feedback
and
now
I've
got
feedback
from
you
Tyler
already,
so
we
discussed
quite
a
few
things
which
I
think
I
addressed
in
every
addressed.
All
of
them.
D
If
we
push
something
like
one
terabyte
or
one
gigabyte
log,
but
that's
mostly
its
and
I
hope
to
be
able
to
really
wrap
up
that
one
soonish
and
more
than
removing
the
ich
to
switch
to
something
else
and
I
think
we
need
to
at
some
point
also
meet
to
discuss,
which
kind
of
the
point
today
or
anyway.
But
what
is
left
really
for
my
son
want
to
have
something
usable
with
it.
The.
A
You
discussed
some
of
the
fluently
work
with
Olivier
yeah,
one
of
the
one
of
the
big
questions
that
I
had
about
that
and
I.
Don't
remember
if
we
discussed
this
last
week
is
how
developers
like
Jessie,
for
example,
would
get
access
to
those
error
logs
if
we
were
passing
them
into
fluent
tea.
Have
you
given
much
thought
to
that.
D
Yes
and
no,
we
discussed
that,
but
we
didn't
come
to
a
solution
yet
because
it
seemed
like
a
bit
too
early
because
for
now
we
mostly
wanted
to
have
an
understanding
or
I
was
fronting
from
the
Evergreen
product
side.
Pretty
excited
have
an
understanding
on
how
what
was
in
place
from
various
infrastructure
in
the
Jenkins
infrastructure
cluster.
D
D
I
I
think
we
somehow
said
that
it
should
come
later
to
try
and
provide
maybe
some
dedicated
up
or
dedicating
I've
access
or
something
to
the
log
analytics
Asia
and
Asia
log
analytics
UI
or
maybe
some
front-end
to
protect
regard
to
I,
don't
know
privacy
or
something
for
that
kind
of
it.
I
think
we
have
an
epic
talking
about
the
matrix
and
and
telemetry
in
general,
which
is.
D
I
just
wrote
it
down,
but
I
guess
you
will
have
to
as
a
p.m.
as
a
product
manager
for
essentials
have
to
express
what
you
want
from
the
privacy
perspective.
Should
we
just
open
it
to
some
people,
we
know
and
trust,
or
should
it
be
available
to
more
people?
And
so
you
know,
for
instance,
should
those
people
be
allowed
and
it
would
be
okay,
that
they
see
the
existing
Jenkinson
fractured
sure
logs.
Some
of
those
or
I
really
see
only
exclusively
essentials
one,
and
so.
A
On
only
essentials,
okay
right
and
we
have
so
we
have
just
for
your
understanding.
We
have
the
LDAP
behind
the
scenes
in
our
project
infrastructure
and
we
also
have
the
ability
to
define
groups.
We
don't
take
very
strong
advantage
of
either
of
those
things
right
now
or
we
can
put
logs
somewhere
else
for
the
time
being.
I
don't
have
a
strong
opinion
right
to
me.
A
If
we,
if
we
are
not
able
to
provide
this
error
telemetry
to
Oh
like
Jesse
and
Carlos,
then
it's
almost
as
if
we
like,
we
wouldn't
have
needed
to
record
them
at
all
like
if
only
you
and
I
have
them,
and
then
we
don't
sort
of
achieve
what
we're
trying
to
achieve
with
the
visibility
for
developers.
I
can
send
send
them.
D
A
So,
as
well
was
switch
over
to
that,
so
most
of
the
work
that
I
was
doing
last
week
was
not
Jenkins
essentials.
Unfortunately,
I
was
standing
and
looking
pretty
at
a
cloudBees
booth
for
Microsoft
build
so
in
between
that
I
did
get
a
lot
of
things.
What
I
thought
were
wrapped
up,
so
this
pull
request
has
sort
of
gotten
a
little
unwieldy
due
to
my
own
time,
but
there
is
the
update
services
pushing
out
update
levels.
The
client
is
storing
it.
A
The
client
is
also
sending
it
with
its
checks
for
updates,
and
so
it's
only
updating
if
there
are
updates
available
which,
with
a1
hard-coded
set
of
updates.
That
means,
after
the
first
run
of
the
client
it's
done
but
ceased.
What
I
really
need
your
help
on
it.
I've
been
on
sort
of
low
bandwidth
connections,
most
of
the
most
of
the
week
last
week
and
I
haven't
been
able
to
really
test
the
run.
A
These
acceptance
tests
very
well
and
I've,
had
to
rely
a
little
bit
on
Jenkins
for
those
when
I
run
things
manually,
things
work
when
they
run
in
CI
or
if
I
run,
you
know
make
check
locally.
It
doesn't
seem
like
all
the
updates
are
getting
pulled
down.
The
first
thing
that
would
be
really
helpful
to
make
this
easier
is
if,
for
the
integration
test,
that
we
were
recording
the
or
saving
the
logs
that
are
coming
off
of
the
Decker
container.
D
D
Try
your
PR
this
morning
and
I
see
something
failing,
so
indeed
we
should
need
to
sustain
you
think
at
least
to
triage
beef
between
what
should
be
working
and
what
shouldn't
be
or
what
is
not
supposed
to
be
working
because,
for
instance,
this
morning,
I
was
seeing
the
client
not
able
to
connect,
because,
to
instance,
the
server
will
start
just
a
blur
after
it
just
to
be
too
late,
and
so
the
client
would
never
try
to
reconnect,
and
so
everything
would
be
failing.
Oh.
B
D
A
I
think
the
I
think
the
ordering
is
probably
in
its
it's
correct.
I'm
doing
air
quotes,
but
you
can
say
cuz
I'm
sharing
my
screen,
it's
correct,
but
yes,
it's
not
coming
up
fast
enough.
That's
certainly
a
problem.
I
expect
at
this
point
that
these
tests
should
be
working.
Yep,
music
manually
validated
that
running
the
server
and
the
client.
D
B
D
So
it's
been
fixed
in
the
meantime
and
also
I've
checked,
but
I.
Think
in
your
case
it's
already
not
the
case
anymore.
We
shouldn't
need
to
build
anything
anymore
because
everything
is
released
or
something
and
soonish
by
the
way
we
should
be
able
so
to
use
as
soon
as
the
PR
we're
talking
earlier
about
the
one
from
Jesse,
we
should
be
able
to
just
use
the
increment
source
versions
releases
for
metrics
for
essentials,
for
whatever
plug-in
we
want
to
use
it
with
I
guess
it
would
be
a
slightly
simpler.
So
why
don't
I.
A
D
B
D
A
Try
out
with
you
more
after
the
meaning,
I
think
there's
three
or
four
things
that
we've
talked
about
that
need
to
be
addressed
and
we'll
just
assign
them
to
each
other,
and
then
then
we
can
move
forward.
Let's
just
a
bother,
everybody
concerns
once
we're
once
we
have
this
pulled
down
or
merge.
These
changes
do
provide
the
basics
of
of
the
the
full
flow.
What
I
noticed
while
is
developing
this
and
level
depending
on
your
time,
I,
would
really
appreciate
your
help.
Is
we've
got
you
know.
A
A
My,
look
at
the
time
we've
kind
of
quite
long,
so
the
other
thing
that
I
know
is
is
sort
of
at
the
top
of
my
list.
If
I
it's
not
literally
at
the
top
of
my
list,
which
I
know
there
is
this
test
that
Jesse
asked
me
four
five
one,
two
fifty
or
five
one,
two
five
zero
there
seems
to
be-
and
this
is
me
segue
into
the
Bill
of
Materials
discussion.
A
The
the
format
of
stuff
that
we
need
to
ingest
for
the
update
service
looks
a
lot
like
the
update,
Center
JSON,
for
example.
I
just
need
a
list
of
URLs
and
artifact
IDs
that
sort
of
a
thing
she
I
was
gonna
sketch
out
a
file
that
would
make
sense
for
Jesse's
tool
to
output
and
as
far
as
I
can
tell
Jesse,
that's
the
only
thing
that
I'm
blocking
in
the
Bill
of
Materials
discussion
right
now
is
that
correct
or
incorrect
I.
F
F
A
A
A
So
you're
I
think
you're
you're
thinking
about
one
part
of
this
and
I'm
thinking
about
the
other.
If
a
change
gets
made
in
get
that's
fine
and
that's
expected,
but
at
some
point
that
data
needs
to
get
sent
or
evergreen
Jenkins
I/o
has
to
be
notified
that
there's
a
new
version
of
that
in
order
for
it
to
generate
the
right
information.
So
that's
all
this
is
okay.