►
From YouTube: GitLab 13.3 Kickoff - Release:Release Management
Description
https://about.gitlab.com/direction/ops/#133-2020-08-22
Allow reporters to deploy protected environments if they are explicitly listed (#225482)
Fire webhook on new deployment (#25344)
Support Releases at the group level (#121476)
Tech eval: Identify all the hard limits of the Environments dashboard that would need to be modified to allow for pagination (#224442)
A
You
hi
welcome
to
the
13.3
release
management
kickoff.
My
name
is
Jackie
Michelle
the
senior
product
manager
over
release
management
here
at
gate,
lab
the
release.
Management
team
is
responsible
for
the
categories
of
release,
evidence,
release
orchestration
secrets
management
and
get
lab
pages.
In
13.2
we
focused
on
the
vault
integration
as
one
of
our
key
items
we'll
continue
that
effort
into
13.3,
but
we're
also
taking
a
moment
to
uncover
better
support
for
managing
deployments
as
an
enterprise
organization.
A
This
will
mean
that
we're
including
non
deployer
permission
options
and
get
lab,
while
expanding
webhooks
to
include
notifications
on
deployments.
Lastly,
we're
going
to
be
enhancing
the
management
of
deployments
at
scale
on
the
dashboard
for
projects
and
environments
to
be
more
exposed,
which
you'll
be
able
to
then
be
look
at
all
of
your
deployments
across
gitlab.
Ideally,
we're
also
co-presenting.
This
kickoff
with
high
Ana's
/
InDesign
she'll,
be
covering
some
future
issues
that
we're
working
on
in
this
current
milestone.
First
up
for
13.3
is
allowing
reporters
to
run
jobs
that
deploy
to
an
environment.
A
What's
really
great
about
this
is
customers
who
have
dedicated
deployers
separate
from
developers
there.
They
can
now
support
that
with
this
functionality
inside
of
get
labs,
it
allows
them
to
maintain
separations
of
duties,
natively,
which
is
a
little
bit
more
challenging
to
do
today.
You
usually
have
to
use
across
projects
or
leverage
different
functionality
and
get
lab
to
maintain
that
continuity
I'm
going
to
pass
it
over
to
Ayane
to
talk
a
little
bit
about
our
plans
around
sharing
production
environments
across
projects.
These.
B
Dekhi
we
have
continuously
working
on
adding
depth
and
in
reaching
the
reason,
management
features
to
support
our
design
vision.
So
this
first
design
item
involves
their
own
supporting
environments
at
the
group
level
by
providing
a
view
of
which
environments
are
shared
across
multiple
projects.
Within
the
same
group,
it's
going
to
address
the
existing
pain
of
our
users
when
monitoring
shared
environments,
but
also
if
the
administration
and
creation
of
across
projects
is
the
foundation
issue
that
will
provide
a
view
of
operational
activities
at
the
group
level,
which
will
be
achieved
through
the
CI
city
group,
dashboard.
B
A
Going
to
be
a
great
feature
that
it's
easily
complemented
by
our
second
13.3
investment
firing
web
hooks
on
nude
appliance
being
able
to
hook
up
get
lab
to
your
existing
ecosystem,
as
a
user
will
be
really
powerful.
With
this
inclusion
of
the
deployment,
ID
and
environment
name
with
inside
the
existing
web
hooks
today,
enterprises
that
are
currently
using
web
hooks
will
be
able
to
easily
trigger
notifications
from
that
event
and
get
lab.
We're
also
going
to
be
investing
in
some
more
quality
of
life
sharing
features
and
get
lab,
which
hayano
will
talk
about.
B
Yeah,
the
next
design
item
is
another
foundational
issue.
By
associating
and
releases
to
group
milestones,
we
are
going
to
be
one
step
closer
to
having
a
global
view
of
what's
being
released
at
the
same
time
at
the
group
level.
So
this
is
a
powerful,
powerful
feature
to
users
that
are
using
group
milestones
today,
they're
going
to
be
able
to
mark
the
time
locks
of
their
releases
in
and
see,
the
plan
addresses
share,
deliver
metrics
in
a
central
place.
At
the
group
level.
B
A
Is
gonna
be
such
a
powerful
feature
for
people
who
are
planning
releases
using
milestones?
The
second
feature
that
we'll
be
spending
some
time
investigating
inside
of
13.3
will
be
around
the
hard
limits
of
the
environments
dashboard.
Today,
the
environments
dashboard
is
limited
by
seven
projects
and
three
environments
per
project,
meaning
users
you
have
over
50
environments,
can't
see
those.
In
the
same
view,
this
issue
will
allow
us
to
unpack
and
uncover
those
limits
and
then
in
the
future,
milestone
deliver
either
nation
or
some
feature
that
allow
people
to
pull
in
more
environments
onto
their
dashboard.
A
B
So
to
continue
with
the
investments
in
the
environments,
Barbie
experience
experience.
We
know
that
today
we
don't
have
a
great
place,
as
Jackie
mentioned,
to
track
in
managing
in
deployment
SQ.
So
we
understand
that
we
need
to
connect
existing
user
flows
in
the
product
and
provide
a
way
for
customers
to
feel
more
confident
when
the
point
immediately.
B
So
this
issue
is
around
investigating
how
we
can
improve
the
experience
for
teams
tracking
and
managing
appointments
at
skills
so
that
they
are
more
invested
and
confident
with
using
environments
and
deployment
in
the
pointman
circuit
lab,
improve,
of
course,
usability
of
a
product
and
offer
a
nonterminating
experience
in
the
environments
dashboard.
We
get
love
I'm.
A
So
excited
for
this
milestone,
we're
investigating
a
lot,
we're
doing
a
bunch
of
design
efforts
and
we're
going
to
be
delivering
some
really
great
quality
of
life
features
for
enterprise
organizations
out
of
release
management.
If
any
of
these
issues
interest,
you
or
you're
excited
to
learn
more
feel
free
to
ping
me
at
J
Michelle
on
any
of
these
issues,
13.3
is
going
to
be
the
best
release
ever.