►
From YouTube: Essentials: Open Planning Meeting (2018-07-17)
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
B
B
A
B
D
Let's
just
make
with
that,
so
I
was
looking
at
this
just
a
few
minutes
ago,
and
so
a
waste
are
going
to
start
from
the
right
to
try
and
describe
what's
the
current
status,
so
the
SEC
gateway
is
basically
something
kind
of
blocked
under
oceans
by
because
it's
something
we
adapted
for
the
new
feature
in
Jenkins
that
lets
you,
you
know
put
logs
elsewhere,
that
under
Jenkins
home
slash
logs
but
I,
think
Vivek.
Is
it
worried
that
it
would,
you
know,
break
something
somewhere?
So
what
I?
From
what
I
understand?
D
With
his
last
comment,
I
think
he's
kind
of
expecting
us
to
you
know,
bump
it
using
our
setup
or
incrementals
so
well,
I,
don't
want
to
spend
too
much
time
increment
if
incremental
defying
access
here
is
you
get
web
login
because
it
didn't
seem
very
prioritize
so
right
now
we
have
a
skipped
test
in
our
code
base,
specifically
to
that
case,
which
is
not
great,
but
well.
We
have
more
pressing
things
in
the
plate,
so
that
that's
that's
kind
of
so
well.
D
If
we
want
to
move
this
forward,
we
will
probably
have
to
find
some
way
to
test
SEC
gate.
We
are
all
sales
or
push
by
anyway
that
thing
forward
yeah.
So
for
other
things
like
so
that's
great
because
for
the
other
issue,
we'll
come
back
to
the
board
about
Jenkins
52
584,
so
the
wrong
availability
zone
in
essentials.
For
about
us.
So
that's
a
good
and
bad
news,
because
so
I
I
think
I
fixed
this
yesterday,
just
actually
before
Carlos
reported
it.
D
But
the
very
good
news
and
nice
thing
is
that
actually
somebody
else
than
me
played
and
and
actually
provisioned
something
provisioned,
the
LMS
flavor
somewhere
and
so
Carlos
discovered
that
issue,
which
I
ended
up
fixing
like
somehow
hours
before
I
reported
it,
but
it
provision
did
the
day
before.
Unfortunately,
I
actually
had
screwed
up
the
place
where
a
field
should
be,
and
so
any
unfortunately
is
as
it's
a
string
and
not
you
know
strongly
typed
thing
it.
D
It
was
correctly
set
by
the
config,
ask
or
plug-in
you
know
for
allegan
the
change
its
configuration,
but
only
would
show
up
when
you
would
try
to
provision
explicitly
given
new
agent
so
and
I
discovered
that
you
know
testing
again,
I,
think
Tuesday
or
Monday
morning,
and
the
time
spent
fixing
it
and
making
sure
things
worked
and
Carlos
was
already
testing
so
unfortunate.
But
the
rest
were
fine.
D
On
top
of
this,
which
is
called
promise
requests
retry,
which
basically
integrates
the
retry
stain
kind
of
standard,
not
used
a
lot
NPM
module
to
retry
things
with
the
request
course
promise
also
kind
of
standard
mode,
NPM
model
to
offer
some
higher
or
an
easier
nice
way
to
retry
things.
So
for
now,
I've
used
three
retries
and
and
I
left
the
default
behavior
of
the
retry
model,
as
is,
which
means
it's
going
to
use
an
exponential
back-off
strategy
going
to
retry,
try
first
after
one.
D
Second,
then
two
seconds,
then
four
seconds
so
we'll
see
if
that
proves
enough
or
if
you
want,
you
know
to
try,
maybe
a
bit
more
so
that
it
goes
beyond
like
10
seconds
or
something
it
could
make
sense.
I,
don't
know
what,
if
you
have
anything
about
any
opinion
about
that
was
one
do
but
obtain
from
a
bus.
B
D
And
other
things
in
flight
right
now,
so
I've
just
filed
the
PR
bit.
So
basically
it's
didn't
progress
because
I'm
waiting
for
the
CI
completion,
but
it's
also
in
Review
for
the
the
earliest
favor
test
in
CI
I
thought
I
would
do
that
later.
But
finally,
I
did
that
pretty
much
earlier,
because
right
now,
there's
already
a
PR
file
by
some
other
than
than
the
core,
with
a
core
team
of
essentials,
5
by
Jessie
and
it
didn't
have.
They
didn't
have
really
easy
ways
to
test
these
changes
locally
or
in
CI.
D
So
that's
why
I
ended
up
doing
that
and
that's
mostly
it
I
need
to
get
back
then
to
the
two
other
ones
in
transient
progress.
The
the
ssh
public
key
one
is
another.
Look
from
my
side:
I
created
a
mais
manually
as
I
said
in
The
Associated
JIRA's
to
go
quickly
or
for
now,
instead
of
using
my
god,
I
would
scold
that
tool
to
you
know,
generate
things,
be
it
a
MRIs
or
via
trade
books
and
from
master
Packer.
B
A
A
A
D
That's
not
impossible,
I
missed
it,
but
I
searched
for
it
just
a
bit
and
it
doesn't
find
anything
obvious.
So
maybe
in
the
marketplace,
but
you
know
I
wasn't
sure
it
was
better
to
use
something
from
the
marketplace,
not
really
official.
You
know,
probably
provided
by
someone,
but
not
really
more
official
than
us
or
by
anybody
s
itself
or
by
docker,
for
instance,
and
I
didn't
find
anything.
So
if
we
do
well
yes,
it
would
be
interesting,
but
anyway
I
kind
of
suspect
that
then
there
will
be
docker,
but
not
Java,
which
is
Rick.
D
B
D
A
Think
I
screwed
up
both
so
I
would
be
very
surprised,
like
I
know,
on
Azure,
and
that's
where
my
experiences
docker
maintains
a
docker
on
a
good
image
in
the
marketplace
and
that
sort
of
equivalent
would
make
sense
for
for
the
master.
I
would
be
really
surprised.
There's
not
a
Linux
container
or
not
Alaska
native
keeping
a
Linux
image
in
the
AWS
marketplace.
That
just
includes
the
latest
open
JDK
for
the
latest
Oracle
JDK.
D
Yes,
I
wouldn't
be
surprised
for
one,
because
Oracle
is
unlikely
to
well
provide
something
like
this,
because
even
the
JDK
itself
has
been
probability
for
years.
So
well,
right,
University,
open
JDK
so
might
be
different.
Okay,
but
then
then
there
might
not
be
but
or
there
right,
I
will
have
another
look
something
containing
both
so
yeah.
Your
point
is
about
the
master
so
yeah
for
the
master.
We
could
be
able
to
use
an
officially
a
my
I
agree.
I
was
indeed
still
thinking
about
the
agent
once.
A
A
A
D
Well,
yeah,
but
how
would
this
work
tins
for
for
agent?
They
would
probably
we
will
provide
some
way
to
update
the
ec2
configuration
and
for
the
master
I
guess
it
will
be
standard
as
a
various
update.
I
guess
you
know,
I
mean
I
mean
then
anyway,
we
don't
want
to
be
the
one.
The
responsible
for
publishing
didn't
edit,
that
am
I
yeah
right
right,
right,
I
really
were
up.
I
will
just
reopen
the
two.
A
D
This
is
the
third
one
you
see
in
progress
and
Gipe
is
already
filed
and
I
think
you
commented
on
that
one
about
the
deletion
so
right
now
it's
well.
It's
not
blocked
per
se.
I
need
to
just
find
finest
spent
and
spent
I
spent
more
time,
making
sure
I
address
every
single
comments
when
I
actually
think
I
did
for
some
of
those.
But
I
didn't
hear
back
so
I,
yeah,
I,
guess
I
just
need
to
push
to
be
slightly
more
pushy
to
actually
get
answers
on
my
and
the
things
that
I
deem
addressed.
D
A
So
the
other
question,
no
I,
don't
there's
some
thoughts
that
I
have
that.
I
need
to
think
longer
that
before
I
ask
questions
and
the
stuff
that
Manny's
been
working
on
and
that's
that's
gonna
be
in
flight
until
next
week.
I
believe
I
think
she's
out
this
whole
week
and
I
had
started
on
the
the
migrations
container.
So
the
plant
and
I
don't
remember
if
we
reviewed
this
at
all.
But
the
plan
is
that
for
the
deployment
in
the
kubernetes
environment,
we're
gonna
have
a
separate
container.
A
That
just
runs
this
equalize
migrations
and
see,
and
then
whisk
is
that
yeah
they
started
putting
really
that's
pretty
simple,
great
and
then
assuming
that
we
can
get
trusted
CI,
which
is
the
Jenkins
environment.
That's
building
containers
to
properly
run
the
Evergreen
tests,
then
we'll
be
able
to
get
those
containers
published
pretty
quickly.
D
C
D
A
D
Think
you
merged
something.
Didn't
you
I,
do
the
PR
from
you?
What
about
rewriting
or
refactoring
some
tests?
Also,
yesterday,
I
want
the
power.
Yesterday
I
mean
maybe
it
was
like
two
days
before
but
tell
you
then
it
would
personally
make
sense
because
he
was
studying
to
deploy
around
like
you
know
two
days
ago,
so
roughly
it
could
have
could
have
kind
of
much
anyway.
D
It's
just
with
that.
Well
I
mean
anyway,
it
will
get
messy
again
in
the
future,
I
suppose,
but
yeah,
it's
just
right
now,
a
bit
messy
to
actually
figure
the
model
of
everything
without
actually
dumping
the
database
and
have
a
look
I
know
that
that
man
is
many
had
to
do
that
some
days
ago
and
yes,
looking
at
those
different
files,
you
have
to
mentally
either
mentally
build
that
thing
that
model
from
the
I
mean
dude,
DV
model
or
or
yes
them
the
DB,
and
have
a
look
at
at
what's
currently
available.
I
added.
C
A
Look
there's
a
there's,
a
hack
that
I
was
doing
on
the
weekends
and
that
I
need
section
there
so
make
it
easier
to
use
node
and
the
node
modules
directly
from
your
shell
will
actually
go
into
the
docker
container
I
played
around
with
that.
So
you
don't
have
to
say
you
know,
dot,
dot,
slash
tools,
node
do
this.
C
A
So
I'm
gonna
I'm
going
to
wrap
that
up
and
and
get
that
submitted
today
and
I
also
spent
some
time
poking
around
with
typescript
over
the
weekends
or
it
actually
works
fairly
well,
with
feathers,
I
was
kind
of
surprised.
Someone
already
did
the
work
about
a
year
ago
to
make
feathers
in
typescript
work
well
together
and
I
talked
a
bit
with
Mandy
about
it.
A
Last
week
when
we
were
just
chatting
one
on
one
and
I,
don't
know
how
useful
it
would
be
right
now
for
for
where
the
project
is
but
I
think
for
the
for
the
models
and
for
some
of
the
the
services
side
of
the
world,
I
think
some
type
take
checking
could
be
useful.
It
looks
fairly
straightforward
to
incorporate-
maybe
maybe
when
I'm
awake,
some
nights
with.
A
D
A
D
It's
not
the
cut
that
took
the
test
that
didn't
fail.
Everything
is
just
broken.
You
should
just
you
know,
I'm
used
when
I'm
doing
that
in
July
I'm,
indeed
used
to
you
know,
see
that
everything
breaks
before
it
really
actually
reaches
the
state
where
the
stage
where
tests
are
run,
yeah,
yeah
but
yeah
anyway,
I'm
kind
of
starting
to
feel
more
and
more
used
to
it.
So
it's
nice
anyway,
that's
I!
Guess
that's
not
the
place
to
discuss
my
ability
to
to
move
forward
with
note
here.
B
A
A
Giving
back
on
topic,
assuming
my
meeting
load
this
week,
actually
looks
a
lot
better
than
it
last
week.
So
last
week,
I
was
only
able
to
get
started
on
this
ticket.
Assuming
the
azure
provisioning
with
terraform
of
the
post
receivable
database
goes
well
on.
My
fingers
are
crossed
that
everything
just
works.
The
way
that
the
documentation
says
it
should
be
straightforward
to
get
this
up
and
running.
I
might
need
some
help
from
Olivier
later
in
the
week
to
make
sure
that
the
migrations
container
is
running
correctly,
but.
A
It's
right
or
it's
right
around
the
corner.
Now
there
are
these
two
tickets
that
Mandy
had
around
getting
some
database.
Consistency
I'd
asked
her
to
try
to
get
that
incorporated
before
we
go
production.
So
even
if
I
have
the
Evergreen
Jenkins
io
online
by
the
end
of
this
week,
I
think
we'll
still
have
to
call
that
like
alpha
and
just
be
ready
to
blow
away
the
database.
If
we
need
to
yeah.