►
From YouTube: CNCF CI Working Group Meeting August 22, 2017
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
B
C
B
So
this
is
the
status
of
that,
so
it
was
successful
or
it
failed,
and
then
it
does
it
for
either
the
current
stable
release
or
it
does
it
for
the
hitch
on
master
and
then
each
cycle
furrow
we're
planning
to
have
these
cycles
for
every
six
hours
and
then
it
moves
on
to
the
deployment
stage.
Where
AWS
is
your
bluemix,
you
see
Jiki
packet
will
deploy
to
those
clouds
and
then
we'll
run
into
in
tests
to
verify
the
deployment
and
then.
A
B
A
deployment
here
which
is
a
more
defined
or
scope
view
of
the
deployment.
So
here
we're
looking
at
just
the
Prometheus
deployment
on
AWS
and
we
can
see
under
the
status
column
whether
that
job
succeeded
or
failed
and
in
the
show
half
of
the
binary
with
the
artifacts
that
it's
using
and
these
linked
upstream
github.
And
then
it
also
gives
you
a
prefix
of
the
branch
that
it
ran
on
or
whether
it
was
a
tag
or
a
stable
release
or
theater
version.
And
then
we
have
job
IDs
which
link
to
the
pipeline.
B
B
And
then
the
additional
marks
here
and
then
we
have
harvest
eight,
which
is
when
you
hover
over
success
badge.
It
will
bring
up
extra
details
and
we're
also
going
to
incorporate
some
features
so
that
when
projects
from
Cuban
it
is
down
which
are
actually
normally
deploying
on
top
of
the
Cubans
cluster,
if
the
Cuban
it
is
deployment,
fails,
they're
all
going
to
fail
are
going
to
get
aboard
of
red,
which
we
don't
want.
B
And
then
this
is
a
pipeline
here,
and
this
is
the
jobs
we
see
here
and
then
we
have
links
that
go
upstream
to
the
actual
job
and
then
we're
going
to
add
soldiers.
So
we
can
actually
filter
multiple
projects
on
particular
clouds
and
the
clouds
filter
which
allows
us
to
go
okay.
We
want
to
look
on
look
at
this
on
just
GCE
or
just
pack
it
or
we
could
do
all
of
them
and
then
status
ultra.
So
we
can
filter
a
particular
branch,
a
particular
release
or
all
the
succeeded
or
failed
jobs.
B
So
we
completed
a
demo
to
the
TSE
on
Tuesday,
August
15
and
then
there's
an
issue
on
github
which
we're
planning
to
respond
to
today
surrounding
integration
with
the
canonical
store,
which
they're
also
using
a
tariff
on
codebase.
So
it
would
be
nice
to
try
and
take
a
modular
approach
to
the
tariff
on
code,
so
other
people
can
use
it
and
we
worked
on
together
with
other
people.
B
B
And
we're
also
looking
into
ways
to
be
able
to
add
projects
without
crop
growing
changes
to
the
option
Rica,
which
is
when
running
jobs
with
the
gate,
Labs
VI,
Yemen
file.
It
has
to
be
in
the
reefer,
so
we're
actually
making
changes
now
to
be
able
to
make
that
external
and
it
does
not
have
to
be
in
the
repo
or
the
branch
to
be
able
to
do,
builds.
B
So
these
are
the
features
we're
trying
to
work
on
at
the
moment,
we'd
like
to
automate
the
gate
lab,
install
and
setting
it
up,
so
that
anyone
can
create
a
good
lab
instance,
and
then
it
will
automatically
clone
down
the
other
stream
cross
crowd
across
project
rivers
and
set
it
up
so
that
you
can
incorporate
your
project.
That's
what
the
CI
system
and.
B
B
B
C
Hi,
this
is
Erin
yeah
listed
as
sig
testing
I
continue
to
not
have
paid
much
attention
to
the
distance
I
apologize,
but
this
sort
of
help
me
catch
up
link
to
these
slides.
In
the
meeting
that
says
it's
not
there
already
would
help
me
broadcast
this
information
to
the
appropriate
folks
on
my
amp
and
I'm.
Also
trying
to
understand
are
you
using
github
issue
milestones
or
projects
to
sort
of
help
track
some
of
the
stuff
you've
presented
as
in
progress
I'm,
trying
to
get
out.
C
Got
that
my
thing
would
be
like
you
were
just
talking
about
how
Asher
is
coming
up
and
so
I
don't
see
that
on
either
the
project
boards
I,
don't
see
a
milestone
associated
with
it.
So
I'm,
assuming
like
it's
that
level
of
for
testing
what
the
roadmap
is
like.
What,
when
or
where
these
things
are,
your
lives
that
make
sense.
C
C
C
C
B
B
C
The
next
session,
but
being
able
to
look
at
the
agenda
and
see
what's
coming
up
would
also
be
helpful
to
maybe
get
more
interested
people
yeah.
A
C
I
could
give
you
a
concrete
answer.
There
I
may
have
even
said
this.
The
last
time
I
know
that
there
might
be
some
interest
in
understanding
how
or
the
ways
in
which
this
could
overlap.
With
the
conformance
testing
effort
around
kubernetes,
their
various
funding,
various
people
are
trying
to
figure
out
a
way
to
demonstrate.
The
picture.
Brunet
ease
cluster
is
to
form
it
and
help
you
put
together
a
tool
called
Santa
boy,
maybe
demonstration
of
something
cross.
Cloud-Related
that
uses
sana
boy
to
exercise
a
kubernetes
cluster
could
be
really
interesting
to
some
folks.
C
I
say
that
not
having
what's
too
closely
to
edit
myself,
but
it
seems
like
that
is
the
the
path
towards
actually
exercising
and
testing
conformance
of
the
kubernetes
cluster.
That
has
the
most
momentum
behind
it,
and
so
it's
on
invoice
just
basically
a
program
that
runs
the
kubernetes
and
add
tests
and
then
grabs
configuration
about
the
dumps,
the
various
kubernetes
resources
and
some
information
about
how
the
kubernetes
cluster
was
configured.
C
And
so
I
would
think
that
if
the
various
cross
cloud
deployments
that
come,
your
efforts
are
standing
up
if
they
are
compatible
or
can
be
scraped
by
sana
bleeding.
That
would
be
a
good
thing
if
they
can't
it
would
be
useful
information
to
understand.
Why
not
I'm
not
not
necessarily
sure
if
that
would
mean
that
this
is
a
gap
and
sound
of
voices,
humph
shion's
or
if
it's
a
gap
in
how
things
are
complete,
but
I.
C
C
A
The
conformance
testing
is
really
important
to
us
specifically
to
make
sure
the
kubernetes
all
the
kubernetes
clusters
that
are
deployed.
We
can
point
to
specific
releases,
have
feature
set,
what
the
compatibility
is
and
during
the
validation
of
the
conformance
tests,
is
on
the
forefront
of
all
that
yeah.
C
Totally
and
I
again,
I
haven't
looked
at
in-depth
it
as
set
of
scripts
that
you're
running
but
I,
believe
you.
You
essentially
end
up
running
the
e3
tests
with
a
regex
that
only
runs
tests
at
the
word
conformance
in
them,
which
is
effectively
housed
on
a
Bui.
Does
it
as
well?
So
it's
not
like
you
have
any
tests
that
live
in
your
codebase
you're
just
running
the
tests
that
live
in
the
kubernetes
codebase
using
artifacts
that
are
produced
by
the
kubernetes
project.
C
That's
all
cool,
it's
just
sauna
boy
seems
to
be
this
sort
of
extra
level.
On
top,
that's
attempting
to
provide
a
standardized
way
of
collecting
information
about
the
cluster
under
test,
so
that
the
end
result
is
that
somebody
could
take
a
look
at
your
test
results
and
your
configuration
and
reproduce
the
same
thing
on
their
side.
C
You
know,
jumping
up
and
down
wondering
why
this
is,
and
so
the
idea
is
because
Hana
buoy
is
collecting
additional
information
about
the
cluster
itself.
That
could
be
used
to
identify
that
this
open
shape
distribution
is
only
conformant
when
it
is
run
with
this
particular
container
engine.
This
particular
version
of
the
container
two
things
of
that
nature,
so
this
was
being
able
to
give
that
extra
introspection
or
metadata
about
the
clusters
that
are
set
up
by
cross
cloud
would
be
a
useful
demonstration.
C
C
C
A
We'll
be
in
LA
on
the
12th
for
the
upcoming
conference
and
if
anyone
is
there
feel
free
to
reach
out
alone
was
conveyed
up
in
LA
and
depending
on
how
the
conference
what's
what's
happening,
there
we'll
get
out
the
agenda
beforehand
and
if
there's
any
conflicts
and
are
in
cable,
letting
them
know
the
Roy's.
That
12
is
the
next
and
meeting.