►
From YouTube: GitLab 13.7 Kickoff - Verify:Continuous Integration
Description
Issues reviewed in this video:
https://gitlab.com/gitlab-org/gitlab/-/issues/202082
https://gitlab.com/gitlab-org/gitlab/-/issues/223793
https://gitlab.com/gitlab-org/gitlab/-/issues/276583
A
A
A
We
want
to
make
it
so
that
jobs
that
are
restarted
in
a
pipeline
would
be
associated
with
the
triggering
user.
The
problem
we're
trying
to
solve
here
is
when
you
have
a
pipeline,
that's
been
started
and
it
has
been
paused
for
whatever
reason.
Maybe
it's
been
cancelled,
for
example,
or
there
was
an
error
when
the
pipeline
stops
all
of
the
subsequent
jobs
that
have
not
run
become
skipped
jobs,
but
when
that
pipeline
is
restarted
by
a
user
other
than
what
the
one
that
originally
started
the
pipeline.
A
Unfortunately,
the
job
that
got
restarted
is
associated
with
the
second
user,
but
the
skip
jobs
is
still
associated
with
the
original
user
and
we
do
want
to
fix
that
so
that
there
is
a
more
accurate
record
of
who
is
responsible
for
triggering
a
job
that
is
completed
and
eventually
for
that
pipeline
to
complete
as
well.
So
the
proposal
we
have
here
is,
as
it
stated,
change
the
user
of
the
skip
jobs
to
match
a
user
actually
retrying
a
previous
job
and.
A
We're
aware
that,
even
if
you
set
an
aggressive
exploration
policy,
that's
only
one
strategy
for
managing
storage
consumption,
and
certainly
you
want
to
have
the
ability
to
go
through
and
delete
artifacts
in
an
efficient
manner
right
now.
You
can
delete
them
one
by
one,
but
certainly
having
an
endpoint
to
bulk
delete.
Artifacts
would
be
very
useful,
so
those
are
two
of
the
issues
that
I
wanted
to
talk
through
that
we'll
focus
on
in
13.7.
B
I'll
start
sharing
my
screen,
so
I
would
start
with
giving
a
little
context
that
I
hope
it.
My
screen
is
visible
right.
Yes,.
B
So
in
one
of
the
recent
issues
we
provided
this
feature
to
users
that
they
would
be
able
to
keep
the
latest
artifacts
from
a
successful
job
or
pipeline,
and
this
was
delivered
in
this
particular
one
that
I'm
highlighting
the
next
step
that
we
took
was
we
had
created,
like
we
added
a
control
in
in
the
pipeline
settings
in
the
project
level
settings
for
keeping
latest
artifacts
from
successful
jobs.
B
So
there
was
this
toggle
that
we
provided
to
users
that
they
could
switch
on
and
off
based
on
how
they
want
the
behavior
to
be
like.
But
later
we
figured
that
for
self-managed
instances.
It
was
not
possible
for
users
to
opt
out
of
the
feature-
and
this
was
the
consequence
of
this-
was
they
were
ending
up,
storing
a
lot
of
unnecessary
data,
so
in
this
issue
that
we
would
be
working
in
for
for
the
next
milestone,
we
are
providing
a
similar
control,
but
at
instance
level.
B
So
here
you
see
that
there's
again
a
toggle
that
says
that
provides
users
to
option
an
option
to
switch
on
and
off
this
feature
for
keeping
latest
artifacts
from
last
successful
jobs
but
like
if
this
is
switched
off
and
like
this
is
not
opted
for.
This
will
preclude
accessing
this
feature
at
project
levels.
A
Thank
you
victica
again
I'll
link
to
these
issues
at
the
bottom
of
the
video.
We
welcome
your
comments
in
the
issue
just
being
pitaka
or
myself,
we'd
like
to
hear
from
you
anyways
thanks
for
listening
have
a
great
day.
Everyone.