►
From YouTube: Essentials: Open Planning Meeting (2018-06-19)
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
B
A
C
D
So
welcome
everybody,
so
I'm
gonna
just
share
my
screen
right
away
so
that
we
have
the
place
to
look
at
by
the
way.
Welcome
Mundy,
so
it's
she's
showing
about
Amanda
on
the
left,
is
working
going
to
work
with
us
and
as
a
back-end
service,
developer
and
so
right
away.
Switching
to
what
I
was
working
on
and
I
will
give
the
mic
to
Mandy's
feisty
later
I
think
so.
Last
week,
I
was
mostly
at
the
exit
conference.
Where
I
gave
a
talk
about
essentials.
D
A
D
Sure
so,
and
I
actually
pinged
through
Twitter
yesterday
the
Eclipse
confrontation
and
Kids
Foundation
and
so
on.
For
now
no
answer
yet
I
hope
it
will
be
posted
soon,
so
that
I
can.
Then
it
did
find
something
like
and
Trillian
reference
it
from
there
right.
So
what
I've
switched
to
since,
mostly,
and
also
trying
to
help
Amanda
who
I
should
call
Mandy
on
the
project,
is
the
LMS
support?
D
So
it's
kind
of
disabling
issue
of
the
docker
cloud
flavor.
We
support
since
roughly
two
weeks
so
now
we're
trying
to
see
you
how
we
are
going
to
set
up
a
collection
agents
right
away
from
AWS,
so
the
status
about
that
is
that
it's
just
getting
started
for
tomorrow
morning,
I'm
going
to
have
a
work
with
someone
who
knows
ECS
much
more
than
me,
so
that
we
optimize
the
timing
and
see
if
we're
able
to
spawn
agents
from
there,
then
see.
Then
what
are
the
possible
caveats?
D
That's
bottom
line
tomorrow,
we're
trying
ICS
and
see
how
it
behaves,
then,
even
if
I
separated
it
from
that
ticket,
we
are
going
to
very
soon
just
once.
It's
done
to
look
at
Auto
configuring
or
so
when
it's
using
the
elbe
newest
flavor
of
essentials.
You
know
Auto
configuring,
to
use
the
external
artifact
storage
to
start
things
in
s3,
as
was
developed
some
weeks
ago,
but
the
by
the
architecture
team.
So
unlike
Jesse
and
Carlos
and
I.
Guess
that's
it
for
me
for
for
the
last
week
and
it
was
a
collusive.
A
A
Something
to
provision
agents
either
as
containers
or
VMs,
and
that's
not
something
that
Jenkins
has
really
done
out
of
box
before.
So
this
is
a
little
bit
uncharted
territory
as
far
as
starting
up
the
Jenkins,
with
from
the
very
very
beginning,
with
zero
masters
and
automatically
having
some
other
agent
provider
configured
so
I
think
it's
pretty
cool
working,
teased,
yeah.
B
A
system
built
into
Jenkins
core
that
allows
you
to
define
a
cloud
which
is
sort
of
at
this
point.
I
would
consider
it
kind
of
the
legacy
support
for
actual
clouds.
But
basically
it
says
if
you're,
if
you're
please
go
ahead
and
start
allocating
some
new
agents
out
of
some
pool
that
you
have
available
I.
Think
in
the
longer
term,
we'd
like
to
take
advantage
of
stuff.
That
niccola,
for
example,
is
experimenting
with,
whereby
we
can
directly
make
a
connection
to
a
fresh
cloud
machine
using
whatever
service
we
have
available
in
the
course
of
a.
A
A
D
So
I'm
using
for
the
poker
club
what
we
call
flavor
the
docker
plugin,
which
basically
indeed
implements
the
cloud
API
for
Ducker
and
I'm,
using
kind
of
the
same
for
ECS
and
there's
another
plug-in
called
ec2
plug-in,
which
is
doing
exactly
the
same
for
provisioning
from
ec2,
and
so
yes,
and
so
Jesse
just
may
be
for
others,
and
so
for
myself.
I
think
the
main
issue
as
I
knew
nothing
with
what
you
were
saying
about.
D
The
cloud
API,
for
instance,
is
that
it's
necessarily
because
of
the
fact
it's
going
through
the
queue
and
then
waits
for
it
when
it
goes
too
fast
and
so
on
some
kind
of
latency,
which
we
can
really
reduce.
You
know
to
zero
before
some
some
agent
starts
being
provisioned
right.
That
would
be
kind
of
the
original
design
issues
with
this
yeah.
B
I
mean,
though
the
cloud
API
was
sort
of
a
transitional
system
that
sort
of
took
the
visiting
model
of
static
agents
and
tried
to
make
it
work
with
an
elastic
system,
but
basically
a
response
to
increasing
pressure
by
allocating
more
agents
and
then,
after
a
while
it
can
the
cloud
implement
case.
An
implementation
can
drop
some
of
them,
but
I
mean
what
we
really
want
to
be
moving
towards.
Is
that
you
know
there's
no,
there's
no
general
pool
of
agents
attached
to
Jenkins
floating
there.
B
B
Perhaps
I
mean
that
there
is
some
work
on
I
know
by
Google
to
create
a
warmed
up
char
cache
so
that
you
can
start
up
a
remoting
agent
with
all
of
the
plugin
chars
that
needs
already
present
statically
in
the
image
before
it
launches.
You
don't
have
to
transfer
code
in
the
normal
case
over
the
channel,
so
there's
various
optimization.
So
you
can
make
okay
I.
D
B
Did
want
to
mention
one
thing:
that's
pretty
critical
for
adding
AWS
agents,
which
is
that
you
need
to
think
about.
I
am
Ross
or
whatever
your
security
scheme
is
so
in
the
case
of
the
s3
plug-in,
we
made
a
decision
that
we
expect
the
the
master
to
have
some
sort
of
AWS
credentials
that
could
those
could
be
implicitly
the
via
I
am
or
we're
also
working
on
a
GUI.
That
would
let
you
configure
particular
credentials
and
Jenkins
if
you
prefer,
but
either
way.
B
D
Be
considered
untrusted
yeah
I
remembered
the
JEP
about
that
yeah.
So
it's
it's.
It
was
supposed
to
be
pushed
from
the
master
so
that
it
just
have
some
some
temporary
thing.
I,
remember
something
I
used
to
download
and
maybe
not
to
upload
or
something
and
go
through
a
master.
Yeah
I.
Remember
something
about
that:
India
in
the
JEP
about
artifacts
storage.
Right,
yes,.
B
D
Yeah
indeed,
the
I
am
is
going
to
be
slightly
more
tricky
than
just
using
an
access
and
access
key
and
its
password,
as
I
already
somehow
discovered
the
battaglia
today
but
anyway.
So
let's
just
go
on
enough
speaking
already
more
than
ten
minutes,
let's
switch
to
others.
So
let's
keep
the
better
for
yen
I
guess
so,
let's
switch
to
Tyler
and
we'll
switch
to
Mandy
I
think
at
words.
So
Tyler
what's
the
status
today,
you
want
to
hear
your
voice
again
with
the
noise
behind
there's.
A
The
work
that
I've
been
doing
is
just
getting
the
computed
up
made
manifest
to
the
clients
and
as
far
as
I
can
tell
at
this
point
this
morning
everything
looks
correct
from
a
system
standpoint,
but
the
smoke
paths
are
still
failing,
though
I'm
very
happy
batiste
that
he
did
the
work
and
put
those
snow
tests
into
place.
But
well
it
takes
me
forever
to
run
house
is
actually
quite
helpful.
Okay,
integration
of
client
server
and
Jenkins
running
so
this
this
before
request,
that's
related,
was
computing
update
mode.
A
Plugins
that
we
would
need
in
their
dependencies
that's
enough
to
get
us
moving
right
now.
There's
some
hard-coded
overrides
for
stuff
59
from
that
depository
or
we'll
need
to
find
that
at
a
later
point,
some
way
to
say
get
I
said
the
essentials
DMO
and
incrementals
repository
at
a
little
bit
closer
together
to
generate
that
in
just
IMO,
but
from
that
the
server
is
only
giving
the
client
what
updates
it
needs.
A
So
what
that
means
from
that
from
a
data
flow
standpoint
is
every
time
we
create
a
new
update
level,
and
this
is
defined
in
in
the
Jeff
307.
All
of
the
dependencies
are
listed
there.
Every
single
you
know
artifact
most
part
of
that
update
level
is
listed,
but
when
the
client
contacts
us
we're
going
to
have
the
latest
versions
of
software
on
that
clamp,
and
then
we
do
a
signature
comparison
and
we
only
give
the
client
what
it
needs
so
we're
not
readout
loading
the
entire
world.
Every
time
we
have
an
update
level
so.
C
A
A
To
say
that
it
works
because
the
tests
are
still
filming,
but
it
looks
like
it's
working
and
I'm,
not
sure
where
the
tests
are
going
right
now,
which
is
why
we've
been
sort
of
locked
up
on
getting
that
production
environment
under
ever
great,
not
checking
tile
deployed,
because
this
needs
I
need
to
land.
This
first
and
I.
Please,
like
that
at.
D
Least,
you
made
a
huge
step
like
30
minutes
ago
or
less
because
now
that
we
can
see
on
the
logs
of
that
our
kite
in
DCI
that
Jenkins
does
start
so
now,
there's
something
wrong
with
the
client
handling
which
is
receiving
non
json
response
from
your
debt
service,
as
it
said,
but
we
can
see
that
Jenkins
now
starts
when
it
couldn't
before.
That's.
A
Something
I've
got
to
figure
out
a
better
way
to
handle
this
when
you're
turning
a
304,
not
a
lot
of
mileage,
either
express
or
feathers,
is
not
allowing
me
to
do
fly
in
the
body
and
I
think
it's
just
inserting
its
own
body.
So
it's
the
client
is
requesting
a
content,
type
of
application
JSON
and
the
server
is
saying
now.
I'm
gonna
give
you
an
error
message
instead
and
thereby.
D
Yeah,
let's
table
that
for
later
I
had
a
question
about
that.
But
let's
just
do
that
later,
so
girls,
that's
great,
so
yeah
I
will
have
a
look
and
so
I'm
not
sure
by
the
way.
I
can
really
help
on
that
part,
but
seems
like
now
he's
starting
so
great.
Let's
just
keep
that
for
the
chat
and
later
discussions,
let
now,
let's
switch
to
Mandy
targeting
anyone
else.
So
as
I
was
saying,
keeping
the
better
for
the
and
so
Mandy
welcome
and
thanks.
D
C
D
And
don't
hesitate
by
the
way
I
mean
we
generally
try
to
push
PR
that
already,
but
you
can
definitely
R.
So
in
that
very
case,
I
guess
push.
You
know,
work
in
progress
PR
so
that
we
can
provide
feedback
and
get
it
get
you
more.
You
know
help
even
more
in
a
circular
loose
way.
Sometimes
I
mean
pushing
things
in
order
in
explicitly
tagged
label
as
such
PR,
so
that
we
can,
you
know,
provide
what
we
think
are
are
failing,
and
you
know
you
can
use
the
yourself.
D
C
D
Great,
and
so
as
I
was
saying
for
others
I
just
told
earlier
Mandy
that
I
think
it
would
be
easier,
and
anyway,
that's
kind
of
what
we're
trying
to
do
in
general
to
just
file
a
specific
PR
for
only
the
first
case
about
your
making
sure
when
we're
setting
to
large
data
it,
which
is
that
it
should
be
something
instead
of
just
you
know,
making
a
big
PR,
addressing
everything
with
regards
to
aligning
to
the
chip
will
be
making
the
review
easier
and
overall
anyway,
I
mean
it
makes
sense.
It's
not
it's.
A
Certain
deeply
if
you're
related
is
you'll,
find
this
on
those
on
the
backend
Mandy,
but
there's
a
lot
of
there's
a
lot
of
stuff
that
was
kind
of
stubbed
out
originally
and
unstopping.
Some
of
those
things
out
once
you
get
out
of
error,
telemetry
becomes.
A
D
A
A
D
Mean
who
I
think
we
are
that's
a
good
thing,
I
think
we're
all
aligned
to
the
fact
that
we
should
keep
P
ours
easier,
smaller,
because
we
all
know
that
it
makes
reviews
and
everything
or
orders
of
magnitude
easier
and
quicker,
but
we
also
know
that
sometimes
it's
just
impossible,
so
that's
that's
right,
I
mean
so
I
think
we
are
mostly
done.
Anyone
have
has
anything
to
add
I.
Think
I.
A
A
B
Being
used
a
bit
more
from
pipeline
code,
I
also
seem
that
it's
being
used
some
from
the
Java
10
hackathon,
so
that
people
can
have
a
I
think
well.
Leg
was
working
on
setting
up
docker
images
using
incremental
builds
of
plugins
that
we
could
have
a
ready
to
run
image
containing
a
complete
snapshot
of
stuff
that
had
various
known
fixes
in
it.
B
B
A
D
D
D
D
D
Yeah,
okay,
exactly
so
thanks,
everybody
I
think
we're
done
and
we're
in
time.
Five
minutes
left
that
that's
okay,
awesome!
So
thank
you!
Everybody
and
so
see
you
next
week
same
time
and
if
you
need
anything
or
you're
interested
to
join
the
project,
so
I
just
remind
that.
It's
happening
mostly.
The
most
discussions
are
happening
here
on
git
er,
so
associated
to
the
repo,
and
that's
it.
Thank
you.
Everybody
and
see
you
later.
Bye,
bye,.