►
From YouTube: Build Artifacts Category Retrospect & Value Add
A
Testing
features
the
breadth
of
testing
capabilities,
and
I
wanted
to
retrospect
a
little
bit
on
this,
because
the
newt
brought
up
some
really
great
nits
around.
I
guess
there
weren't
just
knits.
They
were
like
really
valid
clarification
points
around
the
differences
between
pipeline
artifacts,
the
differences
between
job
artifacts
and
what
we
were
calling
build
artifacts.
So
that's
sort
of
the
what
I'm
hoping
to
accomplish
here
james.
B
B
But
I
think
that,
as
we
filled
that
in
it
helped
to
differentiate
between
the
job
artifacts
and
the
pipeline
artifacts,
why
those
are
different,
how
those
are
managed
and
how
this
is
different
than
package.
That
was
one
of
the
points
that
I
knew
brought
up
was
that
a
lot
of
other
companies
talk
about
this
as
something
that
falls
into
registry
or
package
and
why
these
are
different,
because
they're,
more
ephemeral,
they're,
not
something
that
you're
necessarily
deploying
to
a
customer.
It's
really
more
for
an
internal
facing
audience,
usually.
A
Perfect,
so
I
think
adding
this
build
artifacts
category,
which
includes
both
pipeline
artifacts
that
are
produced
as
a
testing,
artifact
report
and
then
job
artifacts,
which
are
the
latest
output
of
your
pipeline,
which
are
both
assets
that
are
useful
for
the
testing
category,
but
also
generally
in
the
verify
stage,
which
will
be
utilized
for
top
of
funnel
activities
for
the
testing
categories,
but
also
generally
useful
for
all
verify
use
cases
to
amplify.
Not
only
your
testing
funnel
but
add
value
for
for
the
entire
verify
stage.
A
We're
definitely
really
excited
that
you're
taking
that
on,
and
I
think
that
it'll
be
easy
to
direct
traffic
to
this
category
page
and
also
it'll
be
clearer
for
users
instead
of
just
having
the
ci
artifacts
label
on
issues
that
now
it
has
a
declared
vision.
It
has
a
forward-looking
use
case
and
customer
problem
to
solve
and
direction
where,
before
it
didn't,
really
have
a
declared
like
path
forward
revision.
It
was
kind
of
just
a
collection
of
features
or
epics
yeah.
B
A
Absolutely
and
then
hopefully
help
them
test
better
and
help
them
improve
coverage
and
and
performance
of
their
artifacts,
and
then
we
can
help
convert
those
users
to
then
author
pipelines
and
use
other
features
to
help
in
the
entire
verify
stage
to
help
them
in
their
experience.
Well
james,
thank
you
for
helping
me
reflect
on
this.
I
I
definitely
am
excited
for
this
new
category
and
I
think
it'll
really
help
our
users
see
the
future
of
artifacts
in
their
experience
at
gitlab.
So
thank
you.