►
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
Yeah
they'll
be
good.
I
noticed
that
somebody
has
been
updating
the
meeting
notes
for
today.
C
C
C
Great
just
I
took
the
liberty
of
putting
a
bunch
of
things
on
the
rcmd
document,
the
agenda
for
today
yeah
but
feel
free
to
point
out.
If
there
is
something
that
you'd
like
to
discuss
for
the
story,
I
missed
at
the
previous
meeting.
So
I
know
there
was
a
discussion
about
generating.
C
Okay,
I'll
just
go
ahead
to
stop
me
if
not
making
sense.
Okay.
The
first
thing
I
wanted
to
mention-
I
guess
everyone
here
already
knows-
is
that
we
picked
the
name
for
the
protocols.
It's
cd
events
and
the
dns
name,
though,
is
still
not
defined,
so
we
have
cd
events
or
event
cd
and
yeah,
so
we
need
to
check
which
one
is
available
and
which
not,
and
we
asked
the
cdf
for
help
that.
B
Is
this
cd
is
the
dns?
Is
that
one
you're,
the
one
you
type
in
the
browser.
C
Yeah
yeah,
basically
yeah.
C
Yes,
on
the
cloud
event
binding,
the
event
should
be
a
reverse
dns.
So
in
that
sense
I
think
events.cd
would
be
my
my
favorite.
I
steve.
D
B
I
eventually
so
stupid
question
there
would
be.
Would
people
think
this
is
like
events
happenings
in
this
in
the
city
domain,
or
do
they
want
to
use
that
for
kind
of
like
those
type
of
events,
summits
and
so
on?.
A
D
A
C
C
And
I
think
stevie
mentioned
that
we
don't
want
to
do
double
work
and
buy
a
domain
and
someone
names
and
then
transfer
it
to
the
cdf.
So
hopefully
we
can
get
help
from
from
there
too,
to
get
this
registered
by
the
cdf
directly
or
the
linux
foundation,
or
this
yeah,
and
once
we
have
the
domain,
we
should
probably
update
our
documentation
and
sdk
and
everything.
But
maybe
we
can
wait
until
we
have
a
finalized,
dns
name.
D
And
one
thing
on:
once:
we
get
the
domain
name
and
we
want
to
stand
up
a
basic
website
along
underneath
that
I
would
recommend
using
hugo
and
doxy
as
the
markdown.
D
C
We
have
a
new
github
arc,
which
is
called
city
events,
and
we
asked
the
cdf
also
for
help
with
the
logo.
Design
has
to
have
a
nice
logo
and
they
sent
back
a
creative
brief,
which
is
this
google
doc
and
I
started
putting
something
on
it
and
I
think
someone
else
added
ideas,
but
yeah,
I
feel
free
to
contribute
to
it.
I
think
once
we
fill,
we
have
a
satisfactory
status,
we
send
it
to
the
cdf
and
I
guess
it's
an
integrative
process.
C
C
Okay,
anything
else
on
the
name.
C
All
right
next,
I
wanted
to
briefly
talk
about
the
relocation
to
destiny.
Events
org,
I
guess
we
created
a
ddr
in
the
github
we
kind
of
assumed
gita
is
the
hosting
service.
I
just
wanted
to
put
the
question
there.
We
want
to
use
github
or
gitlab,
or
else
both
as
a
kind
of
replication
mechanism
in
place.
C
I
think
github
is
good
for
at
least
for
a
starting
point
just
wanted
to
ask.
I
think,
maybe
concern.
D
I
would
just
stick
with
github,
since
that's
what
most
of
the
cdf
projects
are
under.
C
C
Yeah,
I
I
agree:
okay
with
that
out
of
the
way,
so
in
terms
of
free
pause,
my
recommendation
would
be
to
kind
of
follow
what
cloud
events
do,
which
I
think
looks
nice
and
makes
sense
so
to
have
like
a
spec
document
which
would
map
what
we
have
in
the
vocabulary:
draft
folder
in
our
sync
events.
So
we
basically
host
this
back
there.
C
We
could
use
the
spectre
for
other
documents
like
a
community
nd
or
governance
nd
as
well,
or
we
could
create
a
community
repo
if
you
want
to
and
then
we
could
have
sdk-star
repos
for
various
sdks
and
eventually
you
could
have
one
repo
for
the
website
hosting
containing
basically
the
doxy
and
whatever
documentation
we
want
to
put
there.
D
Yeah
that
that
sounds
good
one
question
on
the
license.
Does
anybody
mind
if
we
just
use
use
apache
2
for
everything.
C
I
think
it's
we
had
this
discussion
before
for
the
sig
events,
repo
and
I
think
most
of
the
places
apache
2
is
used
and
I
think
for
consistency.
It
makes
sense
to
to
use
apache
2
unless
anyone
is
concerned.
D
I
just
know
when
you
start
creating
repos,
that's
one
of
the
things
we
got
to
make
sure
we
just
drop
in
there.
C
All
right
good
point
for
the
poc:
that's
a
folder
in
these
events,
repo,
I
thought.
Maybe
it
would
make
sense
to
have
one
repo
with
all
the
plc's
one
reaper
per
plc
in
the
new
arc.
I
don't
know
you
could
leave
it
in
the
sick
events.
C
E
D
Repo
would
work
best
because
then
you
can
have
the
read
me
kind
of
explain
what's
in
the
repo
and
where
to
find
things
instead
of
jumping
around
to
different
repos.
B
How
does
cloud
events
do
this?
Do
they
have
any.
B
And
we
could
have,
I
don't
know
if
this
good
idea,
but
we
could
have
something
called
experimental,
for
example,
where
we
put
all
the
extra
experimental
stuff.
What
were
you
doing.
D
I
think
I
think
for
like
you're
saying
for
the
the
poc
side
of
things
that
we
mean,
like
you,
have
experimental
at
that
level
like
we're,
trying
out
a
new
like,
for
example,
the
deployment,
a
deploy
vocabulary
that
may
fall
under
an
experimental
part
of
the
poc.
C
Right,
yeah
and
I
think
for
the
for
this
pack,
I
have
one
bullet
point
underneath
it's
from
afterwards
b01.
C
Maybe
we
we
can
have
a
general
discussion
in
life
today
about
how
we
want
to
handle
versioning
what
it
means
to
a
certain
version
number
and
what
kind
of
stability
we
we
provide.
So.
C
C
We
have
some
code
that
we
wrote
for
the
poc
some
adapters
for
captain
and
also
an
experimental
controller
for
tecton.
Do
we
want
to
gather
those
into
our
organization
or
let
them
try
to
maybe
move
them
into
target
organization?
I
mean
the
the
techno
one
is
already
on
the
tecton
cd.
C
The
captain
of
adapters
are
under
mauricio's
own
account
right
now
we
don't
have
to
decide
today
it
was
just.
We
just
wanted
to
bring
it
up,
and
if
someone
has
ideas
we
can
discuss.
E
For
this
I
feel
like
as
a
user.
It
makes
more
sense
if
it's
inside
the
same
like
repo
for
cd
event,
so
inside
maybe
like
experimental,
someone
can
come
and
check
out
the
poc,
and
then
you
know
all
of
the
information
for
that
that
adapter
code.
B
Yeah
also,
it
could
be
good
to
have
it
collected,
because
currently
it
is
a
little
bit
of
a
kind
of
like
I
don't
know.
A
cumbersomeness
is
that
when
he's
trying
to
set
up
the
poc,
you
need
to
download
these
ones
separately.
B
So
it
could
be,
for
example,
that
you're.
I
think
it
would
be
good
that
everything
in
the
plc
is
collected
at
once,
because
I
did
actually
run
into
an
occasion
when
I
had.
I
had
to
pack
a
puck
up
and
running,
but
then
it's
I
had
to
redo
some
things
and
it
didn't
work.
C
D
On
the
techdown
side,
how
did
with
the
catalog
and
the
techton
hub
is
that
bringing
in
like
tasks
and
pipelines
from
different
organizations?
D
So
if
I,
let's
say
from
the
or
to
the
side,
if
I
wanted
to
contribute
something,
would
I
contribute
into
that
repo,
or
would
I
have
my
own
repo
where
people
would
go
get
it?
You
know
how's
the
how's,
the
organization
kind
of
handled
when
you
want
to
when
we
start
having
more
outside
people
contributing
to
this
that
you
found
that
makes
the
easiest.
C
Right
for
task
on
texas
side,
we
have
a
different
level
of
support
if
you
will
so
there
are
some
of
the
the
tasks
that
are
supported
by
the
detecting
community
and
they
provide
like
automated
testing
so
that
it's
it's
verified
other
tasks
in
the
catalog
that
can
be
contributed
by
anyone
and
depending
on
how
the
level
of
commitment,
so
if
they
want,
if
they
set
up
the
same
level
of
ci
and
testing,
then
they
get
the
same
level
of
kind
of
validation
as
the
community
wants,
and
you
can
also
have
tasks
in
outside
repos.
C
So
the
hub
technically
supports
displaying
tasks
from
multiple
catalogs,
so
the
catalog
is
a
git
repo
and
the
hub
is
the
web
interface
and
the
web
that
you
can
configure
it
to
pull
the
task
from
multiple
repos.
So
today
it
only
pulls
tasks
from
one
repo
but
yeah.
It
could
pull
from
more
repos
in
future.
Or
if
you
have
your
organization
and
you
have
your
own,
then
you
can
collate
tasks
from
how
many
catalogs,
as
you
want.
D
D
D
I
think
we
need
to
flush
it
out
more,
but
it
it
feels
kind
of
that
we'd
have
a
catalog,
because
you
know
if,
for
example,
if
somebody
wants
to
find
some
events
around
security
that
they
would
be
able
to
go
to
the
catalog
and
find
out
what
adapters
are
out
there,
that
implement
security,
the
security
vocabulary,
so
they
can
either
use
that
example
or
bring
those
in
to
their
pipeline.
For
example,
you
know,
so
it's
just
a
easy
way
to
find
things
is
what
I'm
thinking
about
down
the
down
the
road.
D
Like
you
said,
we
don't
have
to
decide
these
today,
but
that's
kind
of
what
it
it
looks
like
to
me
from
now.
From
this
point
of
view,.
C
Right
now,
yeah,
I
I
agree,
I
mean
I
think
it
makes
sense
to
have
at
least
one
central
place
to
discover
all
these
things
like,
like
you
said
so
you
you
want
to
use
a
certain
type
of
events
that
you
want
to
see
where
you
have
adapters
for
in
terms
of
actually
storing
the
codes
having
one
central
repo
might
have
some
organizational
issues.
I
think
because
then
you
have
approvers
for
that
people,
and
but
it
depends
how
you
set
things
up,
but
yeah
we
can.
We
can
solve
that
as
we
go.
B
I
mean
as
long
as
it's
easy
to
to
use
it.
It's
not
a
problem,
but
currently
as
the
pockets.
You
need
to
clone
three
different
repositories
to
a
certain
path,
and
so
it's
kind
of
like.
If
there
is
an
install
or
something,
then
you
can
have
a
different
repos,
but
it's
more
for
you
know,
ease
of
doing
something.
C
Yeah
yeah
yeah,
we
could,
we
could
add
some
automation
into
the
pse
or
we
could
even
try
to
make
the
current
script
more
like
a
framework,
so
you
can
decide
which
parts
you
want
to
pull
in,
but
yeah.
That
would
be
some
extra
work,
but
I
think
we
it's
fine
to
start
with
the
experimental
repo
in
the
org
and
we
could
pull
the
code
in
there.
B
B
C
C
B
Yeah
well,
I've
come
across
it.
Sometimes
when
I
read
it
so
I
wanted
to
mention
it
but
yeah.
Well,
if
I
got
the
time
I
could,
but
I
won't
promise
something
sure
sorry.
C
Cool,
if
fox,
wants
to
be
added
to
the
orc
free
to
sign
yourself
in
or
send
me
a
message
with
your
email.
If
you
don't
want
your
email
to.
D
C
Written
in
here
make
sure
everyone
is
added
to
the
org.
C
All
right,
the
other
thing,
then
we
discussed
during
the
last
kind
of
sig
meeting
about
jenkins
and
cd
events
and
text
on
possible
pocs,
and
so
I
wanted
to
to
discuss
this
today
so
make
sure
to
join
the
meeting.
So
maybe
we
can
have
a
discussion
on
these
and
make
plans
for
a
potential
plc
that
would
involve
jenkins
as
well
similar
to
the
one
that
we
have
done
with
tactile
men.
C
And
yeah,
so
I
think
one
thing
that
I
wanted
to
to
capture
here
is:
what
kind
of
events
does
jenkins
said,
and
how
does
this
match
to
existing
cd
events
and
the
buckets
that
we
have?
E
Yes,
so
let
me
share
the
link
to
the
repository
between
all
of
the
events
and
I
can
also
share
my
screen
and
walk
through
the
events
which
are
currently
supported.
E
So
at
the
moment
we-
and
this
is
also
part
we
like
this-
is
participating
in
hacktoberfest
and
there
is
an
issue
to
add
more
sort
of
like
events
which
are
supported
in
like
the
pipeline,
but
as
a
whole.
The
parents
supported
our
cue
events,
so
when
a
job
is
entering
the
queue
or
when
a
job
is
left
to
queue.
So
again,
this
is
like
a
single
job
existing
by
itself.
E
There's
some
build
events
for
when
a
job
hasn't
started
or
it
is
completed
or
it's
in
the
in
the
finalizes
state,
and
I
think
this
was
more
so
when
we
were
picking
up
events
on
what
to
choose.
I
think
what
came
into
mind
was
the
more
relevant
events
which
would
make
like
designing
systems
on
top
of
each
other
more
easy.
So
you
know
if
a
job
is
completed,
you
would
ideally
want
to
trigger
something
else
in
a
different
cd
system
or
when
a
job
is
finalized
or
a
job.
E
Yeah,
so
completed
will
be
sent
out
when
they're,
basically
like
two
stages,
so
the
event
completed
is
only
sent
out
when
it's
successful
and
finalized
will
be
sent
out
like
either
way.
If,
if
a
build
is
successful
or
if
a
build
is
failed
or
if
it's
still
in
the
pending
stage,.
C
E
Yes
and
then
fail
is
being
sent
separately
as
well.
So,
for
example,
if
someone
is,
they
have
a
job
and
the
job
was
built,
but
they
only
really
want
the
failure
when
they
they
do
not
care.
When
it's
ended,
they
really
only
got
the
fail.
E
So
that's
when
this
event,
like
the
field
will
be
sent,
but
if
they
also
want
to
know
the
time
between
the
event
being
completing
or
like
that
particular
job
competing
in
the
job,
failing
that's
when
they
would
want
to
use
finalize
so
there's
it's
it's
a
tiny
bit
of
a
difference,
and
I
think
we
need
to
make
it
like.
I
need
to
add
some
more
detail
on
the
difference.
That's
a
really
good
point.
E
And
and
then
there's
the
job
event
for
if
a
new
job
was
created
or
updated
and
and
possibly
like
deleted
and
and
the
known
events
for
want
to
note
is
online
when
a
node
is
offline,
and
there
are
some
more
note.
Events
for
you
know
like
an
agent
is,
let's
say,
like
added
to
a
queue
or
if
an
agent
is
in
the
waiting
stage,
and
not
all
of
that
stuff
like
that,
but
right
now
these
are
the
events
which
are
supported
and
moving
into
like
the
future
of
maybe
like
a
month
or
so.
E
There
is
a
plan
to
add
more
pipeline
events,
so
when
something
is
moving
between
stages
of
pipelines
from
one
stage
to
another
stage
or
when
one
stage
has
failed,
so
that's
going
to
be
a
bit
different
than
individual
events.
E
C
C
Yeah
yeah
pipeline
task,
I
think
tasks.
Maybe
we
correspond
to
the
stage
once
once
they're
become
available,
but
the
three
events
that
we
have
our
pipeline
run
cued
started
and
finished.
C
I'm
not
sure
when
the
eq
leaving
queue
event
is
generated.
Is
that
once
the
job
is
completed,
surely.
E
A
C
E
B
No,
but
we
should
probably
mention
something
in
in
the
continuation
integration
events:
we
have
build,
queued,
build
start
and
build
finished.
C
Yeah,
I
think
it
builds
events
are
specific
to
a
job
which
is
a
build,
so
that
creates
an
artifact
and
so
after
a
build
we
sent
like
already
for
published
or
artificial
packaged
events
as
well.
I
think
that
was
the.
E
Yeah,
I
I
do
agree
with
that
and
we
can
implement
that
in
jenkins,
but
I
don't
think
that's
going
to
work
for
all
jobs,
because
there
obviously
are
some
jobs
where
someone
would
might
want
to
build
and
publish
an
artifact.
So
that
can
be
a
possibility
of
implementing
that
event
inside
of
jenkins.
But
it
might
become
a
bit
hard
to
figure
out.
When
exactly
would
we
want
to
trigger
that.
C
C
C
An
event,
for
instance
that
requires
an
artifact
id,
it's
an
option
not
to
be,
but
if
you
want
to
send
an
artifact
that
you
need
to
to
be
able
to
understand
where,
where
to
take
that
argument
id
from
so
it's
a
similar
kind
of
problem,
we
have
an
object
inside
because
jenkins
is
kind
of
high
high
level
pipeline
orchestrator.
In
this
sense,.
C
C
E
We
can
also
offload
this
to
the
user.
Who
is
configuring
that
particular
sync,
since
that's
how
it's
very
like
ui,
based
at
the
moment,
what
events
would
the
sync
like
to
receive
and
then
act
upon,
so
the
user
can
maybe
select.
I
also
want
to
send
build
events,
for
you
know
my.
E
My
job
is
also
building
artifacts
and
publishing,
but
I'm
not
sure
if
it
might
make
it
easy
or
hard
for
for
the
users,
because
it
might
be
a
bit
difficult
to
figure
out
the
difference
between
like
build
events
or
build
like
events
or
jobs
that
you're
building
an
artifact
versus
just
plain
jobs.
C
I
think
it
would
make
sense
and
certainly
would
help.
C
E
Yeah,
I
think
that's
a
good
idea.
Definitely
thinking
of
offloading
it
to
the
user
itself.
B
I
thought
it
was
at
least
we
had
some,
I
guess
when
you're
running
your
tests,
you
want
to
have
the
environment
where
you
run
it,
but
maybe
that's
not
exactly
corresponding
to
node,
but
I
guess
you
could
use
it's
in
my
head
at
least.
E
I
do
see
I
do
see
that
point
because,
like
you
know,
and
when,
whenever
someone
would
want
to
have
a
special
sort
of
testing
environment
for
their
job,
they
might
create
a
node
and
add
additional
capabilities
to
it.
Yeah.
Okay,
that
I
think
that's
something
that
I
might
need
to
look
a
bit
more
and
ask
jenkins
community
who's,
more
familiar
with
environments
and
like
node,
but
that
that
that
can,
as
mathias
said,
that
is.
That
is
true.
That
they're
in
in
a
way
that
that's
both
executing.
D
E
Yeah
it
aligns
more
with
infrastructure
and
like
starting
up
or
tearing
down
an
infrastructure,
then
very
clear
alignment
with
environments.
But
I'm
sure
that
it
is
something
that
jenkins.
D
Yeah
in
in
our
world
the
artillious
world,
we
view
we
call
them
endpoints,
but
nodes
are
belong
to
an
environment.
So
you'd
have
you
know
a
database
server
you'd
have
your
kubernetes
cluster
and
then
you
may
have
some
lambda
functions
that
make
up
the
qa
environment
and
those
are
all
going
to
be
part
of
different
types
of.
C
D
C
So
I
think
it
makes
sense
maybe
to
to
some
discussion
around
on
this
kind
of
events
or
cd
events
as
well.
So
maybe
what
I
can
do,
I
can
create
an
issue
or
a
discussion,
and
then
we
can
continue
the
discussion
there
on
this
specific
topic
and
see
if
we
want
to
add
some
some
events
to
the
data
spec.
C
E
Yeah,
I
don't
mind
either
way,
but
it's
still
I
like
creating
and
maybe
figuring
out
that
environment.
Usually,
I
think
that's
a
good
idea.
C
E
Yes,
no
I'll
definitely
start
working
on
these,
and
I
also
pull
in
some
more
people
who
are
familiar
with
the
entire
jenkins
ecosystem
and
they
might
be
to
help
out
as
well
and
the
terminology
and
the
differences
between
you
know
jenkins
and
other
ci
cds,
especially
like
tech
drawn.
While
we
were
since
we're
using
that
for
the
poc.
C
E
C
Now
great,
we
only
have
a
few
minutes
left.
Do
we
want
to
get
back
on
the
discussion
in
terms
of
the
format
for
the
spec
and
the
generating
sdk
code,
or
anything
else
folks
would
like
to
bring
down.
A
A
Most
likely
some
of
those
discussions
or
some
of
those
actions
are
pretty
close
to
being
done,
and
what
I
would
propose,
as
is
that
we
as
sort
of
a
standing
bullet
for
future
meetings,
we
try
to
to
look
into
yeah.
Whatever
discussions,
I
think,
are
either
important
or
soon
to
be
closed
or,
or
can
be
easily
closed
just
so,
we
can
basically
shorten
down
the
backlog
a
bit.
C
Yeah,
it
makes
sense,
so
let
me.
C
A
I
think
that
that
might
take
too
much
time.
I
think
if
you
look
at
there
might
be
one
bullet.
Actually,
if
we
look
at
it
that
I
think
I
documented
some
discussion
as
basically
just
needing
a
formal
decision,
it
seems
like
everyone
is
in
agreement,
but
I'm
just
not
sure
about
the
decision.
Let's
see
if
I
can
actually
remember
which
one
that
is,
I
hope
I
noted.
D
Maybe
when,
when
we
look
through
these,
if
there's
some
way
on
the
wiki
page,
we
could
just
color
code
or
tag
the
ones
we
think
that
are
close
just
to
make
things
easier
to
find
again.
A
Yeah,
that
would
be
a
good
point.
In
fact,
I
think
it's
the
first
one,
it's
one
of
the
ones
that
it
seems
to
be
really
close
to
to
at
least
partial
decision.
We
were
talking
about
generic
versus
concrete
activity
events
and
I
think
everyone
seems
to
be
in
favor
of
having
generic
activity
events.
C
The
person,
I
think
we
we
need
to
have
concrete
activity,
events
as
well
and
and
that's,
I
think,
an
area
where
we
gain
a
lot
of
value
by
having
this
shared
vocabulary,
because
especially
the
concrete
activity.
Events,
probably
where
you
get
a
lot
of
letter
of
different
names
in
different
systems,
and
if
we
can,
at
least
in
this
place,
have
one
name
which
is
explained
with
a
clear
semantic.
C
And
so
there
will
be
adaptation
layers
needed
for
the
different
platforms
to
converge
to
those
names.
But
then,
at
least,
if
you
receive
an
event,
cd
event
that
talks
about
a
test
or
a
build.
You
know
what
is
meant
with
that,
and
then
you
can
take
an
action
on
that.
Whether
if
you
only
get
events
about
tasks
and
generic
tasks
and
pipelines,
I
think
that's
useful
if
you
want
to
display
the
progress
of
a
pipeline
or
of
your
work
flow
made
of
multiple
tasks
or
pipelines.
C
D
Yeah,
I
agree,
I
think,
when
we
talk
about
the
concrete
events,
I
think
it's
going
to
be
helpful
in
the
long
run,
but
also,
I
think,
we're
going
to
end
up
needing
for
a
a
translation
matrix.
So
this
is
our.
This
is
from
the
spec
side.
This
is
the
definition
of
the
concrete
event
now
in
jenkins.
You
know,
just
like
we
had
the
conversation
about.
D
What
a
note
is,
you
know,
so
a
node
in
in
the
spec
is
defined
as
this
and
jenkins
it
maps
one
to
one
it
maps
to
something
else
and
in
like
arterius,
it's
a
map
to
something
else.
I
think
we're
going
to
need
a
matrix
that
kind
of
helps
people
digest
or
or
a
way
to
bring
things
into
their
their
frame
of
reference.
E
E
C
And
I
think
we
started
to
collect
some
of
those
names
so
yeah.
We
should
keep
those
in
a
document
nicely
in
a
nice
table
all
right,
so
we
are
at
time
we
have
a
bit
of
a
hard
cuts
and
another
meeting
coming
up.