►
From YouTube: Delivery Fast Boot: Jarv task Day 1 summary
Description
Delivery team fast boot Day 1, Jarv recaps the challenges of the task for automatically generating a package and deploying from a specific branch.
The issues listing the work done are contained in epic https://gitlab.com/groups/gitlab-org/release/-/epics/17
B
From
omnibus
and
what
that
is,
is
just
ensuring
that
when
we
trigger
an
omnibus
pipeline
it
properly
triggers
the
deployer
pipeline,
which
then
we'll
install
the
auto
deploy
package
and
eventually
what
we're
going
to
be
doing
is
this
omnibus
pipeline
is
going
to
be
triggered
by
your
pickin
job.
So
it's
going
to
pick
various
M
ours
into
the
auto,
deploy
branch
and
trigger
it
and,
at
the
end,
you'll
get
a
deployment
to
staging
so
we've
sort
of
verified
today.
B
A
Awesome
so
the
thing
you
told
about,
like
triggering
the
omnibus
branch,
could
be
clogged
anything
else.
Besides
omnibus
we
can
write
like
we
can
trigger
any
pipeline,
we
want
in
any
project.
So
what
I'm
thinking
about
is
when
we
start
introducing
components
that
are
containerized
right
like
when
we
stop
using
omnibus
for
everything,
but
to
start
using.
You
know
different
project
I'm
thinking
about,
for
example,
a
registry
where
we
are
going
to
have
to
find
a
way
to
deploy.