►
From YouTube: Ops Section Product Walk Through - Play Around
A
Hey
my
name
is
Kenny
Johnson
I'm,
the
Senior
Director
of
Product
Management,
covering
the
ops
section
here,
get
lab
I'm
gonna,
be
just
recording
myself
messing
around
with
some
parts
of
the
ops
section
that
I'm
not
as
familiar
with.
So
this
is
part
of
an
effort
to
create
a
walkthrough
or
regular
walkthrough
that
I'll
do
to
ensure
kind
of
coherence
or
a
integrated
experience
between
various
components
of
get
lab
covering
this
section.
A
B
B
A
As
well
as
this
static
website,
where
I
was
doing
things
like
using
reviewer,
apps
and
other
features,
so
that
gave
me
a
lot
of
experience
in
how
to
implement
some
of
these
features.
My
previous
projects
here
have
been
have
all
primarily
used,
auto
dev
ops,
so
they
don't
have
any
gate
lab
C
IMO
file
in
them
this
one
specifically
uses
Auto,
DevOps
I've,
used
it
pretty
frequently
in
other
walkthroughs.
A
It's
a
simple
kind
of
crud
Ruby
on
Rails
app
when
I
was
thinking
about
doing,
was
looking
at
some
of
the
other
features
that
I
could
use
in
this
project.
Just
to
start
a
place
to
play
around
so
I
know
that
I
already
use
feature
flags
here
and
those
were
fairly
easy
to
instrument
my
project.
That
is
minted.
A
Done
that
recently,
so
this
is
where
I
said,
the
unleash
context
is
where
I
asked
whether
or
not
oops
ask
whether
or
not
a
specific
VG
flag
was
enabled
before
displaying
or
before
implementing,
and
then
this
is
where
I'd
go
before
displaying.
So,
if
that
feature,
Flags,
maybe
a
little
display
this
random
artisan
Lincoln.
A
B
A
A
B
B
A
A
Okay,
so
I
think
now
I
should
just
have
played
us
left
cool
just
latest.
That
means
that's
the
latest
container
image.
That's
used
to
run
this
application,
cool
I
thought.
Another
thing
I
could
do
was
look
at
releases,
so
I've
never
created
a
release
before
really
sure
how
this
will
work.
Let's
see
tag
name.
Let's
call
this
release
1.0
from
master.
A
A
A
So
you
set
the
master
and
do
day
trips
and
the
release
date.
If
you
release
and
leave
the
milestones
start
date,
blank
set
the
milestone
title
to
the
version
of
your
release,
such
as
version
nine
point,
four,
add
an
issue
to
your
release.
By
associating
the
desired
milestone
from
the
issues,
right-hand
sidebar.
A
Elisa's
feature
this
is
associated
with
massage.
This
can
optionally
be
associated
with
one
of
our
project
mother's
go
enjoy,
including
a
milestone
array
in
your
request
to
release
API
pieces
display
this
association
with
the
milestone
in
cater
top
section
of
the
waste
block.
This
was
added
in
twelve
five.
A
B
B
A
A
B
B
A
B
A
A
B
A
A
A
B
A
B
B
A
A
A
A
A
A
A
A
A
B
A
A
A
A
A
A
A
A
A
B
A
B
A
B
A
A
A
A
A
Schedules
I'm
familiar
with
how
to
add
a
scheduled
jobs,
aren't
any
here,
but
maybe
there's
some
examples
where
I've
done
that
before
okay,
you
can
add
a
schedule,
have
a
custom
interval.
You
can
use
some
other
I
say
just
constant
ax,
say
the
cron
time
zone
target
branch.
Any
variables
then
say
the
pipeline.
Alright
have
specific
only
one
on
scheduled
jobs
to.
A
Okay,
I
think
there
was
an
example
where
I
have
done
that
I
think
so.
Anesthetic
website
is
part
of
that.
Udemy
course
that
I
took
I
think
I
did
add
some
scheduled
CI
jobs
yeah.
This
is
a
daily
run.
I
can
find
it
automatically
with
that
play
button.
This
is
how
I
edit
it.
It
runs
every
day
at
4:00
a.m.
on.
B
A
A
I
can
have
a
custom
CI
configuration
pass,
I,
don't
want
to
be
kill
em,
so
yah
yah
mo
and
my
base
directory
I
can
I
make
these
public
auto
cancel
redundant
pending
pipelines
at
school.
Let's
get
outdated
diploma
jobs
when
I
deployment
job
is
successful,
skip
all
the
job
on
Joe's
right,
oh
yeah.
We
should
do
that.
That's
cool
test
coverage,
parsing.
A
B
A
A
B
A
B
B
A
A
A
A
Okay,
so
those
is
you
had
them
I
doing
this.
This
CI
settings
was
saying
pipeline
status
coverage
report.
I
should
probably
give
me
some
indication
that
I'm
talking
about
badges
and
that
I
could
go
convictive
configure
these
okay.
That
was
interesting.
Sir
I
had
a
new
badge.
Now,
let's
look
yeah
okay,
so
I
should
probably
fix
that
thing.
That
I
did
before.
B
A
A
Have
a
yeah
I've
never
set
up
a
group,
runner
I
could
try
doing
that.
That
might
be
fun.
I
keep
going
through
here.
Variables
got
a
bunch
of
CI
pipeline
variables
familiar
with
how
to
set
those
and
how
to
make
sure
I
should
probably
make
sure
these
are
masked.
No,
actually,
no.
No.
These
are
really
yeah.
None
of
these
need
to
be
masked
they're,
just
useful
variables
for
Auto
DevOps
and
deployed
tokens.
Tokens
allow
read-only
access
to
your
repository
and
registry
images,
so
this
would
be
for
like
BOTS
I
would
imagine.
A
B
A
A
A
A
A
A
A
B
A
B
A
B
A
So,
reflecting
on
this
experience,
couple
places
where
the
documentation
would
have
been
helpful
and
where
I'm
just
seeking
to
understand
how
to
do
some
of
these
tasks,
I
think
as
I'm
thinking
through
what
kinds
of
tasks
would
be
useful
for
this
walkthrough.
There
is
the
whole
process
of
setting
up.
Some
of
these
features
like
defining
your
yellow.
A
Creating
cross
project
experiences
I'm
wondering
if
it
would
be
better
for
me
to
focus
on
using
them
so
creating
and
creating
issues
and
tags
and
releases
and
then
merge
requests
with
pipelines
and
then
processing
a
release,
including
the
documentation
of
that
release
in
within
maybe
like
a
multi
project
setup.
That
might
be
an
interesting
thing
to
set
up
where
I
could
frequently
one
do
the
same,
walk
throughout
that
experience
of
like
adding
some
new
features
to
that
capability
or
that
those
set
of
projects.
A
That
would
let
me
test,
you
know,
pipelines,
jobs,
artifacts,
created
as
a
result
of
Auto
DevOps
pipelines
and
not
on
our
DevOps
pipelines
triggering
between
projects
as
well
as
release,
is
and
the
creation
of
release
artifacts
so
might
be
where
I
start
for
I
walked
through.
This
was
helpful,
especially
I.
Think
in
like
more
walkthrough
I
can
do
other
walkthroughs
about
the
configuration
of
some
of
those
components
as
I'm
configuring
them,
but
the
ongoing
one
might
be
more
useful
in
terms
of
utilizing.
A
The
feature
is
on
a
on
a
daily
basis,
so
I'm
gonna
stop
the
recording,
they're
shooting
me
I'll,
follow
up
with
some
additional
issues
that
I
spotted
in
this
video
and
then
write
that
my
thoughts
in
this
recording
document
section
about
where
I
think
I
should
focus
future
sessions.
Go
thanks.
Everybody
stop
sharing
and
stop.