►
From YouTube: CNCF CI Working Group 2020-05-26
Description
CNCF CI Working Group 2020-05-26
A
A
A
B
B
A
B
Yeah,
I
I
I
already
put
this
as
a
placeholder
as
as
tracking
the
the
work
happening
on
cncfci
and
looking
at
the
respective
projects
which
are
there.
I
just
wanted
to
understand
a
little
bit
on
how
much
more
work
was
happening
and
also
in
the
tracking
of
what
works
or
what
doesn't
work
on
the
respective
projects
highlighted
into
the
ci
dashboard.
A
B
B
Yeah,
so
the
arm
team
is
is
still
progressing
work
around
the
kubernetes
conformance
testing,
as
you
know,
so
that
that's
work
which
is
progressing
and
there
are
other
components
of
cloud
native
elements
that
our
engineering
team
is
contributing.
Architecture
support
per
se,
but
not
so
much
focused
on
to
the
ci
elements.
B
The
tricky
part
is,
I
think,
how
to
monitor
when
things
fail.
Whether
the
failure
is
is
what
the
failure
is
attributed
to
whether
it's
particular
commits,
or
if
it's
an
architectural
issues
that
would
need
to
be
fixed
or
whether
it
is
something
else
which
is
elsewhere
in
the
code
and
which
just
resolves
after
a
few
additional
changes
in
the
upstream
code
base
right.
B
B
A
A
B
A
A
A
B
A
So
maybe
they
do
public
builds
of
arm
unstable,
but
not
on
head
so,
rather
than
having
it
all
internally
and
redoing.
The
build
systems
that
are
already
happening
try
to
help
projects
to
have
more
coverage
on
at
least
the
stable
versions
of
the
project,
projects
and
stable
versions
of
kubernetes
that
are
running
daily,
which
would
include
arm.
That's
the
goal
there
and
then.
C
A
C
C
A
Other
commits
and
other
things,
if
you
have
the
artifacts
from
the
sky,
builds
publicly
available,
then
we
would
like
to
pull
those
down
and
use
those
artifacts
for
deploy.
The
test
column
is
for
integration,
so
this
started,
as
I
was
saying
in
some
of
these
tough
and
the
tests.
These
are
actually
integrations
into
their
cia
systems
and
we
were
moving
towards
that
and
and
then
a
lot
of
the
focus
got
shifted
away.
A
A
C
C
A
B
A
B
A
B
A
A
B
B
Okay,
now
that
that
sounds
great
actually
and
in
your
discussion
with
some
of
the
projects
like
jaeger
and
similar,
which
you've
shown
the
proof
of
concept
on
x86,
have
you
also
discussed
the
arm
angle
with
them
or
and
if
you
have
or
planning
to
weaken,
we
can
participate
in
that
discussion
and
see
how
to
stimulate
interest
or
how
best
we
can.
We
can
support
that.
A
A
A
A
B
C
B
C
A
B
A
C
B
B
A
C
A
A
Testing
how
network
applications
for
telecom
are
following
cloud
native
principles,
and
this
actually
does
run
all
of
this
is,
is
a
test
suite
and
it's
running
in
travis.
So
what's
not
happening
or
what's
not
here
on
either
of
these
initiatives
is
a
dashboard.
But
theoretically
you
could
do
something
similar
and
say
we.
What
is
the
status
of
a
group
of
tests
that
you
care
about?
That
may
be
testing
a
certain
set.
A
So
if
people
are
interested
in
dashboards
outside
of
say
that
the
ci
system
that's
running
a
specific
project,
then
that
would
be
a
possibility
to
take
something
like
this
and
and
build
something
for
another
project
or
take
the
idea
and
have
it
refocused.
Maybe
we
don't
care
as
much
about
build
that
you
want
to
test
some
type
of
integration
between
projects.
B
B
B
A
B
A
B
A
A
Else
up
in
there,
but
in
the
last
couple
of
months
there's
been
a
few
mentions
on
different
slack
channels,
or
maybe
someone
mentioned
something
in
a
twitter
issue
related
to
a
build
problem,
and
there
will
be
some
someone
pointed
something
out
and
it's
noted
so
it.
I
guess
it's
somewhat
still
sane,
but.
B
C
C
A
We
need
we
need
to
decide
if
it's
going
to
go
forward.
Is
there
going
to
be
enough
interest
to
help
contribute
or
help
make
that
happen
so
that
we
can
bring
it
to
that
next
stage,
because
right
now
it's
in
this
in
between
with
core
dns,
is
doing,
builds,
running
the
test
and
then
building
the
artifacts
and
doing
the
deploys
envoy,
etc.
And
then
you
have
some
of
them
that
are
doing
integrations,
but
they're
only
we're
only
part
way
there.
So,
ideally
we'd
get
shifted
fully
over,
and
if
we're
going
to
put
in
that.