►
From YouTube: Single Source of Truth: Examples of practice application
Description
Single Source of Truth is difficult to do at scale, but there are various methods to apply it in a practical way.
This video covers just a few examples of how GitLab does it by generating, embedding, and linking content.
Single Source of Truth (SSoT) is:
- a GitLab subvalue: https://about.gitlab.com/handbook/values/#single-source-of-truth
- TeamOps action tenet: https://about.gitlab.com/handbook/teamops/shared-reality/#single-source-of-truth-ssot
Companion video to blog post: https://cynthiang.ca/2022/12/20/ensuring-a-single-source-of-truth-ssot-at-scale
Written and voiced by Cynthia "Arty" Ng, Acting Chief of Staff to CTO.
A
Hi
everyone,
my
name,
is
Cynthia
ing
that
are
known
as
Artie
Chan
online
and
at
get
lab
and
I'm
here
today
to
talk
to
you
a
bit
about
a
single
source
of
Truth
or
ssot
at
getlam.
Single
source
of
Truth
is
a
sub-value
which
we
consider
important
in
order
to
have
a
single
artifact
for
all
of
our
git
lab
team
members,
users,
customers
and
community
members
as
well.
A
There
are
many
benefits
to
having
an
ssot
with
a
shared
reality
and
for
more
practical
reasons
like
lower
maintenance.
If
you
want
to
learn
more
I'll
link
to
a
companion,
blog
post
in
the
description
in
this
video
I
want
to
focus
on
practical
examples
of
how
we've
applied
single
source
of
Truth
at
gitlab
and
possibly
inspire
you
to
take
similar
actions.
A
So
one
example
is
to
actually
generate
information
on
this
product
page
in
our
handbook.
For
example,
we
list
the
product
managers
in
all
of
their
counterparts,
but
this
is
actually
generated
from
a
single
data
file.
This
allows
us
to
generate
other
Pages,
such
as
the
technical
writing
list
of
assignment
and
the
support,
stable
counterparts.
A
Of
course,
other
times,
written
content
is
not
easy
to
generate,
especially
if
the
wording
is
important.
In
this
these
cases
you
might
embed
the
content
you're
still
using
a
single
Source,
but
then
displaying
the
information
in
multiple
places,
so
at
gitlab
we
use
a
website
generator
where
partials
can
be
included
anywhere
on
the
site.
So,
for
example,
we
have
this
manage
stage
introduction,
which
is
then
embedded
at
the
top
here
of
the
overview
page
and
which
can
be
used
elsewhere
as
well.
A
Other
times,
information
might
reside
in
a
different
tool,
so,
wherever
possible,
you
can
embed
these
too.
So
git
live.
We
frequently
embed
charts
to
show
the
status
of
key
performance
indicators,
and
you
can
see
here
this
engineering
kpi
a
chart
from
a
different
tool
and
it
links
to
where
that
chart
resides
in
our
charts,
dashboards.