►
From YouTube: GitLab 13.5 Kickoff - Release:Progressive Delivery
Description
Planning issue: https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/13#note_391349561
A
Hi,
my
name
is
enrico
lewinsky
and
I'm
the
senior
product
manager
for
the
progressive
delivery
group
under
the
release
stage
here
at
gitlab
today,
I
want
to
walk
through
some
of
the
really
exciting
content
that
we
have
planned
for
the
13.5
release,
so
I'm
going
to
go
ahead
and
share
my
screen
and
let's
get
started
so
as
always.
If
you
want
to
walk
through
and
see
what
we
have
planned,
you
can
check
out
the
issue
on
the
progressive
delivery
group
project
issue
number
13..
A
It's
called
pd
13.5
planning
issue
and
I'm
going
to
scroll
down
to
arts
and
the
verbals.
So
one
of
the
first
things
that
we're
going
to
be
working
on
is
a
template
for
deploying
to
aws
cc2.
A
Previously
we
developed
and
delivered
the
option
to
deploy
to
ecs
into
fairgate
and
even
connected
it
to
auto
devops,
and
this
is
again
the
same
systematic
way,
we're
going
to
provide
a
full
gitlab
ciemo
file
that
does
deployment
to
ec2
and
in
the
next
release,
or
so
we
will
also
connect
this
to
autodevops.
A
The
next
issue
that
I'm
really
really
excited
to
talk
about
is
automatic
rollback
in
case
of
failure,
so
we
in
the
previous
milestone,
we
delivered
the
option
to
see
to
view
alerts
on
the
environments
page
and
this.
What
this
does
is
in
case
there's
a
critical
alert
that
you
can
find
on
your
deployment.
A
This
will
do
an
automatic
pullback,
so
there's
going
to
be
a
new
setting
that
can
be
selected
whether
or
not
you
want
to
choose
this
option
to
automatically
go
back
in
case
of
an
error.
But
if
there's
a
critical
error-
and
you
select
this
option,
the
deployment
will
roll
back
to
the
previously
last
successful
deployment.
A
The
next
issue
that
I
want
to
talk
about
is
small
one:
create
job,
stop
ecs
review
apps.
So,
as
I
mentioned
before,
we
added
that
option
to
deploy
to
pcs
using
auto
devops.
However,
we
did
not
have
an
auto
stop
option
for
those
review
apps.
So
this
is
what
we're
adding
in
this
milestone
and
another.
The
next
one
is
api
support
for
forward
deployment
enabled
so
in
a
few
milestones
ago,
we
added
the
option
to
make
sure
that
you
are
always
on
the
current
deployments.
A
So
this
is
not
yet
providing
an
s3
template,
but
it
is
a
addition
to
our
documentation
to
explain
how
you
can
deploy
two
s3.
So
it's
one
step
before
we
actually
add
the
template,
which
is
planned.
So
I'm
really
really
excited
to
see
this
release
be
delivered.
I'm
excited
to
hear
any
feedback
that
you
have.
As
always,
you
can
either
ping
me
on
the
issues
themselves
or
contact
me
at
logalowinski,
gitlab.com
and
I'll
see
you
in
the
next.