►
From YouTube: SIG Events Meeting - July 4, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
A
A
A
First,
action
from
last
meeting-
I
didn't
note
any
really
so
there's
nothing
to
follow
up
there.
As
far
as
I
can
see.
A
So
first
thing
to
look
into
the
agenda:
is
the
planning
for
zero
one?
It's
a
recurring
thing
that
we
will
have
now.
I
guess
in
all
our
city
events
and
significance
meetings
until
done
with
us,
so
from
sigurdan's
perspective,
we'll
discuss
more
about
the
administrative
tasks,
not
specific
vocabulary
tasks
unless
we
have
time
in
the
end,
of
course,
we
can
bring
in
such
as
well
that's
no
problem
at
all
and
the
sub
bullets.
I've
added
here
is
the
on
the
release,
announcement
and
the
tragic
evidence,
and
none
of
those
are
yet
started.
A
As
far
as
I
can
see,
I
volunteered
to
take
on
the
governance
part,
but
I
will
not
be
able
to
do
that
now
before
my
vacation,
which
starts
end
of
this
week,
so
I
will
do
that
when,
when
I'm
back
after
vacations
in
early
august
and
then
the
release
announcement
is
also
something
that
I
guess
will
happen
closer
to
the
release
itself.
A
D
I
think
it
would
be
nice,
though
I
would
actually
add
a
few
more
items
to
the
scope.
I'm
not
sure
whether
you
have
seen
the
recent
recording
of
the
cdf
outreach
committee,
but
yeah
I'm
from
well.
We
discussed
how
we
actually
leverage
the
community,
the
ambassador
program
and
one
of
the
points
there
was
actually
doing
more
outreach
for
city
events
and
more
promotion
using
the
powers
of
ambassadors,
and
that
mean
it
would
definitely
require
some
template
slide
decks
or
overview
slide
decks
so
that
they
could
reuse
in
their
talks.
D
Maybe
some
schwa
logistics
for
that,
but
yeah
laurie.
The
new
cdf
outreach
chair
is
happy
to
collaborate
on
this
topic
and
I
think
we
should
leverage
this
opportunity.
A
Yeah
sounds
good,
so
do
you
think
we
should
make
it
part
of
this
announcement
issue
we
have,
or
should
we
mix
repetitions
for
them.
B
A
A
A
D
So
basically,
what
we
were
discussing
is
actually
making
the
cdf
outreach
committee
more
open,
because
now
it's
just
a
group
of
premier
member
companies,
company
representatives
without
project
representatives-
and
this
was
actually
one
of
the
topic
we
discussed
seriously
and
with
fatih
being
the
executive
director
and
strongly
supporting
transparency
in
the
foundation.
D
I
think
it's
rather
a
done
deal
so
if
anyone
wants
to
start
participating
you're
more
than
welcome
but
yeah
at
the
same
time,
my
belief
that
we
will
basically
removing
most
of
the
obstacles
so
that
anyone
could
jump
on
this
committee
and
participate
if
they
want
to
contribute.
B
D
Yeah
actually
yeah,
this
topic
was
discussed
heavily.
I
can
share
meeting
notes
with
you
later
and
I
believe
that
next
presentation
to
the
governing
board
by
laura
will
also
include
that,
and
maybe
I
will
do
some
summary
at
the
qc
meeting
tomorrow.
D
D
Well,
it's
all
fresh
news.
We
just
had
meetings
last
week.
Everything
is
yet
to
happen,
but
the
good
news
is
that
you
know
there
is
definitely
interest
to
make
it
happen.
A
Is
there
some,
maybe
some
meeting
from
that
meeting
that
we
should
just
touch
here
then.
D
But
yeah
so
outreach
committee
was
totally
closed
entity.
Until
that
I
mean
I
had
no
idea
who
is
a
member
of
this
outreach
committee.
A
A
Okay,
good,
I
didn't
intend
to
talk
much
more
about
the
actual
planning
for
the
001.
Now
do
any
of
you
think
we
should
mention
anything
from
generic
terms
before
we
go
on
in
the
meeting,
and
we
can
come
back
to
this,
of
course,
for
more
c
different,
specific
tasks
later
on.
D
So
last
year
that
you
see
upon
important
10k
for
cd
event,
sakai
system
which
haven't
been
used
and
which
could
be
potentially
used,
for
example,
this
autumn
as
a
part
of
lfx
mentorship
programs
or
whatever
sponsored
development.
D
D
Because
there
are
two
ways
doing
basically
internship
program
or,
let's
say
hiring
a
contractor
developer
to
do
something.
D
It
depends
so,
basically
there
could
be
two
approaches.
One
is
technical
content,
so
somebody
who
dips
deep
dives
into
the
technical
part
finds
the
gaps,
tries
out
the
prototypes
on
their
own
and
creates
documentation
and
another
one
is
just
copy,
editing
and
basically
designing
the
documentation
for
the
future,
which
part.
Would
you
rather
see
in
the
current
state
of
the
documentation.
D
B
D
Yeah,
if
you
rather
look
for
technically
advanced,
develop
users
or
maybe
somebody's
developer
background,
then
it's
more
complicated.
A
Yeah,
I
think,
yeah
well,
I
guess
we
could
benefit
from
both.
I'm
not
sure
that,
though,
that
it's
the
best
word
for
the
money,
but
instead
of
just
letting
the
money
go,
we
can
of
course
do
that.
Do
we
have
any
other
opinions
in
the
group
here?
What
we
could
use
the
money
for.
C
C
Gitlab,
for
instance,
or
other
type
of
events,
so
it
kind
of
build
a
catalog
of
those
another
thing:
that's
with
another
project
that
would
be
nice
to
to
have
is
some
visualization
front
end
or
when
we
collect
cloud
events
to
kind
of
help
us
visualize
them.
So
this
is
someone
with
some
javascript
skills,
not.
B
C
Libraries
could
build
something
like
that.
That's
another
thing
that
we
could
do
yeah
another
area
which
is,
but
maybe
that's
not
a
good
fit.
For
a
internship,
though
I
mean
that's
the
the
what's
called
the
application
life
cycle
events
captain
offered
to
integrate
with
city
events.
D
So
the
budget
is
allocated
for
any
advanced
advancement
of
city
events
ecosystem.
So,
basically,
as
long
as
it
helps
all
the
projects
and
not
let's
say
just
tickton
or
jenkins-
this
money
can
be
used.
There
is
no
additional
boundaries
set
as
we
discussed.
So
it's
up
to
see
the
events
governing
team
talk
to
you
how
this
money
would
be
allocated.
D
A
C
I
mean
other
things
that
we
could
get
out
on
is
the
yes,
the
case
of
course,
and
maybe
some
we
discussed
about
automation
and
setting
up
some
of
the
sdks
or
automation
for
the
specification
based
on
schemas.
So
I
mean
there
are
this
kind
of
small
projects.
I
think.
A
Yeah,
I'm
just
a
bit
concerned
how
we
could
set
up
such
things.
It
relates
to
the
association
as
well.
I
guess
we
we
would
need
to
spend
some
time
support,
sometime,
of
course,
in
our
group,
even
though
we
might
get
in
some
resource
externally,
it
wouldn't
be
for
free
when
it
comes
to
our
own
time
as
well,
and
I
think
anything
that
would
delay
the
release
of
0.1.
A
D
And
this
why
I
wanted
to
highlight
that
it's
not
necessary
to
just
have
let's
say
internship
with
someone
not
experienced
technically
it's
possible:
well,
even
modern
gsoc
or
google
season
of
dogs.
They
are
allowed.
They
allow
for
professionals
who
want
to
start
working
in
open
source
and
through
lfx
mentorship.
You
can
also
have
a
more
or
less
experienced
person
working
on
that
so
yeah,
and
actually
I
would
rather
advise
that
because
as
well
as
you
said,
otherwise,
it
would
require
significant
time
resources
from
the
core
team,
which
is
not
big.
D
So
I
can
definitely
help
with
logistics,
getting
called
this
money,
lfx
mentorship
setup
and
other
things
but
yeah
well.
I
could
probably
help
with
mentoring
two
in
autumn,
but
definitely
not
this
summer.
A
Andrea,
I
think
I
missed
your
first
suggestion
by
the
way
before
you
talk
about
the
association,
you
said
something
else
right,
which
I
forgot
to
note.
C
C
I
believe
mission
and
mauricio
already
looking
into
something
like
that,
but
we
could.
We
could
have
that
for
other
common
platforms,
yeah
to
start
yeah.
D
Well,
this
is
also
possible,
though
it
needs
some
discussion,
because
in
this
case
the
project
wouldn't
be
vendor
neutral.
D
So
it
immediately
raises
this
question
whether
we
actually
invest
the
money
correctly,
which
is
again
not
a
blocker,
but
it
really
needs
some
justification
and
careful
planning
and
probably
opening
an
opportunity
so
making
a
call
for
let's
say
all
the
adapters
for
top
scm
systems
and
then
the
average
application
just
for
github.
Okay,
we
can
go
with
github.
C
I
think
it
will
be
difficult
to
to
get
something
if
you
don't
contribute
at
least
a
little
bit
from
from
our
group.
I
mean
I
I
can.
I
should
be
able
to
to
spend
some
time
like
this
summer.
If
there
is
anyone
to
require
some
mentoring
or
also
in
autumn,
depending
on
the
time
where
we
can
make
things
happen,.
C
Further
idea
I
mean
yes,
we
could
we
could
just
work,
but
I'm
not
sure
that
would
be
very
good
use
of
money
as
well
or
I
don't
know
if
there
is.
There
are
conferences
where
we
can
have
like
if
you
want
to
to
have
a
day,
zero
event
or
a
posted
event
in
maybe
a
open
source
summit
or
some
other
conferences
that
we
could
invest
the
money.
D
Because
travel
grants
is
definitely
possible,
so
let's
say
taking
a
contributor,
let's
see
so
we
had
a
scholarship
for
one
of
the
students
to
present
at
cubecon.
C
B
D
Valid
point:
yeah
right
now
we
basically
get
this
money
from
the
cdf
and
thanks
to
them
I
mean
well
indirectly
for
cdcon
day
for
cubeconde.
A
So
if
we
should
try
to
progress
this,
I
think
one
easy
task
would
more
just
be
to
to
see
if
we
can
get
some
if
we
can
find
some
technical
writer
or
what
you
said
or
exam
some
editor
to
look
into
the
documentation
we
have.
That
could
be
us.
Well,
let's
go
ahead
if
we
find
such
a
resource,
but
then,
of
course,
for
yeah,
for
example,
the
visualization
front,
and
that
would
for
sure
be
vendor
neutral.
I
think
that
might
require
an
event-
storage,
maybe
solution
as
well
connected
to
it.
D
I
think
the
best
step
right
now
would
be
to
just
figure
out
the
topics
we
would
like.
So
if
you
want,
I
can
do
some
bits
about
the
documentation,
maybe
some
public
calls
etc
for
anyone
who
would
be
interested
because
if
you
have
a
potential
candidate,
then
the
discussion
is
quite
easy,
if
not
it's
more
challenging,
so
I'm
doing
the
same
for
captain
in
the
coming
months,
so
I
can
do
cd
events
as
well.
A
So
andrea,
what
do
you
think
it's
possible
to
to
set
up
a
visualization
with
some
resources.
C
At
least
it
doesn't
have
to
be
like
very
sophisticated,
but
if
we
set
up
an
initial
framework,
then
we
can,
you
know
iterate
on
it.
I
think
it
would
be
yeah.
It
would
be
beneficial
for
our
pocs
like
doing
demos
yeah,
that's
mainly
it
doesn't
have
to
be
like
if
you
use
some
kind
of
event
back
end,
it
doesn't
have
to
be
like
the
the
one
that
we
recommend
as
part
of
city
events.
It
can
just
be
something
that
we
use.
A
D
And
I
will
do
the
budgeting
and
logistics,
so
basically,
we
have
a
platform
for
this
or
basically
any
other
program
in
the
future,
which
is
thicker
expenses
but
yeah.
If
somebody
could
take
a
look
at
the
visualization
part,
it
would
be
nice
because,
while
I
understand
the
purpose
of
that,
it
would
be
nice
to
parallelize
it.
A
But
to
me
the
disposition
part
sounds
at
least
like
something
that
is
quite
easy
to
set
the
borders
around
the
other.
When
it
comes
to
automation
is
the
case,
and
the
adopters
adapters
might
not
be
as
easy
to
well
the
first
one.
All
the
adapters
is,
of
course,
vending
neutral
problems,
maybe
and
the
sdk
automation
might
be
a
bit
fluffy,
maybe
as
well.
But
what
do
you
think
andrea?
I
mean,
as,
as
I
said
before,
I
I
will
not
be
working
much
more
now
before
my
vacation,
so
I
might
not.
C
C
No,
I
don't
have
any
vacation,
I
mean
I
I
have
some
days
I
will
be
in
like
in
august.
I
will
be
traveling,
I
will
be
working
from
italy,
so
I
have.
B
C
One
day
off
to
travel
there,
but
I
will
be
working
there
from
there
so.
D
Okay,
so
we
can
just
at
the
next
meeting
yeah.
A
Perfect,
so
I
think
we
should
go
on
in
the
agenda
good
discussion
and
thanks
for
bringing
up
perfect.
So
we
have
jalandha
with
us,
and
I
think
we
should
take
the
opportunity
now
to
to
let
under
present
or
demo,
the
spinach
integration
that
has
been
working
on,
which
is
currently
another
review
so
get
under.
If
you'd
like
to
take
the
sharing.
E
Let
me
know
if
you
are
able
to
see
my
screen:
yes,
okay,
yeah,
so
this
is
the
pr
that
is
there
like.
We
need
to
integrate
spinnaker
with
sig
givens
poc,
so
that
poc
is
existing
poc.
I
think
that
is
developed
initial
time.
This
is
the
current
poc.
Is
there.
So
what
I'm
doing
is
like
right
now,
I'm
integrating
spinnaker
to
the
existing
poc
here
the
existing
poc
looks
like
this,
so
just
to
have
an
introduction
or
just
a
quick
check
yeah.
E
So
this
has
a
tecton
pipeline.
It
builds
and
it
triggers
an
artifact
package
and
even
to
captain
and
captain
approves
the
artifact
and
then
back.
It
sends
a
artifact
published
event
and
that
event
is
received
by
again.
Tecton
and
tecton
will
do
a
deploy
job
and
then
finally,
it
says
the
service
deployed
event,
so
this
flow
is
the
existing
one.
So
that
is
there
right
now
in
this
equivalence,
tripo
I'm
what
I'm
doing
is
like
I'm
trying
to
add
a
spinnaker
into
this
flow
yeah.
E
So
my
image
looks
like
this
slight
difference.
So
if
you
see
the
corner
part,
the
right
top
corner
is
what
is
added.
It's
just
a
spinnaker
and
the
cd
event
controller.
The
cd
events
controller
is
the
one
is
responsible
to
consume
the
event
and
produce
the
events
and
to
produce
the
event.
So
we
have
actually
created
a
cloud
event
java
sdk.
So
this
is
yeah
java,
sdk
based
on
cloud
events,
so
this
will
emits
the
cloud
events.
E
What
spinnaker
needs
to
do
so
yeah
right
now,
so
the
flow
works
this
way,
so
it
fits
in
the
existing
flow.
So
if
you
I
just
want
to
explain
in
this
flow,
how
it
works.
This
part
of
thing
is,
like
all,
is
with
the
existing
poc,
so
the
so
the
last
spinnaker
one
is
added
here
like
if
you
see
a
very
corner
right
side,
so
the
spinnaker
is
added
here.
So
this
is
the
additional
part.
So
what
it
does
is
like
everything
is
similar
until
artifact
is
published.
E
So
if
you
could
see
my
cursor
here
so
yeah,
the
flow
works
here
right.
So
you
know
that
like
tecton
runs
the
build
pipeline
and
it
sends
an
event
artifact
packaged
to
captain
and
captain
approves
that
artifact
right
so
and
then,
once
the
artifact
is
approved
by
captain
and
captain
sends
yeah,
so
captain
sends
artifact
published
event.
So
this
time
now,
I
am
also
sending
it
to
spinnaker.
E
So
the
artifact
published
events
earlier,
it
is
sending
into
tekken
triggers
so
now,
unlike
spinnaker,
also
registered
to
listen
to
this
particular
artifact,
which
is
sent
by
captain
outbound.
E
So
artifact,
published
event
is
also
received
by
spinnaker
for
the
same
image
and
same
trigger
id.
What
and
context
what
district
what
is
created
by
tecton
and
what
spinnaker
does
is
spinnaker
receives
this
event
and
it
runs
a
deploy
pipeline
within
spinnaker,
yeah
and
the
middle
part.
You
see
this
is
the
existing
one,
so
the
tecton
does
the
job
of
taking
the
artifact
published.
E
I
mean
deployment
starts
and
then
sends
the
service
deployed
event
in
the
same
way.
So
spinnaker
also
spinnaker
also
receives
that
artifact
published
event
and
runs
the
deploy
pipeline,
and
it
sends
the
send
back
to
the
notification
that
kept
inbound
to
cd
service
deployed
and
the
same
service
deployed
event
is
a
listen
by
captain
inbound
again,
the
same
way
like
when
tecton
sends-
and
this
is
what
like
captain
inbound
again,
it
says
the
deployment
is
finished.
Mock
has
deployment
finish
for
both
the
tecton
and
spinnaker
as
well.
E
C
Just
just
a
quick
question:
if
I
got
it
right,
it's
are
there
two
deployments
happening
or
is
it
just
it's
just
spin
across
the
deployment
in
this
scenario,.
C
E
Both
both
does
the
deployment,
so
tecton
is
like
the
existing
way
how
it
is
doing
the
same
deployment
is
there
and
and
spinnaker
also
does
the
deployment
in
the
different
environment?
I
mean
it's
in
the
same
kubernetes
cluster,
but
it's
a
different
part.
It
is.
D
Yeah,
so
actually
it
brings
up
a
good
question
how
we
are
going
to
grow
this
plc
when
we
add
more
tools,
because
yeah
during
one
deployment,
always
for
h2,
we
want
to
demonstrate,
can
be
quite
resource
consuming.
So
maybe
we
should
start
adding
some
enablers,
for
example,
in
action
charts
later.
So
it's
definitely
not
for
this
demo.
I'm
excited
to
see
this
integration,
but
yeah
later
for
scalability
yeah.
It
would
be
really
nice
to
see
how
we
can
actually
minimize
the
footprint
for
particular
demo.
E
Yeah
so
I'll
just
go
to
the
demo,
so
the
changes
what
I've
done
before
going
to
domain,
maybe
quickly
I'll,
go
through
the
changes.
So
I
have
created
a
script
to
configure
and
install
spinnaker.
E
So
this
does
these
bunch
of
things.
So
it
will
just
do
a
installation
of
spinnaker
and
running
into
hal,
and
then
it
creates
a
trigger
to
subscribe
to
spinnaker
event,
api.
That
is
the
artifact
published
event
and
it's
create
an
application
and
pipeline
also
which
I
need
to
run
from
the
service
deployed
event.
So
it
does
all
within
the
script
and
there
is
another
another
script.
E
It
invokes
it
to
create
the
whole
pod
and
inside
that
it
is
just
install
the
helm,
cli
and
configuring
the
things
that
is
required
for
spinnaker
to
install-
and
I
have
some
templates
to
use,
deploy
spinnaker
the
pipeline-
and
this
is
this-
is
where
the
spinnaker
eco,
where
we
have
the
consume
and
produce
endpoints
created.
E
So
the
actual
thing
will
be
not
having
the
changes
with
the
cd
events,
so
this
will
replace
the
changes
that
is
going
with
the
cd
events,
rest
endpoints,
to
consume
and
produce
yeah.
This
is
where
I
create
a
spinnaker
service
account
to
interact
with
kubernetes
with
spinnaker
is
what
is
the
change?
Okay,
so
I'll
have
a
quick
demo,
and
so
probably
we
can
go
through
the
changes
and
maybe
online
time
permits
otherwise
offline.
We
can
have
some
reviews.
E
Yeah,
so
this
is,
the
scripts
are
integrated
to
the
existing
poc.script.
So
this
script
we
have
so
run.
Currently
I'm
running
on
the
same
branch,
I
think
so
yeah,
it's
the
spinnaker
poc
yeah.
So
this
is
the
same
script
and
I
have
modified
this
one
to
include
install
and
configure
spinnaker.sh,
so
this
runs
only
with
the
option
when
we
have
run
with
spinnaker.
So
this
is
the
comment
I
think
I
got
from
andrea.
This
is
addressed
so
this
one
works
like
this.
E
E
So
I
have
already
installed
spinnaker
here.
E
Yeah,
so
the
spinnaker
parts
are
running,
so
this
is
the
part
where
the
cd
events
rest
point
and
end
points
are
there.
So
this
is
the
replaced
one
from
the
script
and
all
other
things
that
we
are
not
using,
but
yeah.
It's
used
internally,
the
gate
and
all
of
this
stuff
yeah.
So
just
I
I'll
quickly
quickly
run
the
tecton
pipeline
so
because
that's
when
the
main
flow
starts
yeah,
so
I'm
under
the
poc
I'll
just
run
this.
E
It
takes
the
same
inputs,
no
change
here.
Actually
so
only
the
change
like
explained
it's
in
when
it
comes
to
the
cd
artifact
published
event,
so
yeah
I'll
just
have
this.
E
D
E
B
E
E
Yeah
so
tecton
is
here,
and
the
captain
is
running
here
and
I
have
the
spinnaker,
so
the
script
will
actually
create
the
cd
events
poc.
So
this
is
the
application
inside
spinnaker
and
inside
application.
It
will
also
create
a
deploy
pipeline,
so
that
pipeline
will
have
basically
the
configuration
to
get
the
cd
events
poc
from
the
kind
cluster
and
deploy
it
into
the
this
default
namespace
in
the
same
kubernetes
cluster,
so
running
on
port
80..
So
it's
just
a
simple
deployment.
E
The
same
poc
image
will
be
deployed
here,
yeah,
so
going
back
to
this,
so
this
is
what
is
the
image
is
built
yeah.
If
you
go
to
captain
in
the
sequence
yeah,
we
have
a
one
sequence
waiting
here
for
approval.
E
E
E
Yeah,
so
this
is
successful,
so
these
things
are
deployed
here
we
can
just
see
ctrl.
E
But
this
was
yeah,
it's
replaced.
This
is
the
one
is
deployed
here,
so
we
can.
I,
I
can
just
do
port
forward
to
see
whether
the
deployment
is
access
or
not
yeah.
The
captain
have
the
deployment.
Jobs
are
successful
yeah,
so
I
have
done
some
changes
in
the
captain
code
base
also,
so
that
is
the
cdf
the
captain
inbound
code
base,
so
that
will
take
some
spinnaker
things
and
context
and
make
the
captain
context
fast,
based
on
the
service
deployed
event.
E
Yeah,
it's
a
code
change
inside
yeah.
D
You
have
a
chance
to
submit
at
least
a
draft
pull
request.
Yeah.
E
Sure
I
will
I'll
submit
it,
so
I
have
it
we
are
actually
in
spinnaker
and
as
also
he's
in
yeah,
this
isn't
captain.
Also,
there
are
some
changes
so
I'll
submit
for
today.
D
Much
appreciated
so
why
I'm
really
getting
it
up
right
now
we
are
scheduling.
Basically
the
events,
0.1
specification,
adoption,
adoption,
captain
and
yeah.
Having
all
this
information,
it
would
be
useful
for
us
to
understand.
What's
missing,
okay
and
yeah,
it
could
be
helpful
for
the
spec.
E
E
E
C
D
E
A
C
So
does
is
there
a
way
you
can
tell
captain,
then
it
expects
completion
from
both
systems,
or
is
that
did
you
do
something
that
shipyard
configuration
to
so
that
captain
knows
it
expects
this
sequence
to
be
completed
twice
because
you're
getting
the
events
back
from
from
both
right.
E
E
So
if
you
see
here,
I
think
there
are,
I
don't
know,
but
for
tecton,
so
there
are
like
multiple
deploys
runs.
I
don't
know
it's
a
mess
from
my
side
are
not
sure
if
this
is
oh
sorry.
E
Yeah,
so
it
has
tecton
has
multiple
pipelines,
I
mean
deploy
jobs
run
so
each
time
it
will.
I
mean,
sends
a
service
deployed
event
and
captain
receives
also
in
the
same
way
order.
I
think
that
much
times
here
and
now
I
could
see
that,
like
one
more
time
also
extra
for
spinnaker
is
coming
here
from
the
logs
and
as
well
as
from
here.
So
it's
it's
the
same
event
that
I'm
using
on
the
captain
side.
It's
not
the
different
one.
Maybe
if
I
answer
it
correctly,.
C
C
You
start
the
deployment
sequence
with
spinner,
sorry
with
captain
and
then
spinnaker
is
doing
the
deployment
because
then
maybe
it's
it
keeps
the
it's.
Maybe
it's
cleaner.
You
don't
see
all
the
events
coming
from
from
both,
but
I
don't
know
it's
just
a
suggestion.
B
E
E
Yeah
right
now
right
now
that
is
static,
so
only
one
specific
pipeline
that
I'm
looking
for
and
then
trying
to
run
that
alone
from
spinnaker
side.
Once
the
moment
this
this
event
is
received,
I
mean
artifact
published
received
event
is
received,
so
I'll
only
pick
one
of
the
deploy,
spinnaker
poc
pipeline
and
run
so
this
is
static
yeah.
So
no
one
notifies
like
from
other
side
to
run
which
specific
job
but
yeah
spinnaker
itself,
I'm
like
taking
one
static
job
to
run
whenever
this
event
occurs.
Yep.
E
So
we
can
retrieve
like
now.
In
this
case
the
captain
is
sending
only
the
image
name
id
and
so
the
context
and
trigger
ids
right
so
right
now
we
don't
have
any
information
that
which
pipeline
to
run
from
captain
side
so
yeah.
If
captain
send
something
saying
like,
I
need
to
run
this
specific
job
our
pipeline
on
spinnaker.
So
we
can
take
that
as
an
input
and
run
and
look
for
that
specific
pipeline
and
then
try
to
run
that.
So
we
can
do
that
in
spinnaker,
yeah.
C
Yeah,
it
was
not.
I
was
not
asking
really
about
which
pipeline
to
run
but
more
like
the
sha
of
the
image,
because
tekton
is
building,
the
image
is
producing
an
image
shot,
and
that
goes
into
the
artifact
published
event
and
then.
B
C
Picked
up
by
spinnaker
through
captain
spinnaker
is
deploying,
and
if
I
remember
correctly,
you're
deploying
tag
1.0,
yes,
and
I
was
wondering
if
it
would
be
possible
instead
of
deploying
a
fixed
stack
to
the
plug,
to
deploy
the
shot
of
the
image
that
has
been
just
produced
by
the
build
pipeline.
C
C
C
Well,
it
depends
I
mean
if,
if
the,
if
the
build
script
recreates
the
1.0
tag
yeah,
but
I
think
it
would
be
nicer
to
because
in
the
artifact
published
event,
you
have
the
shot
of
the
image
that's
being
produced.
So
my
question
was:
it
is
possible
to
to
get
that
shot
from
the
event
into
into
the
manifest.
Somehow
I
don't
know
if
that's
something
that
spinnaker
supports.
E
Yeah,
maybe
I
need
to
check
that
if
I
understand
correctly
yeah
so
to
update
the
manifest
based
on
the
image
that
we
receive
in
the
event
even
published
right.
So,
okay.
E
I'll
I'll
check
on
that,
so
if
that
is
possible,
maybe
so
I
should
have
some
things
to
change
like
update
the
manifest,
so
we
have
some
apis
in
spinnaker,
so
that
is
visible
from
the
spin
cli
api
that
I
used
in
the
script
itself,
so
that
image,
even
we
can
modify
it
with
the
yeah.
We
have
some
apis
that
exposed
I'll
check
on
that
and
then
I'll
get
back
next
time.
C
A
Yes
yeah,
so
I
guess
there
were
cydia
artifact
published
is
sent
both
to
spinnaker
and
detecting
right
yeah.
It
includes
the
which
one
is
it
is
it?
The
show
is
not
mentioned
there,
but
the
show
is
part
of
that
event
as
well,
then,
somewhere.
E
A
Think
it
is
good
to
add
the
shot
to
this
picture,
so
it's
visible
that
that's
where
it
comes
from
from
captain
and
then,
if
it
can
be
you,
it
can
be
also
be
visualized
in
the
which
is
it's
run,
deploy
pipeline
for
both
spinnaker
and
text
and
then
to
say
that
we
run
the
point
pipeline
on
a
certain
city,
a
specific
char.
That
comes
so.
We
can
see
that
it's
the
same
char
that
is
mentioned
in
two
places,
then.
E
Yeah
I'll
try
to
check
that
good
one
think
it
is
possible
yeah.
A
A
There
we
go
now.
I
think
I'm
sharing
again
so
presentation
is
done.
We
have
an
upcoming
presentation
from
fidelity.
I
was
hoping
it
could
be
on
on
august,
8th,
sorry
july
18th,
but
it
seems
now
that
the
people
involved
in
that
presentation
will
come
back
from
vacations
actually
on
july
18th,
so
they
might
not
be
able
to
perform
that
presentation
there.
A
A
A
We
have
some
upcoming
conferences
and
there
are
some
news.
As
far
as
I
know,
the
spinnaker
summit
is
still
not
really
published.
I
believe
so
it's
not
really
possible
to
to
see
any
more
about
what
it
will
be,
like.
A
A
Now
we
don't
know
either
if
there
will
be
any
co-located
events
with
duke
or
north
america.
This
fall.
A
There
is
an
issue
if
we're
interested
to
be
part
of
the
discussion
there
to
see
how
we
should
integrate
or
use
make
use
of
the
terms
defined
in
sign
drop
in
seed
events.
We
will
most
probably
not
do
any
major
updates,
at
least
for
the
serious
one
release,
but
I
think
we
should
do
it
for
the
coming
releases
after
that.
So
we
are,
we
make
use
of
what
is
done
in
siege
interpretability,
and
there
is
some
interaction
on
going
through
this
ticket.
A
Okay,
any
other
comments
from
anyone
before
we
close
for
today.