►
From YouTube: 2020-09-16 Ops Section Group Conversation - Pre-View
A
A
I'm
really
excited
for
today's
update
got
a
lot
of
content
highlights
to
share
in
this
video.
I'm
really
excited
about
the
gc
and
the
conversation
we're
gonna
have
tomorrow.
So,
let's
just
run
through
the
content
highlights
as
a
reminder.
This
is
my
dog
joining
me.
This
is
the
top
slide
after
that
goes
to
kind
of
the
highlights
from
the
rest
of
the
deck.
The
things
that
I
want
to
highlight
for
tomorrow's
conversation.
First,
I
want
to
start
with
product
performance
indicators.
A
We
had
a
great
product
performance
indicator
review
yesterday,
actually
and
if
you
follow
the
link
in
the
slides
you'll
get
access
to
the
note
stock,
as
well
as
our
products
performance
indicator
page.
A
But
some
of
the
highlights
from
that
conversation
and
our
progress
as
a
section
towards
meeting
our
performance
indicators
of
small
are
that
in
our
package
stage,
which
actually
does
not
have
a
small
goal,
instrumented
or
small
performance
indicator
instrumented
yet
exceeded
their
q3
goal
and
then
set
a
new
goal
for
themselves
and
the
release
stage,
which
does
have
smaug
instrumented
surpassed
100
thousands
now
in
the
last
month,
which
is
awesome
both
great
accomplishments
for
two
stages.
A
If
you
want
to
dig
in
a
little
bit
deeper,
we
also
as
part
of
our
effort
to
make
sure
were
appropriately
balancing
and
focusing
on
some
of
our
core
capabilities,
specifically
in
verify
some
of
the
they're,
not
necessarily
categories.
We
call
them
feature
labels,
but
some
of
the
features
within
verify
that
used
to
fall
on
the
verify.
Ci
group
are
now
going
to
be
the
responsibility
of
the
secrets
management
category
which
lives
in
the
release
management
group
in
release.
A
So
that
is
both
an
effort
to
provide
a
more
holistic
experience
to
our
users,
who
think
of
things
like
deploy,
keys,
variables,
tokens
and
secrets-
that's
very
similar,
as
well
as
make
sure
we're
spreading
our
investment
appropriately
and
allowing
the
ci
team
to
focus
on
kind
of
core
ci
capabilities.
A
Next,
as
part
of
that
realignment
to
from
the
monitor
apm
group,
we
also
created
a
new
group
in
verify
called
pipeline,
offering
they
will
be
focused
on
that
pipeline.
Authoring
experience
the
process
of
offering
your
ci
yaml
it's
great.
We
have
stable
counterparts
in
ux
and
product
to
lead
that
group
that
came
from
the
monitor,
apm
team,
dove
and
nadia,
so
we're
really
excited
for
them
to
hit
the
ground
running
in
that
new
group
things.
I'm
excited
about
the
little
hearts
smiley
face.
A
Logo
is
the
things
we're
excited
about
in
reviewing
all
the
things
that
team
members
contributed
to
what
they're
excited
about
coming
forward.
In
our
roadmap,
though,
the
two
that
I
wanted
to
really
highlight
was
on-call
schedule
management.
This
is
in
our
monitor
group,
the
former
monitor
health
group.
It's
really
a
great
continuation
of
our
focus
on
this
kind
of
end
of
the
devops
loop,
bringing
it
back
into
feedback
for
plan.
A
Where
we're
we
have
great
alert
and
incident
management
capabilities
and
we're
also
going
to
add
on-call
schedule
management
so
think
about
a
complete
devops
team.
Various
team
members
are
on
call
for
any
operational
incidents
that
might
occur.
We
want
to
have
you
be
able
to
perform
that
capability
things
you
would
do
in
a
product
like
pagerduty
right
there
in
gitlab,
in
your
single
devops
platform.
A
Second
thing:
I'm
super
excited
about
is
it's
a
first
step
and
I
love
celebrating
our
first
steps,
but
it's
a
first
step
towards
the
content
that
you
provide
in
your
gitlab
ci
yaml
file
being
presented
in
other
parts
of
the
application,
not
just
driving
pipeline
creation
and
how
the
runner
executes
those
pipeline
creation,
but
also
driving
how
that's
displayed
and
you
can
interact
with
it.
A
The
first
example
that
I
highlighted
was
variable
descriptions
in
pipelines,
so
I'm
excited
to
see
how
you
can
use
driving
the
disk
writing
the
description
in
your
ciemo
file
for
a
variable.
It
would
then
show
up
when
you
click
manually
run
pipeline,
so
that
your
users
who
might
be
running
that
pipeline
who
didn't
create
it,
can
have
a
much
better
experience
in
understanding
what's
going
on
in
their
pipeline
and
what
some
of
maybe
the
default
variables
might
be.
A
The
heart
is
for
our
gratitude
section.
So
moving
on
to
gratitude,
one
of
the
things
I
really
wanted
to
highlight
was
the
monitor.
Apm
team
they've
now
moved
to
other
roles
in
other
groups,
but
they
accomplished
a
number
of
awesome
things
in
our
dashboarding
and
prometheus
integration
and
metrics
and
logging
aggregation
that
were
all
pretty
astounding
for
a
small
team.
A
A
The
celebration
thing
is
about
accomplishments,
there's
a
whole
section
of
accomplishments
in
this
deck.
I
encourage
you
to
look
at
all
of
them.
Some
of
the
ones
that
I
pulled
out
were
matrix
jobs,
cleanup
process
for
the
container
registry,
which
allows
our
users
to
better
manage
their
container
storage
pipelines
for
forked.
Mrs,
it's
a
shorthand
for
allowing
you
to
run
the
pipeline
in
the
parent
project
for
a
fork
demar.
A
A
It
was
originally
released
in
130,
but
you've
seen
the
ability
to
manage
multiple
terraform
states
and
better
access
control
for
the
terraform
state
management
and
then
alert
and
incident
management
has
really
come
a
long
way,
just
in
the
last
six
weeks,
with
improved
capabilities
in
alert
lists
and
instant
management
lists
and
they'll
be
continuing
to
the
monitor
health
group,
we'll
be
continuing
to
iterate
on
that
building
new
capabilities
and,
as
I
mentioned,
even
going
so
far
as
moving
into
on-call
schedule
management,
and
then
I
always
include
a
closing
slide
for
what
today's
international
day
is.
A
Today
is
world
ozone
day.
I
encourage
you
to
take
a
look
at
the
slide
and
follow
some
of
the
links
and
some
of
the
activities
that
you
can
perform
really
highlighted
for
me
that
in
the
past
our
our
whole
world
has
come
together
and
solved
really
complex
global
environmental
problems
and
that
we
do
have
shiny
examples
of
how
we
can
do
that.
So
I
look
forward
to
the
conversation
tomorrow
and
the
questions
and,
as
always,
feel
free
to
ask
us
as
tough
questions
as
you
can
think.