►
From YouTube: GitLab 13.6 Kickoff - Verify:Continuous Integration
Description
Issue board for milestone 13.6: https://gitlab.com/groups/gitlab-org/-/boards/1372896?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Acontinuous%20integration&milestone_title=13.6
Issues reviewed in this video:
https://gitlab.com/gitlab-org/gitlab/-/issues/15603
https://gitlab.com/gitlab-org/gitlab/-/issues/241026
https://gitlab.com/gitlab-org/gitlab/-/issues/244831
https://gitlab.com/gitlab-org/gitlab/-/issues/241718
A
Hi
everyone,
my
name,
is
tao
yeager,
I'm
the
product
manager
for
verify,
continuous
integration
and
joining
me
is
project
designer.
A
And
we
want
to
talk
about
the
things
that
we
are
going
to
be
working
on
in
milestone.
13.6
specifically,
there
are.
These
are
the
I
pulled
out
about
four
issues
that
are
key
for
discussion
and
then
feel
free
to
also
check
out
what
we
have
planned
for
milestone
13.6
first,
here
we
have
what
is
essentially
a
collaboration
between
the
ci
team
and
the
runner
team.
We
want
to
allow
the
after
script
to
execute,
even
when
you
have
a
cancelled
and
timed
out
pipeline.
A
Currently,
when
the
your
pipeline
is
cancelled
or
times
out
it,
it
does
skip
any
after
script
that
you
have
in
your
ci
configuration,
and
the
proposal
for
solving
for
this
is
to
introduce
a
new
option
that
is
interruptable
that
when
it's
set
to
the
value
of
graceful,
what
will
happen
is
the
the
application
the
pipeline
communicates
to
the
runner,
letting
it
know
through
the
request,
job
endpoint,
and
what
that
will
do
is
when
this
new
option
is
set
for
interruptible
graceful,
regardless
of
pipeline
not
executing
being
cancelled
or
timeout.
A
It
will
still
proceed
with
ensuring
that
the
after
script
is
run.
This
should
prevent
things
that
you
expect
to
run
for
every
pipeline
to
be
skipped.
Next,
we
have
an
issue.
This
is
a
feature
to
allow
the
keeping
the
latest
artifact
to
be
configurable
at
the
project
or
job
level.
I
think
for
the
proposal
we're
going
to
do
this
at
the
project
level.
First,
currently,
in
our
recent
implementation,
we
made
it
so
the
latest
artifact
for
the
most
recent
successful
pipeline
or
jump
is
always
kept.
A
However,
there
are
times
where
you
don't
want
all
of
those
artifacts
on
the
latest
pipeline
or
job
to
be
kept,
because
it
increases
the
consumption
of
storage,
and
you
want
to
be
able
to
disable
this
at
the
project
level,
I'm
going
to
turn
it
over
to
vitica
to
talk
through
how
we
want
to
we
designed
the
solution
for
this.
B
Thanks
to
so,
as
you
can
see,
from
the
visual
under
the
settings
section
and
in
the
cicd
tab,
what
we
have
done
is
we
have
added
this
additional
section
for
artifacts
which
wasn't
there
before,
and
this
comes
right
after
the
runner
section,
and
we
are
giving
users
this
control
to
check
if
they
want
to
keep
the
latest
artifacts
from
the
last
successful
jobs
and
yeah.
That
would
provide
them
a
better
control
over
their
ci
consumption.
A
A
A
A
B
Okay,
I'm
just
sorry
so
in
this
design
we
have
separated
out
the
enable
pipelines
for
merge,
result
and
enable
more
trains
option
and,
as
you
can
see,
that
enable
moisture
in
option
is
still
sort
of
dependent
on
enable
pipelines
for
most
results.
That
means
that
if
you
check
the
enable
pipelines
for
merge
result
option
the
motion,
option
gets
checked
by
itself
like
it
gets
activated,
and
that
means
that
we
are
communicating
to
the
users
that
for
an
optimal
experience,
they
should
be
like
keep.
B
A
Mithika
and
the
last
issue
I
want
to
talk
about
was
actually
originally
reported,
as
a
bug
what's
happening
is
when
you
have
a
project
subscribe,
the
project
subscription
enabled
there's
actually
currently
not
a
way
to
remove
that
subscription
and
in
reality
this
is
actually
an
enhancement
to
that
feature
and
and
a
a
missed
feature
that
we
want
to
implement,
rather
than
consider
it
as
a
bug.
A
This
is
a
vita.
You
want
to
talk
through
what
the
change
will
be.
B
Yeah
sure
so
the
change
here
is
not
like
a
lot.
It's
a
very
predictive
solution
that
we
have
provided
here
that
earlier
in
the
table.
We
only
provided
the
name
for
the
project
and
the
author,
but
now
there's
also
this
button
that
lets
you
delete
the
subscription.
A
Yeah
thanks
it's
a
small
addition,
but
it
certainly
is
going
to
have
a
huge
impact
for
those
teams
who
want
to
turn
off
a
subscription
for
a
particular
project.
That's
it
that
of
the
the
key
features
that
we'll
be
working
on
in
13.6.