►
From YouTube: Essentials: Open Planning Meeting (2018-07-31)
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
Mandy,
do
you
mind
if
I
sort
of
just
talk
about
our
progress?
First
Before
we
jump
into
some
of
this
other
stuff,
so
I'm
very
pleased
to
report.
That
was
the
production.
Evergreen
back
up
or
back
ends.
Excuse
me
is
online
and
is
functional,
so
I
qualified
some
of
the
some
of
the
work
yesterday
to
make
sure
that
the
database
was
correct
and
that
updates
were
being
delivered
to
new
clients
and
things
like
that,
and
but
this
is
a
big
it's
a
very
important
step
to
getting
actual
users
to
adopt
and
use
Jenkins
essentials.
A
I'm
very
excited
it
up.
There's
some
outstanding
work
that
I
still
need
to
get
into
JIRA
to
get
us
to
where
we
can
close
out
milestone.
One
for
me
say
from
the
production,
readiness
standpoint
and
a
lot
of
that
and
I'll
just
get
into
some
of
my
tickets
and
a
lot
of
that
comes
down
to
automatically
generating
this,
not
ingest.
That
VML
knows
a
typo
but
automatically
generating
the
ingests
content
that
we
ever
made.
B
C
B
A
A
A
B
I've
got
the
changes
in
for
the
server
side.
I
just
need
to
troubleshoot
some
finer
details
with
that
and
then
I've
started
on
the
changes
for
the
client.
The
only
thing
I
haven't
figured
out
for
the
client
is
how
to
get
the
actual
flavor
value
into
the
object
that
we're
creating,
because
I
think
those
are
docker
containers
right
on
the
client
side,
the
only
part
because
I
haven't
felt
like
my
whole
lot.
They.
A
B
Actually,
what
I've
been
looking
at
in
in
the
docker
file
having
it
push
in?
Basically
the
value
of
the
directory
that
we're
building
from
because
each
one
has
its
own
custom
docker
file,
and
we
know
the
directory
names.
So
I've
already
started
on
the
path
of
injecting
that
variable
into
the
container
and
now
I
just
need
to
get
the
actual
client
code
to
read
that
variable
and
pass
it
along
when
it
calls
you
to
create
okay.
A
But
we've
got
some
time
set
up
later
today
to
do
a
parent
session.
I
think
we
should
be
able
to
assuming.
We
can
figure
out
the
debugging
problem
that
you've
had
challenges
with
from
the
client
side
and
getting
those
tests
to
pass
I
think
we
should
be
able
to
get
that
wrapped
up.
Listen
sounds
like
it
sounds
like
you're,
so
close
I
know.
A
B
B
A
A
A
A
A
So
the
last
item
that
I
want
to
leave
in
your
mind
and
to
think
about
and
when
Battiste
gets
back
I
when
I
talked
with
him
about
it,
more
I've
been
considering
simply
referring
to
this
entire
thing
as
evergreen
and
part
of
the
reason
so
dropping
the
essentials.
Moniker
and
part
of
the
reason
that
I've
been
thinking
of
dropping
it
is
jakey's.
A
Essentials
is
very
confusing
for
a
lot
of
people
and
it
makes
people
think
it's
an
all-in-one
bundle
distribution
that
solves
all
your
problems,
which
is
it
is
not
exactly
but
a
lot
of
the
I'd
say
the
automatic
nice
things
for
users.
We
had
put
down
into
milestone,
two
which
we
may
or
may
not
be
able
to
get
to
in
the
near
term
and
I.
Think
evergreen
more
appropriately
captures
the
automatic
updating
aspect
of
this
and
will
help
us
solicit
users
that
appreciate
the
automatic
updating
part
without
necessarily
needing
to
implement
all
of
the
batteries
included.