►
From YouTube: CI/CD Minutes visibility / tracking update May 2022
Description
This video is an update to the initial April walkthrough (https://youtu.be/NgHtnYR2qVo).
- The bug for incorrect Month display can be tracked here: https://gitlab.com/gitlab-org/gitlab/-/issues/357909
- Other UX issues are being tracked here: https://gitlab.com/gitlab-org/gitlab/-/issues/363029
- These are both part of this epic: https://gitlab.com/groups/gitlab-org/-/epics/7561
A
A
A
So
similar
to
the
last
video,
this
is
in
my
personal
namespace,
and
this
is
just
within
the
preferences
and
then
the
usage
quotas
and
that's
where
we're
starting
from
so
I
am
happy
to
say
that
this
view
does
now
include
the
shared
runner
duration,
so
you're
able
to
see
that
you're
going
to
see
this
tabbed
treatment
here
and
in
some
other
places.
So
you
can
look
at
your
ci
cd
minutes
and
your
shared
render
usage
in
the
same
spot,
not
toggling
between
different
pages
back
and
forth.
A
You
will
notice
that
we
do
still
have
a
bug
or
that
there
is
a
bug
where
we
default
to
and
hold
view
the
team
is
working
on
a
fix
for
that,
so
that
you
get
the
latest
data
right
away,
so
don't
be
concerned
if
you
land
on
this
page-
and
you
see
no
usage
you're,
just
looking
at
not
the
latest
date,
so
we
can
see
that
we
have
the
ci
cd
minutes
as
well
as
the
shared
winner
usage.
We
do
still
have
a
bug
where
shared
runner
usage
is
showing
the
wrong
month.
A
It's
off
by
a
month.
Here,
you'll
see
this
graph
kind
of
jump
around
high
ci
cd
usage
in
april
of
36
minutes
and
that
matches
up
with
high
ci
cd
usage
in
february
here-
and
this
is
just
off
by
a
month.
So
really
april
is
what
is
counting
for
may
so
so
that's
still
a
bug
there.
We
do
have.
The
usage
by
project
includes
both
our
cscd
minutes
and
our
shared
render
usage,
and
this
graph
is
now
sorted
by
the
ci
cd
minute
usage
descending.
A
So
you're
going
to
see
your
projects
that
have
the
most
usage
on
top
this
matches
with
what
the
table
underneath
it
is
showing
for
the
current
month
as
well,
and
so
now
this
is
going
to
exclude
projects
that
have
zero
minutes.
You're
not
going
to
see
those
in
here
because
they're
not
a
value
to
you
as
you're,
looking
for
what's
using
my
minutes
over
the
course
of
this
month.
A
So
now
this
will
be
sorted
so
that
you
can
scroll
through
and
quickly
see,
which
are
the
projects
that
are
taking
all
of
the
minutes,
and
we
have
that
graph
as
well
for
our
shared
runner.
So
I
wanted
to
call
out
the
difference
here
between
these
two,
so
you
can
see
my
blog
project
here
only
has
a
couple
of
it
has
a
couple
of
shared
runner
minutes,
but
no
ci
cd
minutes
and
I'm
gonna
reiterate
what
I
said
in
the
last
video.
A
That
is
because
we're
not
counting
those
cicd
minutes
yet
for
projects
created
for
july
of
2021..
We
are
going
to
change
that
on
june
1st,
so
on
june,
1st
all
public
projects
will
have
their
cicd
minutes
counted.
So
if
you're
as
you're
getting
closer
to
that,
you
want
to
understand
what
projects
are
using.
Now
you
can
look
at
that
shared
runner
usage.
A
The
other
bug
that
I
want
to
call
out
here
is
the
shared
runner
usage.
This
is
not
700
minutes.
This
is
700
seconds.
The
team
already
has
a
change
open
and
I'm
hopeful
by
early
next
week
that
this
will
be
showing
minutes
across
the
board.
It
is
we're
really
sorry
that
this
isn't
labeled
of
what
it's
using
and
what
that
calculation
is
incorrect,
so
we'll
get
that
fixed
up
right
away
on
gitlab.com.
A
So
this
view
looks
very
familiar.
Everything
is
under
the
pipelines.
Tab
now
we've
gotten
rid
of
that
shared
duration
tab
because
we're
using
that
same
view
of
ci
cd
minutes
usage
and
shared
render
usage
so
that
you
can
see
all
of
it
in
one
spot
same
bugs
persist
here
of
defaulting
to
the
older
date.
First,
so
you
need
to
click
to
get
to
2022
and
then
you'll
see
the
most
recent
as
well
as
the
month.
Date
of
this
is
really
data
for
may
not
april.
A
I'm
showing
my
minutes
here
of
26
year,
runner,
duration
and
8
19
rather
cicd
minutes
same
things
exist
here.
We're
sorting
this
graph
again
by
the
cicd
minutes
descending,
so
you
can
see
which
of
your
projects
are
the
ones
consuming
those
minutes
I
did
want
to
call
out
again.
You
see
a
little
bit
of
a
difference
here
with
the
shared
runner
usage
here,
showing
7.6
with
the
cicd
minute
showing
zero
and
that's
because
of
that
cost
factor
that
we're
going
to
apply.
A
So
all
those
public
projects
that
are
getting
shifted
over
and
all
the
public
projects
today
are
using
a
cost
factor
to
actually
calculate
the
cicd
minutes.
You
have
more
shared
runner
duration
than
the
400
cicd
minutes
and
I'll
link
to
our
documentation.
That
explains
the
cost
factor
calculation
and
the
current
cost
factor
as
it
exists
today.
A
So
you
can
more
easily
scroll
through
and
look
at
what
is
using
your
minutes
and
if
a
project
hasn't
doesn't
use
any
shared
runner
or
ci
cd
business
for
the
month,
it's
not
going
to
show
up
in
the
table
and
then
one
of
the
next
enhancements
the
team
is
going
to
be
working
on
is
getting
that
table
view
for
past
months,
not
just
the
current
month,
so
that
historically,
you
can
look
back
and
see.
How
much
did
these
projects
use
over
time
as
much
as
we
have
the
data
for
it?
A
So
those
are
some
of
the
changes
that
we've
made
in
15
0
on
the
pipeline
execution
team.
To
those
two
pages
I'll
link
to
the
april
video,
which
has
a
bunch
of
the
issues,
descriptions
or
the
issues,
rather
that
talk
about
this
work
as
well
as
the
epic,
that's
tracking,
all
of
this
work
and
the
documentation
link.
If
you
have
any
questions,
please
feel
free
to
comment
on
the
video
I'm
keeping
track
of
that
or
you
can
email
me
at
jheimbug,
gitlab.com
and
I'll
include
my
email
address
in
the
video
description
thanks
so
much.