►
From YouTube: CNCF CI Working Group 2019-10-22
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
CNCF CI Working Group 2019-10-22
A
Today
this
is
Lucina
and
welcome
to
the
sands.
The
FCI
working
group
call
will
give
folks
just
a
few
more
minutes
and
start
at
five
past
the
hour.
I'll
paste
into
the
zoom
chat
the
link
to
the
agenda
and
meeting
notes,
please
feel
free
to
add
your
name,
email
address
and
any
agenda
items
you'd
like
to
discuss
today.
A
A
A
We
don't
currently
see
on
the
call
he
wanted
to
touch
on
the
projects
that
run
on
arm
that
are
showing
on
the
scene,
C,
F,
dot,
CI
dashboard,
to
learn,
what's
preventing
each
project
from
going
to
green
and
what
reporting
may
help
assess
an
accelerate
progress?
There's
any
of
their
topics,
please
feel
free
to
add
to
the
list
it's
an
hour,
long
call.
So
we
should
have
plenty
of
time.
A
Cool,
so
some
upcoming
events
in
a
week
is
open
source
summit
in
France
the
scenes
the
F
dot
CI
initiative
does
will
not
have
a
presence
there,
but
we
do
have
a
keynote
from
Priyanka
at
gitlab.
So
if
anyone's
joining,
please
feel
free
to
add
your
sessions
if
you're
presenting
or
anything
else
that
you'd
be
interested
in
sharing
or
think
it's
worth
folks,
knowing
about
it
open
source
summit
this
month.
A
And
then,
of
course,
in
four
weeks,
q
con
cloud
Natick
on
North
America
is
happening
in
San
Diego
and
the
sand
sea
at
CI
dashboard
will
have
an
intro
and
a
deep
dive,
we're
also
interested
in
all
of
the
intros
and
deep
dives
for
the
scenes.
They
have
hosted
projects
if
you've
seen
the
Twitter
handle
at
C&C
FCI.
We
are
interested
in
your
topics
and
we're
sharing
them.
So,
hopefully,
you'll
have
good
attendance
at
UConn.
B
A
A
There's
some
co-located
events
at
Q
Klan
and
some
members
of
the
CNF
testbed
initiative
will
be
presenting
at
an
assembler
service
mask
on
that's
on
Monday
November
18th
and
it
is
sold
out.
But
there's
a
waiting
list
available.
You
can
click
through
in
the
meeting
notes
if
you're
interested
more
to
learn
more
about.
That
seems
like
there's
also
a
hackathon
hosted
at
qualcomm
on
Monday
the
18th.
So
that
looks
interesting.
A
C
B
C
A
That
sounds
great.
Thank
you
for
sponsoring
that
it's
like
a
nice
lead
up
to
Q.
Come
to
here,
yeah
I
think
the
acceptance
rate
was
12%
for
Q
calm.
So
it's
wonderful
to
have
another
outlet
to
hear
what
everyone's
working
on
the
next
scene
CFC.
Our
working
groups
coincide
with
holiday
weeks,
so
I'm
not
quite
sure.
A
B
B
A
A
A
A
A
We
has,
as
some
folks
on
the
call
may
know,
we've
added
armed
support
to
the
graduated
projects
on
since
the
FCI
builds
and
deploys,
and
in
June
we
wrapped
up
with
envoy
in
May
we
added
accordion
s
fluent
E
and
Prometheus,
pink
and
kubernetes.
We
also
have
had
a
large
effort
to
change
how
cube
spray
and
our
hardware
is
provisioned.
It
was
done
in
one
step
and
it
was
also
using
a
custom
solution
by
the
CNC
FCI
team
called
cross
cloud.
A
This
was
done
before
the
cube,
ADM
and
cube
spray
were
available,
and
now
that
those
are
available
community
tools,
we've
been
working
to
move
towards
using
cube
a
DM
cube
spray
and
in
the
near
future,
kinds
to
provision
accordion
s
for
the
same
CFC,
I
dashboard
and
our
release.
3.0,
which
was
released
on
Friday,
was
the
combination
of
those
efforts.
A
We
also
added
a
few
additional
enhancements
to
primarily
support
external
contributions
to
C
and
C
FCI,
we're
making
it
easier
and
documenting
the
steps
in
which
a
graduated
or
incubating
project
could
help
add
their
projects,
project
really
projects,
information,
release
names
and
build
status
and
then,
in
the
future,
near
future,
deploy
status
and
and
and
test
results
so
that
all
of
the
scene,
CF
hosted
incubating
and
graduated
projects
could
be
reflected
at
a
glance
on
CN
CF,
dots,
the
I
and
so
to
do
that
in
July.
We
started
adding
support.
A
B
A
Container
G
has
been
added
to
the
test
environment
area
of
the
dashboard,
we're
now
using
container
D
instead
of
docker,
and
we
have
in
planning
we're
planning
the
UI
change
on
how
we
can
see
container
G
there
icon
and
their
name
reflected
in
the
test
environment
and
currently
we're
using
the
stable
version
of
container
D.
And
we
would
like
to
iterate
on
that
in
future
versions
to
allow
the
user
to
configure
which
version
of
container
D
they'd
like
to
test
on.
So
in
the
test
environment.
A
We
currently
have
the
radio
button
options
for
kubernetes,
stable
or
the
latest
head
release
and
architecture
options,
x86
and
arm,
and
in
planning
now
and
I'll
share
I'll,
be
able
to
share
the
MOC
today.
I
believe
we're
also
going
to
have
a
column
for
container
D
so
that
the
user
will
be
able
to
see
that
we're
using
the
stable
release
now
and
the
head
release
will
be
n/a
for
our
MVP.
A
A
We
were
working
with
a
drop-down,
but
that
didn't
show
at
a
glance
what
the
test
environment
configuration
options
were
we're
hoping
now
that
this
UI
has
the
the
radio
buttons
you
can
toggle
between
stable
and
head
of
kubernetes
and
arm
and
x86,
and
see
which
projects
run
on
arm
and
see
the
provision,
the
test
environment,
provisioning
status
above
and
then
see
the
build
status
and
the
deploy
status
for
the
projects.
So
on
the
dashboard
you
can
see,
I
have
arm
selected.
The
graduated
projects
will
show
build
and
deploy
as
long
as
the
build
stage
passed.
A
A
So,
in
the
roadmap
this
month
we
have
released
3.0,
so
that
was
the
refactoring
of
our
provisioning
stage.
So
we
are
now
using
cube
spray
and
cube
ATM.
Instead
of
the
custom
cross
club
provision
or
tool,
we've
added
container
D
behind
the
scenes,
then
we
have
a
new
UI
to
show
that
that
container
D
is
in
use
for
our
next
release,
we're
using
the
latest
stable
and
upstream
kubernetes
artifacts.
So
another
big
improvement
is,
we
are
up
to
date,
showing
the
latest
stable
version
of
kubernetes
in
our
test
environment
and
we'll
be
adding.
A
So
our
goal
was
to
add
one
new
project
using
the
Travis
CI
integration,
at
least
one
new
project
and
we've
taken
a
look
at
Yeager's,
build
status
and
Travis
CI
and
we
are
getting
started
on
integrating
with
Jaeger,
so
will
be
you'll,
be
seeing
Jaeger
soon
under
graduated
projects,
in
alphabetical
order,
underneath
fluency
and
above
Prometheus,
and
we're
going
to
start
with
a
x86
architecture.
Support.
A
Next
month
and
I
think
this
kind
plug
in
we
may
need
to
defer
to
next
month,
so
we
wanted
to
make
it
easier
for
contributors,
external
contributors
from
the
CN
CF
hosted
projects
to
help
add
their
projects,
and
we
anticipate
adding
a
kind
plug-in
for
the
test
environment
provisioning
so
that
the
project's
can
have
access
to
their
own
cluster
while
testing.
A
So
that's
on
our
roadmap,
we'd
also
like
to
add
a
second
new
project
using
the
Travis
CI
integration,
which
appears
to
be
maybe
the
tests
or
Nats
and
we'd
also
like
to
create
a
circle.
Ci
integration
and/or,
a
second
CI
integration,
we'll
take
a
look
at
if
circle
CI
is
the
next
best
choice.
There's
also
been
we've
seen
a
shift.
A
A
So
if
you,
if
you're
involved
with
CN
CF,
hosted
project,
incubator,
graduated
or
assumed
to
be
incubated
or
graduated
and
you
are
using
Travis
CI,
we
welcome
your
attendance
we'd
love
to
get
your
feedback
and
participation
in
that
deep
dive
session
and
then
in
December,
we'd
like
to
add
another
new
project
using
the
circle
CI
or
the
next-best
CI
integration,
plugin,
we'd
love
to
collaborate
on
adding
and
to
end
test
and
and
test
results
to
the
dashboard.
As
currently
we
have
a
column
for
them
and
their
na.
A
A
C
So
I
wonder
how
you're
going
to
do
it
and
I
wonder
if
there's
some
useful
time
series
that
you
can
generate
that
would
help
us
rewind
the
clock
to
like
when
a
bill
that
used
to
be
green
turn
red.
When
was
that
I
know
you're
thinking
about
historical
data,
it
probably
doesn't
make
any
probably
don't
have
any
value
of
looking
at
something
a
year
and
a
half
old,
but
maybe
in
a
30
to
90
day
time
frame.
C
D
C
A
A
A
Currently
planning
add
new
project
with
Travis
CI
integrations
continuing
with
Jaeger,
and
the
roadmap
is
available
on
the
cross
cloud,
repo
in
github
for
the
most
up-to-date
version.
We
welcome
your
feedback
on
features
like
the
stateful
URLs,
as
well
as.
If
you
are
interested
in
adding
your
project,
we
can
help
you
get
started
with
that
and
any
other
enhancements
or
features
that
you'd
like
to
see
on
the
C&C
FCI
dashboard.
E
A
D
Part
of
the
goals
with
some
of
the
refactoring
for
that
the
CI
portion
and
see
I
integration
to
the
status
was
to
make
it
where
we
could
work
with
multiple
back
in
CI
systems.
So
Travis
was
the
first
mainly
because
the
project
had
it
just
happened
to
set
up
everything
kind
of
best
defaults,
and
we
want
to
keep
adding
Nance's
on
under
the
list,
but
primarily
because
it
was
Travis
and
we
were
looking
at
adding
it
next.
D
E
D
C
E
D
F
A
D
A
Thank
you
so
much
yes,
and
in
our
roadmap
we
we
didn't
see
the
move
to
your
github
actions
happening
I,
think
when
we
created
the
roadmap,
and
so
now
that
that
has
happened.
We
started
with
Travis
CI
and
hopefully
we'll
have.
Hopefully,
Jaeger
is
staying
on.
Travis
CI
a--
will
have
to
reach
out
to
them,
and
if,
if
more
projects
in
the
graduated
incubating
level
are
moving
over
to
github
actions,
then
we
may
switch
the
priority
of
the
next
CI
system.
A
Thank
you
so
much.
That
concludes
my
updates.
So
there
are
lots
of
ways
to
get
connected
with
the
scenes.
The
FCI
team
on
github
we're
under
our
old
name
cross
cloud
CI
on
Twitter,
since
the
FCI
there's
also
a
scene
CF
CI
slack
channel
under
the
scene,
CIF
org
and
you
can
also
email
us
at
CFC,
I,
add
Volk
co-op.
C
What
have
you
and
I
think
that
when
builds
fail,
of
course,
there
could
be
hundreds
or
thousands
of
reasons
for
a
build
to
fail,
but
I
think
it
would
be
helpful
to
think
through
and
put
on
the
roadmap
at
some
at
some
level
along
the
way,
some
kind
of
best
next
step.
If
things
go
wrong
so
that
an
issue
could
be
properly
raised
in
a
channel,
that
would
be
welcome
to
get
it,
whether
that
be
a
slack
channel,
whether
that
be
github
or
a
git
lab
or
what-have-you
issue
tracker.
What
what
have
you
and
I'm?
A
Thank
you.
We
were
just
talking
about
that
today
and
yesterday,
when
we're
talking
about
how
can
we
engage
external
maintainer
Xand?
How
can
we
engage
the
same
CF
projects
for
both
adding
and
maintaining
the
projects
on
the
same
CF,
CI
dashboard
so
and
we're
also
internally?
We
are
working
on
our
monitoring
and
our
alerting
as
well.
A
A
So
that's
a
good
point
like
how
do
we?
How
can
we
visually
see
that
this
is
the
build
status
from
the
projects
and
it
failed,
and
how
can
we
alert
them
in
case
they
didn't
notice,
or
in
case
they
are
not
aware,
and
then
there
are
some
cases
where
we're
in
the
process
of
change,
and
there
are
some
action
items
that
we
need
to
take.
So
with
that
in
mind,
Denver
or
Taylor,
do
you
have
any
ideas
on
why
things
would
be
failed
for
first
and
then
how
we'd
want
to
engage
beyond
a
github
issue.
D
Right
yeah,
unfortunately,
in
the
current
version
of
get
lab
adings
any
type
of
additional
information-
it's
not
built
in
there
may
be
plugins
or
something
but
yeah
I've.
It's
a
little
bit
easier
to
associate,
build,
builds
and
other
things
even
like
Travis.
You
can
you're
looking
at
a
felt,
build
and
then
I
go
to
commit
and
start
linking
everything
back
and
the
issues,
but
there's
some
problems
with
get
lab
on
that.
D
So
I'd
say
that
first
iteration
is
to
make
sure
that
whatever
you're
saying
in
get
lab
is
very
visible
and
in
this
CNC
FCI
issue
board,
so
that
people
can
drop
the
probably
the
the
URL
so
you're.
Looking
at
that
job
number,
you
should
be
able
to
search
for
that.
If
you
scroll
to
the
top-
and
you
have
the
title-
and
you
should
have
that
information-
you
said
this
is
a
job
that
anyways
it's
the
pipeline.
I
think
I
was
singing
it.
So
the
if
we
have
that
information-
and
you
know
add
you're.
D
Looking
at
this
and
you're
able
to
hop
over
and
search
in
the
in
the
century.
Is
you
board,
and
you
say:
ok,
we
have
this
I
know
it
looks
like
we've
added
five
jobs
and
it's
an
internal.
It's
an
issue.
You
know
maybe
that
we're
migrating
to
the
new
infrastructure.
Then
ok,
that's
fine,
it's
at
least
known
or
if
there's
something
like
Denver
matters
today,
where
there's
an
upstream
issue
on
a
project
with
the
build
changed
and
waiting
on
that
fix.
D
Maybe
we
don't
have
to
do
that,
but
I
think
the
searching
is
the
first
part
what
what
I
was
saying
earlier
on
this
screen
that
Lucina
showing
right
now
there's
no
real
way,
unfortunately,
that
we
can
like
annotate
or
add
additional
info.
If
you
go
look
at
the
list
of
jobs
or
the
list
of
pipelines,
it's
pretty
minimal
and
we've
had
similar
issues
just
internally
that
we've
wanted,
where
we'd
love
to
be
able
to
annotate
the
pipeline's
and
say
this
is
for
x86.
D
Thank
you,
Burnett
YZ
114.
You
can
see
it
there
if
you
go
and
look
at
those
release,
stills
information,
so
we
could
potentially
put
some
stuff
in
here,
but
this
is
all
beforehand
so
that
stuff
that
Lucian
is
showing
you
can
see.
It
says
the
project
and
the
organization,
and
we
have
a
lot
of
other
information
but
actually
annotating
after
the
job
is
I
Denver
Dino.
If
we
can
update
the
environment
variables
after
a
job
is
run,
know
for
the
week,
yeah
I
didn't
think
so.
F
D
Queue
is
to
have
the
status
buttons
on
the
dashboard
when
you
click
them,
instead
of
it
going
to
the
job
that
Lucina
was
just
showing.
If
you
click
one
of
these,
it
would
go
to
the
CI
system.
So
for
Nats,
when
we
get
that
fun,
it
would
go
to
Travis
if
you're
still
on
Travis
or
it
would
go
to
the
Google,
CI
and
link
your
d
would
be
that
be
adding
Jaeger
and
once
we
have
Jaeger,
ideally
that
will
go
to
the
Travis,
CI,
etc.
C
Thanks
Taylor
I,
think
that
illustrates
some
of
the
challenges
of
direction
and
indirection
in
these
sort
of
systems
and
I
mean
I'm,
confident
that
if,
if
I'm
confused
I
can
always
hit
the
open,
a
bug
thing
at
the
bottom
of
the
screen,
and
even
if
it's
not
the
perfect
place
to
note
something.
It
is
a
valid
place
to
note
something
and
we
can
help
chase
down
the
best
place.
To
know
that
after
the
bug
has
been
described
in
some
kind
of
useful
way.
D
Yeah
for
sure
opening
a
bug
based
on
a
failed
job
sounds
great
and
then,
if,
if
there's
a
duplicate,
then
we'll
roll
that
one
in
and
or
if
it's
if
it
looks
like
it's
the
same
as
another,
and
of
course,
if,
if
you
see
that
okay,
it
looks
like
this
one
was
the
same
as
we
had
three
days
ago,
because
you
notice
it
and
I'm
adding
the
job
again
seems
reasonable.
So
as
comments
I
felt
again.
C
D
D
If
the
dashboard
showed
that
and
then
you
see
the
felled
job
and
you
have
a
maybe
a
link
over
to
the
actual
issue.
That's
open
and
I
think
that
would
be
something
possible
if,
if
we're
saving
data,
it
doesn't
really
make
sense
if
it's
disappearing
every
day,
because
the
only
place
again
is
get
lab
and
that
that
doesn't
really
work
out
whenever
we
and
we
start
moving
to
having
the
links
go
directly
to
the
project
CI
systems.
D
So,
ideally,
we
have
some
type
of
some
layer
above
which
is
where
we're
going
with
historical
data.
But
the
reason
why
we
have
the
status
repository.
It's
it's
in
front,
so
all
of
the
data
that's
showing
right
now
on
the
dashboard
doesn't
come.
It
originates
directly
from
a
status
repo
and
what
we
need
with
that
is
just
save
the
data,
and
then
we
could
start
annotating
and
adding
additional
information.
D
A
C
A
It
certainly
does,
when
we
have
any
configuration
either
stable
in
x86
table
arm
head
x86
or
head
arm
that
fails
the
provisioning
stage.
Then
the
all
of
the
deploy
will
be
na.
So
we
want,
we
wouldn't
even
try
it
so
having
the
successful
test
environment
provisioning
ensures
that
we
have
more
active
badges
in
our
deploy
column.
A
A
A
Lets
us
know
that
we'll
hold
on
adding
the
Travis
CI
integration
for
Nats
and
and
we'll
take
a
look
and
we're
excited
to
see
how
you're
enjoying
the
github
actions
how
it's
working
out
for
you
and
then
we'd
like
to
circle
back
and
see.
If
the
github
actions
is
the
next-best
CI
system
that
we
should
be
focused
on.