►
From YouTube: Essentials: Open Planning Meeting (2018-04-30)
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
All
right
and
now
it's
online,
so
I'm,
sorry
I'm
a
little
late
today,
I
had
a
busy
weekend
which
we
can
talk
about
later
on
a
not
recorded
channel.
A
A
C
A
D
A
Perfect,
it's
huge
I,
so
they
I
sent
a
I
wrote
a
blog
post
last
Friday
for
in
my
time
and
I
know
if
it
east
or
probably
you'd,
seen
it
I'm.
Actually,
given
you
know,
given
how
much
work
we've
been
doing
and
how
we
had
anticipated,
having
one
more
person
working
on
this
a
person
yet
to
be
hired
at
Chloe's
I'm,
actually
quite
pleased
with
the
progress
that
we've
been
raised.
A
A
This
frame
no
we'll
get
at
the
status
and
yeah,
but
we're
really
the
the
pre-baking
of
configuration.
That's
that's
there
in
some
basic
level
and
then
the
updates
and
the
version
stuff.
That's
working
in
progress
and
I
think
that's
I!
Think
it's
moving
along!
Well,
we've
got
a
good
decent
design
out
there.
I
think
the
client
is
completely
ready
for
EM
for
those
updates
to
start
being
applied
from
the
the
snapshotting
system,
but
I
think
we're
very
close.
That's
what
I'm
getting
at
I
think
it's
tying
up.
Some
loose
ends:
I
guess.
B
A
E
Yeah
so,
for
my
part,
working
on
the
developer
show
Oh
Jenkins,
5
0
5
4,
0,
+,
90,
+,
5,
0,
61
P.
The
pure
course
is
already
there
just
waiting
for
March
this,
but
I
can't
put
that
on
under
you.
There
is
one
to
report
that
at
the
Ronnie
th
another
one
that
runs
the
PCT
just
the
runs.
Don't
use,
get
custom
work
papa
here
and
get
3:05.
E
A
E
It's
ready,
but
is
not
yet
they
complete
workroom,
we
want
I
mean
different.
This
is
not
getting
the
full
latest.
What
is
it
version
of
essentials
and
using
the
custom
work
packages
to
generate
a
custom
watt?
Five
with
all
the
latest
versions.
Now
the
terminus
did
waiting
to
run
decades
and
appreciative.
So
there
is
a
previous
step
to
work
this
over
idea,
which
is
being
able
to
build
a
custom.
What
we
thought
the
decided
fashion,
not
at
a
monistic
way,
because
now
it's
a
eh,
put
the
feather.
F
Yeah
right
on
the
custom
word
picture
side.
We
have
tasks
to
integrate
with
Geo
305
I
mean
deployment
of
incrementals,
I
hope
to
kinda,
literally
within
next
two
weeks,
so
that
I
will
have
to
link
for
both
deployment
and
for
using
this
releases
and
custom
work
package,
but
yeah.
The
main
thing
is:
we
depend
on
that
all
plugins
you
use
in
essentials.
F
G
There
are
other
changes:
it's
not
just
the
parent
poem,
but
well
I
mean
it
depends
on
what
you're
actually
trying
to
accomplish.
So,
if
you
switch
metadata
to
incrementals
form,
that
means
you're
able
to
publish
binaries
from
individual
commits,
but
whether
those
are
actually
used
by
a
particular
test
suite
depends
on
how
that
test.
Suite
is
configured
so
I
didn't
see
anything
yep
plug
in
PR,
for
example.
That
would
directly
use
that.
G
A
F
If
you
just
a
need
latest
from
the
master
branch
you
from
whatever
the
branch
you
can
do
it
now
in
custom
work
packages,
you
just
define
this
latest
branch
as
a
source.
The
program
in
that
this
latest
versions
won't
be
tracked
and
won't
be
published
to
incremental
releases
so
that
you
won't
have
a
traceability,
so
would
huge
test
all
that's
the.
A
B
A
C
A
G
G
A
F
A
I've
no
plans
on
pointing
the
update,
centered
generation
towards
that
incremental
repository.
Okay,
go
to
it
and
just
just
for
your
background.
Only
part
of
the
reason
that
I'm
fairly
strongly
against
that
is,
we
had
significant
I
would
say,
load
challenges
that
were
difficult
to
diagnose
in
artifactory
because
of
how
heavily
how
heavily
that
and
the
churn
was
in
the
releases
repository
and
artifact
thérèse
indexing
was
taking
quite
a
long
time.
A
G
G
A
E
A
Maybe
after
this
just
to
keep
us
moving
along,
but
we
didn't
fall,
I
just
want
to
make
sure
I've
got
pria
scope
of
if
iron
is
technically
the
the
test.
Automation
work
is
going
on
the
get
plug-in
and
that's
moving
along.
Well.
If
I
wanted
to
start
taking
incrementals
and
blue
ocean
and
pipeline,
for
example,
those
I
think
are
going
to
have
the
biggest
impact
for
for
the
teams
working
on
those
it'll.
We
can
start
to
consume
those
more
rapidly
just
what's
the
Delta
in
work
to
where
we
could
reasonably
pull
those
in.
G
Yeah,
you
know
maybe
I
should
sync
up
with
Andrew
about
that
I
mean
there's,
there's
also
a
conversation
we'll
have
with
the
pipeline
team
about
what
Gingka
baselines
are
appropriate.
But
that's
worth
aagama
like
thank
you,
because
you
can
do
incrementals,
even
when
you're
not
picking
up
an
incremental
version
of
core,
even
when
you're
using
the
old
LTS,
but.
A
What
I'm
thinking
is
if,
if
Raul
and
Oleg
have
some
there's
some
connections
to
be
made
between
what
we're
always
working
on
and
the
customer
package
or
stuff
that
that
will
legs
been
working
on?
Well,
that's
going
on.
Maybe
you
Andrew
and
I
can
bridge
the
gap
for
pipeline
to
sort
of
get
pipeline,
ready
to
be
consumed
and
tested,
and
that
may
be
I.
Think
that'll
reduce
some
of
the
wall
clock
time
for
getting
this
work
done.
Yeah.
G
What
I
would
like
to
see
very
roughly
is
it's
some
simple
tool
you
could?
You
could
run
where
you
have
if
you
have
a
check
out
of
evergreen,
that
you
can
just
say,
run
this
tool
and
it
would
inspect
all
of
the
repositories
that
go
into
it
and
proposed
updates
or
all
of
the
plugins
that
are
listed
there.
E
G
A
A
A
B
It
works
for
real,
with
Swiss
checks
and
so
and
I
think
right,
because
right
now,
I
can
push
whatever
I
want.
So
I
I.
Think
overall,
and
you
know
over
time,
I
think
we
should.
You
know,
begin
to
be
more
picky
about
what
is
acceptable
on
the
server
side.
Thing
pushes
by
the
way,
I
didn't
write,
know
start
writing
the
any
China
of
jet
for
the
server
side.
I
guess
we
should
do
that
or
do.
A
B
B
Indeed,
on
the,
how
do
we
make
it
testable
and
hackable
on
locally
on
the
developer
machine
in
the
server
side,
yeah
exactly
and
kind
of
related
related
to
what
you
said
in
your
introduction
today
we
need
to
start
wiring
things
together,
so
that
it
actually
use
these
things
locally,
even
when
developing
an
evergreen
which
now
is
mostly
mucked.
So
what
yeah?
That's
it.
B
Not
lot
not
enough,
like
I,
think
I
yeah
bit
I
was
thinking,
for
instance,
should
we
have
different
end
points
or
on
new
one
for
era
logging?
You
know
and
use
a
different,
let's
say
type
field
to
push
are
all
things
from
genteel
things
like
the
Evergreen
client
things
like
know
the
system
log
where
there's
no
filly
system
logs
in
the
docker
container,
but
anything
new.
For
instance,
you
introduced
in
the
future
any
kind
of
reverse
proxy.
A
The
reason
I
bring
that
up
is
early
early
on
when
I
was
prototyping.
Some
of
evergreen
out
I
was
planning
on
just
shooting
errors
straight
from
the
client
to
century
century
die.
Oh,
and
one
of
the
things
that
I've
been
debating,
whether
we
should
do
is
we
still
want
to
own
that
end.
Point
like
we
want
our
logs
to
come
into
into
the
backend
services,
but
for
ease
of
use
it
might
make
sense
for
us
to
then
relay
those
to
a
service
like
century
yeah.
B
So
for
your
information,
you've
written
that
in
in
some
of
the
tickets
saying
we
should
end
on
the
endpoint
indeed
and
possibly
later
or
now,
I'll
hit
send
things
outside,
for
instance,
what
I
think
we
discussed
some
time
ago?
Maybe
are
so
the
GC
login,
for
instance.
We
could
push
that
to
some
external
service,
where
some
experts,
for
instance,
and
that
would
analyze
and
you
may
be
able
to
trigger
some
other
issues
and
so
on
so
yeah,
that's
kind
of
maybe
interesting
to
discuss
and
will
you
do
me
a
favor.
A
And
will
you
maybe
set
up
some
time
to
talk
with
Olivier
about
some
of
the
error
logging
work
that
he
had
done
originally
when
I
started
working
on
Jenkins
infrastructure,
we've
looked
at
some
log
aggregation
for
infrastructure
services
and
just
talked
to
him
about
what
we
have
right
now
in
our
kubernetes
infrastructure
for
handling
logs
from
services.
We
might
have
something
we
can
take
advantage
of
there
right.
C
A
F
Yeah
actually,
regarding
student
I'll,
follow
up
on
the
thread,
because
I
think
we
can
get
benefit
from
some
stories
and
maybe
work
around.
They
need
to
update
each
plug-in,
so
I
will
follow
up
with
Jesse
to
understand
the
incremental
fairly
small.
We
have
a
first
order
for
deployment
to
incremental
releases
from
custom
work
packages
and
actually,
if
it
works,
we
may
close
the
gap,
at
least
for
the
hub,
for
this
story
without
updating
plugins,
but
no
warranty
that
it
can
really
work
and
to
understand
it.
Obstructing
this
Jason.
A
B
B
You
know,
as
I
said
in
on
the
chat
kind
of
end,
users
can
Alaska
acceptance,
testing
always
say
for
me,
you
know
triggering
the
actual
instance
in
Jenkins
in
the
container
like
we
do
now
and
check
that
the,
for
instance,
the
Aurora
logging
service
do
service
does
receive
the
warn
the
warnings
and
so
on.
For
instance,
we.
A
E
E
A
So,
tomorrow,
roll,
if
you
ping
batiste,
is
the
maintain
the
reason
that
I
mentioned
the
build
trigger
badge
is
he's
the
maintainer
of
it,
and
it's
a
very
small
and
simple
plugin
to
wear.
If
you
wanted
to
test
some
of
the
the
PC
to
your
ath
work
that
you're
doing
with
that,
it
might
be
a
much
smaller
surface
area
than
they
get
plugin.
If
you
wanted
to
compare
and
contrast,
no.
E
F
E
A
E
D
F
B
A
Well,
I
guess
so:
I'll
be
very
lonely
tomorrow
and
I'll
look
forward
to
to
seeing
you
all
on
Wednesday.