►
From YouTube: Essentials: Open Planning Meeting (2018-07-10)
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
Welcome
to
the
Jenkins
essentials,
open
planning,
meeting,
I
think
Mandy
may
not
be
joining
us
today,
because
she's
indisposed
so
might
just
be
Patti
Smith.
So
this
will
be
pretty
quick
sue.
Batiste
I
was,
and
I
was
in
here
last
week
so
and
just
I
saw
some
work
that
y'all
had
y'all
had
done.
But
could
you
just
give
me
an
overview
of
what
you
and.
B
B
C
So,
basically,
last
week
the
main
thing
that
was
done
was
to
finish
and
get
in
the
merging
of
the
healthiest
flavors.
So
it's
now
available
and
working
so
using
the
online
to
use.
Let
me
just
cloud
formation
to
provide
and
provision
everything,
so
I
filed
issues
around
and
so
we've
been
having
some
kind
of
discussions
and
work
around
configures
code,
artifact
matter
as
three
plugins
easy
to
plugins
and
many
things
like
because,
for
instance,
for
now,
I'll
add
two.
C
C
Now
yeah,
that's
the
one
and
there's
somewhere
a
reference
to
non-going
ticket
were
actually
on
which
paid
by
the
way
I
find
PR
this
morning
on
not
a
fixed
PR,
because
I
didn't
have
time
and
more
than
sure
I
would
like
I
would
I
would
be
the
one
to
spend,
spend
time
on
fixing
or
making
a
fact.
Neither
as
three
plugins
and
configures
can
work
together,
but
at
least
I
found
a
PR
showing
that
that
don't
work
together
globally,
totally
and
so
ii.
C
Think
the
thing
I'm
now
on
is
so
this
morning
I
file
the
PR
and
sent
an
email
to
detail
amenities
to
gather
feedback
around
and
it
worked
the
around
WS
autocorrection.
So
that's
that's
the
check
summarizing
what
I
actually
did
in
in
the
prototyping
PR
and
now.
The
next
thing
I'm
going
to
jump
on
is
the
the
the
long
hoped
one
or
so
one
of
the
the
one
that
made
our
just
some
kind
of
so
somehow
flaky,
sometimes,
which
is
the
retry
failure
film
feature.
C
Hopefully
it
will
make
our
runs
over
in
locally
and
in
CI,
more
stable,
because
sometimes
just
failed
and
it
doesn't
retry.
So
everything
is
just
you
have
to
restart
the
CI
build
and
so
on
and
yeah.
That's
that's
that's
for
me.
If
you
have
any
questions,
I'm
happy
to
take
into
something
specific
or
for.
A
A
Good
right
now,
the
the
client
is
using
this
module
called
node
fetch
where,
as
our
acceptance
tests
in
the
in
the
services
side
are
using
a
module
called
request
and
request,
promise
I
think
it
might
make
sense
to
get
just
changing
the
client
over
to
use
request
promise
rather
than
node
fetch.
There's
no
such
looks
like
it's
a
very
simple,
very
simple
API,
because
it's
really
it's
implementing
in
API,
supported
by
browsers,
called
just
fetch,
which
is
relatively
I,
don't
want
to
say
primitive,
but
it's
just
not
as
advanced
as
it
could
be
yeah.
C
I,
imagine
that
that
the
code
will
look
like
some
some
kind
of
lambda
using
request
promises
and
so
on,
like
high
level.
A
programming
model.
Well
can
just
say:
okay,
that
premiere
should
be
you,
try
it
five
times
and
before
we
haven't
done
or
something
and
then
so
yeah.
That's
our
image
in
the
codes
which
will
look
like
that
yeah
one.
A
Of
the
things
that
I
think
would
be
worth
experimenting
with
is
there's
different
types
of
exceptions
that
will
we'll
go
into
the
catch
state
for
a
promise.
Not
all
of
them
are
download
failures.
For
example,
a
404
is
not
a
retrial,
at
least
in
my
opinion.
404
would
not
be
a
retrial
error
or,
if
you
had
a
syntax
error
in
your
in
your
promise
or
the
function
being
executed
by
your
promise.
That
would
also
not
be
a
retrial
error
yeah
for.
C
C
A
D
C
B
C
From
some
G
Rowling
from
so
that's
another
one
that
just
so
that
tells
that's
just
one
you
stumble
into
it.
The
remove
port
50,000
is
interesting
because
it's
actually
been
triggered
by
the
feedback
of
someone
from
the
community
Daniel
cada
yeah
I'm,
the
jet
PR.
So
that's
that's
one
of
the
good
thing
about
you
know
submitting
concepts
for
public
reviews
and
and
fetching
issues.
C
A
A
D
D
I
would
refactor
it
slightly
before
merging
it
right
now.
It's
a
little
bit
hacky
and
I
would
want
to
make
it
more
of
a
sort
of
standalone
library
that
we
would
use
as
opposed
to
having
it
like
integrated
folium
with
the
code.
The
way
it
is
right
now,
but
if
we
want
me
to
move
in
that
direction,
I
can
go
ahead
and
have
that
done,
probably
today
or
tomorrow.
What.
D
A
D
B
A
C
C
D
A
That's
something
that
you
would
be
able
to
tackle
this
week.
That
would
be
ideal
is
for
me.
I
need
to
continue
continue
on
this
ticket
around
deploying
the
back-end
services
to
Evergreen
that
Jenkins
I/o,
which
means
I,
would
be
provisioning
the
Postgres
database
to
assure
to
actually
run
the
evergreen
services.
A
A
So,
for
me,
I
was
out
obviously
last
week
and
this
week,
isn't
all
that
free
and
clear
as
far
as
my
talent
is
concerned,
but
these
two
tickets
right
up
at
the
top
the
pusher
service
and
then
deploying
evergreen
at
Jenkins
I/o.
Those
are
the
top
two
priorities
for
me
from
a
Jenkins,
essential
standpoint,
they're,
both
fairly
straightforward,
where
I
left
off
with
the
pusher
service
is
with
feathers.
We
have
a
fairly
strong
event
system
so
where
it's
easy
for
the
four
feathers,
which
is
the
the
framework
that
powers
our
back-end.
A
It's
easy
for
that
to
just
admit
events
over
a
socket
to
connected
clients
like
the
Evergreen
client,
for
example,
and
so
I've
done.
The
initial
research
on
that
I
didn't
make
it
coming
in
here.
So
that's
my
bad,
and
but
it
looks
like
that
will
work
to
where,
whenever
we
have
an
update
level
created
in
the
back-end
services,
we
would
just
like
feathers
is
already
actually
admitting
a
created
event,
and
we
just
need
to
expose
that
over
a
second
to
the
client
and
make
the
client
actually
do
something
meaningful
with
it.
So
that's
that's!
C
A
So
I
think
next
week,
Amanda
or
Mandy.
Sorry,
and
what
would
be
nice
to
sort
of
be
prepared
to
do
is,
if
you
can
demo
some
of
the
Sentry
integration
next
week,
I
think
that
would
be
cool
and
then
bits,
East's
and
I,
don't
know
how
far
along
we
will
be
but
being
able
to
demo.
Some
of
the
launch
on
AWS
I
think
would
be
really
cool.
C
B
C
A
C
A
C
A
C
Another
case
just
a
few
minutes
earlier
about
what
I
would
like
to
have
it
available
there.
Definitely
it's
definitely
broken.
So
there
was
something
about
evolution,
testing
which
I
can't
file
PR.
You
know
incremental
incremental
SC
leaf
Iong
blue
ocean,
which
would
help
but
yeah
I
can't
do
that
and
I've
been
doing
that
and
even
on
ec2,
but
it
was
actually
moot
because
yeah
it
was
broken,
so
nothing
got
deployed
by
the
way,
I'm,
not
sure
it's
normal.
If
the
deployments
you
know
we
still
green,
everything
is
looking
like
it's
okay,
when
it's
you
know.
C
A
A
So
the
plan
that
I
have
today
and
when
I
considered
this
to
be
a
higher
priority
than
than
the
other
tasks
that
I
had
reference.
We've
got
the
parallel
infrastructure,
I'm
gonna,
convert
the
pipeline
library
and
to
use
that
parallel
infrastructure
and
continue
the
support
process
without
her.
But
we
should
we
should
be
unblocked
within
the
next
hour
or
so
because
they
just
need
to
switch
some
URLs
after
I
verify
that
they
are
working
correctly
great
yeah.
Apparently
this
I
mean
I'm
glad
you
filed
the
ticket
for
this
pretty
stupid.
B
C
A
We
we
use
Azure
functions
within
the
Jenkins
project
for
some
little
bits
of
community
automation.
It's
quite
hopeful
for
doing
little.
Webhook
based,
you
know
it's
a
logic,
but
in
this
case
the
things
that
are
working
against
us
is
we're
using
a
newer,
a
sure,
runtime
or
Azure
function
in
runtime,
because
we
needed
node
8
or
later.
B
A
There's
like
Java
5,
its
battle-tested,
yeah
or
or
older
yeah,
and
this
this
function
also
takes
a
little
bit
longer
to
execute.
Then
the
usual
runtime
is
around
one
minute,
just
because
we
have
to
download
data
and
upload
data,
and
things
like
that.
Ok,
if,
if
this
happens
again,
I
think
I'm
gonna
early,
this
sort
of
behavior
happens
again.
I'll
have
to
look
into
alternative
deployment
mechanisms
for
the
incrementals
publisher,
but
don't
keep
you
all
updated
on
that,
because
it
is
pretty
critical
to
Jenkins
essentials
somewhat.