►
From YouTube: Thoughts on a Group-level Deployment Dashboard
Description
The intent of this video is to propose a simple solution for rolling up deployments across projects.
A
Hi,
my
name
is
tim
poffenberger
and
I
am
a
solutions
architect
with
git
lab
and
I've
been
brainstorming,
some
ways
to
to
improve
our
ability
to
roll
up
environment
deployments
across
across
projects.
I
have
a
customer
that
I'm
working
with
that
really
wants
that
dashboard
level
overview.
A
We've
we've
gone
over
both
the
the
environments,
dashboard
and
the
operations
dashboard
and
they're
they're,
looking
for
something
a
little
bit
more
customizable
and
I
can
go
into
detail
as
to
some
of
the
gaps
that
they're
recognizing,
but
I
had
a
quick,
quick
thought
on
how
we
could
potentially
approach
this
in
a
really
minimum
viable
way.
A
Here's
the
operations
tab
for
a
particular
project.
You
can
actually
see
that
you
know
the
production
environment
has
received
multiple
deployments,
which
is
great
when
we
get
to
the
group
level.
Let's
say
that
you
know
I
have
a
handful
of
projects
and
they've
all
received
deployments.
It
would
be
awesome
if
there
was
some
sort
of
ability
to
see
the
deployments
across
those
projects.
A
Specifically
so
again,
I
have
the
deployments
history
from
over
here
as
well
as
I
have
another
application
called
soa
that
is
also
receiving
deployments
to
production
and
then
some
additional
applications
as
well
and
how
I'm
kind
of
approaching
this
is
it
kind
of
seems
like
within
my
auto
devops
group.
I
have
multiple
areas,
so
I
have
like
a
financial
subgroup
and
this
billing
payments
project
and
an
ebm
project
and
a
soa
project
and
they're
all
deploying
to
the
same
named
environment
production.
A
Another
way
to
look
at
this
is
you
can
actually
see
that
you
know
we
have
this
production
name,
there's
no
relation
between
this
production
and
this
production
and
this
production
in
the
database.
But
let's
just
you
know,
focus
on
the
the
naming
conventions
here.
What
if
we
moved
these
over
here
so
at
the
group
level
we
could
potentially
have
like
production
and
then
forward
slash,
auto
devops,
financial
billing
payments
production,
auto
devops,
ebm
production,
auto,
devops,
soa
and
all
environments
would
then
be
scoped
at
that
production
level.
A
And
then,
when
you
drop
down,
you
could
actually
see
the
the
corresponding
projects.
A
What
this
would
look
like
so
let's
say
that
I'm
in
my
autodevops
group
I
would
have
an
operations
tab
with
an
environments
tab
and
I
could
simply
click
this
drop
down
and
I
would
be
able
to
see
the
different
corresponding
projects
across
my
namespace.
So
I
have
my
names
or
my
soa
project,
my
scoped,
my
subgroup,
scoped
billing
payments
project
inside
my
financial
directory,
as
well
as
my
ebm
project,
and
if
I
click
here,
let's
go
ahead
and
just
click
on
ebm.
A
It
would
then
take
me
to
the
the
production
deployment
page
for
that
given
deployment.
But
the
nice
thing
is.
This
page
really
allows
me
to
see
across
the
the
stages
when
the
last
deployment
was
across
all
of
my
projects,
and
then
these
commits
are
currently
tied
to
a
mock
project,
but
they
could.
These
commits
could
be
potentially
tied
to
all
of
the
other
corresponding
projects
thanks.