►
From YouTube: Debugging a failed pipeline on the Handbook
Description
Quick overview of how to go about identifying why a pipeline might be failing for a merge request to the handbook.
A
A
If
we
go
into
the
to
the
actual
pipeline,
you'll
see
that
the
pipeline
is
broken
up
into
multiple
stages,
build
test
and
deploy,
and
we
can
see
that
the
build
has
failed
here.
If
you
click
on
this
job,
you
will
see
it's
broken
up
into
multiple
parts,
and
all
of
them
are
failing.
So
I'm
going
to
click
on
the
first
one.
That's
failed,
and
this
should
bring
up
a
log
now.
A
lot
of
this
will
look,
technical
and-
and
it
wouldn't
be
necessarily
relevant
to
to
the
actual
error
for
for
the
most
part.
A
But
what
you
want
to
do
is
look
for
any
message
that
that
can
give
you
some
more
information.
So
if
we
just
scroll
up
here,
we
can
see
here
that
it
tells
us
here
that
there
are
reports
to
entries
for
in
new
delhi,
but
nobody
is
assigned
to
those
roles
be
sure
to
assign
a
person
a
slug
entry
in
tinder
demo.
A
A
And
we're
going
to
look
at
the
changes
we
can
see
that
the
reports
to
value
here
were
set
to
in
util
over.
However,
the
slug
for
for
the
team
entry
for
this
team
member
is
actually
nadia
udalova
and,
and
that
is
why
it
was
it
was
failing
because
it
couldn't
find
an
entry
in
the
team
yaml
with
that
slug
value.
A
So
to
recap,
when
you
get
a
failed
pipeline,
first
of
all,
click
on
on
on
the
pipeline
all
on
these
icons
here
to
show
you
and
then
click
on
the
failed
job
and
try
and
see
if
you
can
find
a
a
a
message
that
is
human
readable,
that
that
makes
sense.
Most
of
our
errors
will
have
some
sort
of
message
that
gives
you
an
indication
of
what
went
wrong.
That
doesn't
mean
that
it
will
always
be
that
case,
but
in
most
cases
you
can
find
the
message
in
there.