►
From YouTube: Delivery Fast Boot: Day 3 discussing Product features
Description
Delivery team fast boot Day 3: Discussing with Jason Lenny which GitLab features can be leveraged for tasks Delivery is working on.
The issues listing the work done are contained in epic https://gitlab.com/groups/gitlab-org/release/-/epics/17
A
B
B
B
B
A
B
B
B
A
B
B
A
So
trigger
and
her
by
our
two
variations,
the
same
thing
it
just
depends
on.
If
you
want
like
deployer
to
automatically
trigger
itself,
whatever
an
omnibus
run
happens
that
you
can
do
that
or
the
other
way
you
can
encode
it
is
by
having
omnibus
trigger
and
different.
It's
almost
like
the
org
structure
depends
on
which
version
makes
the
most
sense
for
you
like,
if
you're,
in
a
situation
where
you're
at
company,
you
know,
there's
a
different
team
in
another
department
somewhere,
they
are
dependent
on
them,
deploying
their
service.
Thank
you!
A
So
whatever
they
do,
you
want
to
refine
yours
to
pick
up
like
the
latest
signatures
or
whatever,
but
you
don't
necessarily
want
to
tell
them
to
like
add
a
step
in
their
bill
to
kick
off
your
bill,
so
you
can
just
mark
yours
is
like
I'm
dependent
on
them.
So
whenever
they
ride,
let
me
run,
but
in
a
way
it
is
building
a
relationship
between
the
two
and.
A
It
can
also
visualize
it,
but
in
any
case
these
are
these
relationships
are
only
created
at
the
moment
that
that's
triggered.
So
you
can't
see
a
potential
view.
This
there's
a
different
feature
that
we're
looking
at
directed
Isaac's
ground,
which
I
said
I
posted
a
link
to
the
team
chat.
Just
like
that's
kind
of
this
grand
unified
one
of
the
elements
in
there
is
to
be
able
to
encode
this
relationship
into
a
single
pipeline
mm-hmm,
and
then
that
would
work.
A
A
B
A
A
A
B
B
What
I
wanted
to
achieve
here,
for
example,
is
something's
readers
of
the
glory
here.
I
want
to
create
three
separate
pipelines
on
that
same
commit.
They
are
doing
different
things
that
are
not
related
to
each
other,
really,
no,
not
really
like,
for
example,
I
would
like
this
to
execute
automatically,
but
I
would
like
these
two
to
be
created
and
be
manual
all
right.
A
The
way
that
we're
solving
this
mission-
okay,
we'll
be
good
enough
in
the
directory
spacecraft,
where
you
can
basically
the
easiest
way
to
think
about
that-
is
that
there's,
a
new
keyword
called
dependent
depends
on
or
something
like
that
and
forget
stages.
Forget
anything
like
there's
only
these
depends
on
relationship
that
builds
our
graph
just
like
just
like
the
gate
graph,
and
it
just
runs
everything
as
quickly
as
possible
and
if
something
depends
on
something
that
accuses
it
behind
it
until
that
exists,
so
you
could
build.
A
We
have
is,
we
have
a
pipeline
and
it
can
have
like
multiple
jobs
or
whatever,
that
might
run
in
different
stages.
But
each
of
these
is
a
heart
of
limit
where,
like
all
of
these
need
to
finish,
if
they're
marked
and
then
go
over
so
with
the
dying
it
would
be,
it
would
be
more
like
you
know
something
like
this
and
you
could
get
to
any
of
these
points
like
if
this
got
stuck
here.