►
From YouTube: GitLab 13.2 Kickoff - Release:Release Management
Description
https://about.gitlab.com/direction/ops/#132-2020-07-22
Welcome to the 13.2 Release Management Kick off! The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages. In 13.2 we are working on depth of the Vault Integration and enriching the Release Orchestration features to support our vision of allowing users to plan and orchestrate releases from wherever they want API, YAML, and UI.
https://gitlab.com/gitlab-org/gitlab/-/issues/24295
https://gitlab.com/groups/gitlab-org/-/epics/2884
https://gitlab.com/gitlab-org/gitlab/-/issues/199250
https://gitlab.com/gitlab-org/gitlab/-/issues/219159
https://gitlab.com/gitlab-org/gitlab/-/issues/28321
https://gitlab.com/gitlab-org/gitlab/-/issues/217355
A
Oh
hi
welcome
to
the
13.2
release
management
kickoff.
As
a
reminder,
the
release
management
team
is
responsible
for
the
categories
of
release,
evidence,
release,
orchestration
secrets,
management
and
get
lab
pages
and
13.2
we're
working
on
the
decks
of
the
vault
integration,
as
well
as
enriching
the
release.
Orchestration
experience
to
support
our
vision
of
meeting
users
where
they're
at
whether
that's
the
API,
the
amyl
or
the
UI
of
get
lab
in
13.2.
We
have
some
really
cool
issues.
Obviously,
so,
let's
go
ahead
and
dive
into
the
first
one
around
setting
deploy
freezes
in
the
UI.
A
This
is
coming
off
of
the
API
extension
that
we
made
available
in
1210,
and
this
is
extending
the
reach
of
setting
a
deploy
freeze
for
the
deploy
team
members
and
release
managers
that
aren't
necessarily
in
the
source
code
or
the
yamo
file
for
team.
So
this
feature
is
a
really
nice
addition
to
the
API
ability
of
setting
a
know
deploy
window
hayano
will
dive
into
the
future
ux
vision
for
deploy
freezes.
B
Remarks
vision
for
the
point
freeze
is
super
exciting
and
cover
multiple
user
stories
such
as
including
the
ability
to
remove
updates
the
boy
freezes
using
UI,
as
well
as
user
stories
that
extend
the
visibility
throughout
the
application
with
alerts
so
that
users,
no
one
on
the
boy
freezes
set
and
they
know
what's
happening
with
their
environment.
Additionally,
since
we
are
asking
users
to
set
the
boy
visiting
UI
using
her
own
syntax,
analyzer
story
is
to
allow
this
non-technical
personas
to
see
human,
readable,
syntax
descriptions
and
UI
so
that
they
can
easily
configure
the
blood
freezes.
B
A
Going
to
be
such
a
nice
feature
for
all
of
our
users
who
are
leveraging
it
deploy
freezes
as
well
as
interesting
and
interested
in
scheduling
no
deployment
windows.
The
next
top
investment
is
extending
our
release
generation
from
the
yamo
file.
This
is
a
cool
feature
around
exposing
the
explicit
steps
inside
of
the
yellow
file
for
the
release.
So,
whenever
the
release,
the
Li
tool
is
generating
a
release,
users
don't
have
to
curl
the
tool
directly.
A
Instead,
they
can
explicitly
call
out
the
steps
for
the
release
generation
as
a
part
of
their
Yama
file,
making
it
very
easy
for
them
to
create
releases
as
a
part
of
their
CI
CD
process.
Kiona
will
discuss
additional
features
where
we're
going
to
be
meeting
users
where
they're
at
and
helping
them
orchestrate
and
coordinate
releases
across
multiple
projects.
Now.
B
Since
we
are
also
investigating
how
to
create
a
single
view
of
the
most
important
and
irrelevant
group
metrics,
such
as
the
number
of
releases
in
the
group,
the
percentage
of
projects
with
releases
and
the
last
five
pass
pipelines
in
a
group,
they
are
fed
by
reporting
on
deployments.
So
right
now
we
have
environments
in
the
ListView
and
we
have
environment
dashboards.
B
We
have
a
few
places
in
the
application
where
you
can
see
and
manage
your
environments
and
deployments
that
don't
really
even
managers,
this
ability
to
track
multiple
projects
at
the
high
level,
the
first
step
towards
what
we
call
the
CIA
CD
dashboards
in
the
sky.
Cd
group
dashboard,
was
to
investigate
which
give
love
UI
components.
We
could
be
used
to
create
this
first
embassy
of
this
dashboard,
so
our
UX
goal
for
13.2
is
to
understand.
B
A
Combination
of
exposing
release
steps
they
amal
file
and
this
view
will
really
help
our
users
plan
and
execute
releases
more
seamlessly.
The
last
investment
firm
13.2
is
executing
on
our
vault
integration
for
CI
CD
jobs.
This
is
the
runner
part
where
we're
enabling
the
gate
lab
runner
to
fetch
and
retrieve
secrets
from
vault
and
inject
them
into
the
CI
CD
jobs
after
we
delivered
the
JWT
authentication
method.
This
feature
will
really
meet
our
bring
your
own
vault
use
case
for
our
premium
users
that
currently
have
a
wall
instance
and
they're.
A
B
We
discovered
that
vault
has
a
different
use
case
for
people
that
are
using
CI
Steve
revels
moving
forward.
We
are
looking
to
match
these
expectations
by
splitting
secrets
and
CI
drivers
in
the
front
end.
We're
gonna
be
working
on
the
design
and
the
ideation
of
this
change
and
the
impact
that
that's
going
to
have
Indians
are
fall.
So
this
item
will
most
likely
require
some
prototyping
and
even
solution
validation,
so
that
we
can
help
our
engineers
determine
the
feasibility
of
this
feature.
If.