►
From YouTube: CI Adoption Journey - DRI Conversation
Description
The UXR team at GitLab met with with Dir of Product Mgmt for CI/CD, Jason Yavorska, to learn more about the CI Adoption Journey effort.
A
B
A
It's
a
good
way
to
put
it
all
together,
but
we
just
weren't
really
sure
like
so
what
we
wanted
to
do
today
was
bend
your
ear
for
about
half
an
hour
around
this
project.
I've
talked
to
Kenny
about
it.
A
little
bit.
I've
talked
to
Christi
about
it
a
little
bit,
but
you
and
I
Andre
have
not
gotten
to
talk
yet.
So
the
though
too
long
didn't
read,
I'll
be
the
DRI
from
the
research
perspective,
but
under
and
I
will
be
partnering
together
with
this,
so
we're
here
to
just
find
out.
C
A
B
The
two
main
pads
I
guess,
I
would
say
to
improving
things,
are
building
features
that
help
people
so
like
that
help
people
adopt
gitlab,
who
would
otherwise
be
blocked,
it's
kind
of
an
awkward
way
to
say
it.
But
it's
it
means
like
if
we're
missing
features
that
make
it
really
hard
for
them
to
implement
their
pipeline
definition,
then
they
get
blocked
at
some
point
in
their
like.
Well,
we
can't
grow
with
you
anymore,
or
we
have
faxing
or
we
couldn't
even
start
with.
B
You
like
mobile,
is
a
good
example
of
that,
where
you
already,
if
you're
doing
mobile
from
the
very
beginning,
you're
having
to
do
some
kind
of
strange
things
that
are
not
so
easy
to
do
so
features
that
we
released
recently
like
rules.
Child-Parent
pipelines
are
all
about
that
track,
which
is
just
kind
of
unlocking,
more
complicated,
workflows
and
hopefully
doing
it
in
a
way.
That's
that's
easy
to
understand.
B
Then
the
other
is
well
mark.
Pentek
was
calling
like
the
journey
to
your
first
green
pipeline
and
trying
to
accelerate
that
and
that's
what
that
get
up
and
running
quickly
with
get
live.
Ci,
epic
is
really
all
about.
Is
you
know
a
lot
of
times
you
the
first
time
you
import
a
project
or
whatever
or
even
just
start
writing
code,
and
you
make
your
first
commit.
B
Or
four
months
ago,
maybe
even
longer,
now
time
flies,
but
they
just
sat
there
and
is
sitting
in
that
same
state.
I've
been
continuing
to
add
more
items
to
it
and
I
come
across
them
because
I
wanted
us
to
always
to
get
back
there,
but
but
it's
really
still
in
the
same
place
is
the
last
place.
Last
time
we
talked
about
it,
so.
B
Two
tracks
and
and
doing
some
research
and
having
like
a
research
partner
to
help
validate
semester,
I
think
would
be
great.
I
was
a
you
know:
I
did
this
job
doing
build
engineering
release
engineering
that
sort
of
thing
for
a
long
time
so
I
have
a
I,
have
my
own
perspective
as
a
user,
which
is
a
good
user
perspective,
but
it's
also
just
one,
and
so
it
still
needs
to
be
validated
against
how
things
are
evolving
and
what
our
customers
are.
B
Looking
for
and
we've
had
some
stumbles
with
some
of
the
features
we
released
recently
like
rules
like
still
nobody
understands
it
and
we're
trying
to
figure
out
how
to
talk
about
the
feature
in
a
way
that
people
can
like
there's
been
six
reef
actors
of
the
documentation
to
try
and
make
it
clear,
but
I
think
it's.
Ultimately,
it
was
just
a
confusing.
It
was
confusing
from
the
start,
and
so
we're
trying
to
clean
that
up
and
having
some
more
research
in
there
I
think
probably
could
have
helped
that
situation.
B
B
B
B
Most
people
understand
kind
of
like
the
general
principles
of
a
build
system
who
would
be
trying
to
get
something
working.
There
is
a
smaller
subset
of
users
who,
just
like
I've,
never
done
a
build
before
and
I
wonder
what
that
would
be
like
and
I
wonder
what
a
build
is
and
we
should
validate
actually
how
many
of
them
there
are
one
of
the
interesting
about
things
about
our
product.
A
A
C
A
Use
gitlab
and
that's
like
the
third
time,
has
come
up
in
the
past
week,
so
that
might
be
something
that
we
dive
into
for
this
because
they
don't
know
if
we
really
have
looked
at
it
yet
ever
other
than
like
I
said
I
eat
like
a
glance
at
it
in
in
terms
of
other
personas
that
you
feel
are
important
for
this
project.
I
assume,
like
the
software
engineer,
the
DevOps
engineer,
yeah.
B
It's
the
way
it
lines
up
its.
It
tends
to
almost
always
be
the
DevOps
engineer
or
the
person
like
for
it.
A
smaller
company
it'll
be
the
software
engineer,
but
it
will
be
them
with
their
DevOps
engineer
hat
on,
because
it's
the
person
who
makes
the
build,
which
is
typically
not
you
know
it's
either
a
shared
responsibility
amongst
everybody,
or
somebody
happens
to
be
good
at
it
and
they
get
it
or
if.
B
B
Related
to
the
build
system,
but
then
there's
also,
you
know
on
an
ongoing
basis.
If
you're
just
an
engineer,
you
still
enter
with
the
build
system
in
small
ways
to
say
like
okay,
we
have
this
new
component.
We
need
to
build
so
I
can
probably
wire
that
in
I
kinda
need
to
go
to
the
central,
build
expert
person
to
tomorrow
that
in
so.
B
B
B
C
B
More
like
appendix
then
no
doc,
but
we
really
need
some
kind
of
like
layered
approach
like
you
or
even
a
choose-your-own-adventure
kind
of
thing,
where,
like
you,
here's
you
know,
here's
like
the
five
ingredients
to
make
a
basic
CI
pipeline
start
with
these,
and
here
here's
our
list
of
things
where
you
might
go
next,
like
are
you
doing
darker,
then
go
check
out
this
page
and
they'll.
Tell
you
some
of
our
cool
features
that
relate
to
that.
Are
you
doing
communities
you
know
check
this
out?
B
C
B
Key
words
like
parallel
and
stuff
yeah,
you
know
you
sort
of
have
to
know
about
them
in
order
to
know
them,
and
if
you
don't,
then
you
might
generate
a
bunch
of
jobs
and
write
off
all
the
gamble
by
hand
when,
in
fact,
we
have
this
parallel
keywords
that
you
know
make
fifty
copies
of
this
job.
And
so
how
are
we
affecting
finding
the
realizing
that
somebody
intends
to
do
that
and
then
guiding
them
to
the
parallel
keywords
like
we're
not
doing
a
good
job
that
other
than
to
say
like?
B
C
B
B
B
Exact,
you
could,
just
you
know,
get
results
instantly
and
then
some
of
the
more
advanced
cases
like
includes
it's
even
just
difficult
to
try
and
understand
what
happened,
and
we
have
rules
as
well
either
only
accept
or
that
actual
rules,
keyword
and
so
those
are.
You
can
set
up
things
like
only
run
this
job.
If
there
are
changes
on
this
certain
file,
so.
C
B
That's
something
else
that
we
could
do
to
make
things
easier.
One
feature
we're
coming
out
with
soon
is
an
improvement
for
the
linter,
where
it
will
do
better
linking
and
it
will
also
give
warnings,
and
we
can
use
that
to
mention
deprecations.
We
can
use
that
to
mention
things
like
hey.
We
noticed
you've
got
like
20
jobs
that
all
have
basically
the
same
name.
Perhaps
you
intended
to
use
the
parallel
keyword
or
something
like
that,
and
that
can
be
a
way
for
us
to
turn
guide
people
to
good
features
and
better
practices
and.
B
B
A
A
Other
things,
okay,
so
all
the
things
that
are
in
the
meta
epoch
are
all
the
things
that
you
kind
of
just
went
over
like
all
these
improvements
that
we
can
make
to
help.
People
have
an
easier
time
using
it
adopting
to
it,
based
on
whatever
they've
used
before
and
then
pushing
that
usage
past
the
lower
level
to
the
higher
a
little
more
complex
pipelines
and
more
complex
usage
to
get
them
to
stay
right.
Yeah.
B
B
B
So
that
needs
to
be
done
and
then
also
the
comments
in
there
I
would
say.
Are
it's
just.
You
could
almost
look
at
it
as
just
like
a
database
of
responses
to
a
good
question
like
how
could
you?
How
would
you
make
it
live
easier
to
use?
At
least
you
know
between
six
months
ago
and
four
months
ago,
that
two
months
it
was
just
people
adding
responses
there
yeah.
B
B
C
B
The
other
hand,
some
kind
of
voting
might
be,
might
be
interesting
to
do
like
find
the
themes
in
the
in
the
issues,
because
they're
not
grouped
in
any
way
right
now
and
then
maybe
just
pull
all
those
users
in
the
thread
and
or
and
look
at
their
responses
and
say
like
which
of
these
seem,
which
of
these
themes
for
issues
seems
to
line
up.
That's
going
to
make
the
most
difference
for
people
and
then
maybe
try
and
start
moving
on
some
of
those.
So
in
that
way,.
A
C
Wanted
to
ask
about
the
other
stages
that
could
be
involve
are
currently
involved
in
that
issue
that
came
in
created.
He
was
talking
about
it
as
for
stage
project
between
source
code
management
and
ops.
Basically,
so
what
what
other
stakeholders
might
lead
might
be
involved?
Perhaps
some
people
from
create?
Maybe
someone
from
growth
I
know
that
drugs
theme
has
on
their
page
exactly
CI
adoption
related
project.
B
So
that's
a
great
point:
I
meant
to
mention
earlier,
but
I
totally
forgot.
The
growth
team
has
been
doing
really
interesting
things
and
helping
people
start
using
CI,
which
sort
of
touches
on
that
there's
been
some
small
overlap.
They're
not
really
helping
people
understand
CI,
really
but
they're,
prompting
people
to
take
a
look
at
CI,
which
is
sort
of
the
first
step
towards
and
they're
doing,
things
like
linking
to
documentation
and
I
think
so.
There's
a
small
overlap.
There.
C
B
I
think
coordinating
with
them
a
little
bit
is
good
to
you
and
they
may
have
some
perspective,
because
the
goal
of
all
of
this
is
to
drive
to
drive
more
users
over
the
stage.
Specifically,
the
goal
here
is
to
drive
more
I,
would
say,
usage
of
verify
and
then
that
we
get
downstream
benefits
from
that
in
various
places.
B
Then,
if
the
growth
team
can
help
us
with
that,
the
related
stages
that
you
were
asking
about,
I
think
the
ones
that
are
most
closely
related
I
was
actually
surprised
to
hear
you
say:
source
code
management.
Although
Ken
you
may
have
something
in
mind
that
I'm,
not
thinking
of,
in
which
case
we
should
just
double-check
that
and
figure
out.
What
can
you
talk
about?
B
Those
are
probably
the
two
most
directly
connected
downstream
ones
and
then
beyond
that,
we've
got
like
monitor
in
ops,
which
is
downstream
from
release,
and
you
know,
if
we're
not
deploying
to
their
environment,
if
they
haven't
set
up
their
environment,
then
we
have
no
way
to
monitor.
But
if
both
of
those
things
are
happening,
when
we
can
connected
monitoring
and
show
people
really
cool
things,
probably
that
answers
your
question
a
bit
yeah
sure.
C
C
C
B
B
B
A
C
B
C
A
B
Has
his
own
make
runner
easier
to
use
epic
and
it's
how
its
improved
the
way
you
can
deploy
the
runner
to
manage
the
resistance?
Recently,
it's
got
in
product
guidance
for
how
to
set
it
up
and
docker
and
do
other
things.
Maybe
he's
gonna
eventually
work
on
the
get
LeBron
or
exec
as
well,
but
he's
also
got
like
the
runners
as
a
service
thing
that
he's
investigating
and
yeah
that
one
is
the
CEO
interest
item
and
on
their
inside.
C
B
B
For
it,
because
everybody's
build
environment
is
a
little
bit
different
and
you
have
to
use
real
Hardware
because
there's
no
such
thing
as
like
a
virtualized,
Mac
and
so
you're
dealing
with
like
plugging
things
in
and
exposing
them
to
the
Internet.
And
so
you
got
all
these
steps
that
you
got
to
do
and
there's
companies
out
there
that
offer
managed
Macs
and
the
cloud
and,
and
so
maybe.
B
Probably
just
yeah
pick
some
next
steps
and
and
just
start
moving
in
one
area.
The
other
I
like
Darren
I
feel
like
has
a
really
good
handle
on
his
area,
and
it
doesn't
need
a
ton
of
attention
because
he's
already
prioritizing
it
now
that
doesn't
need
research,
but
we
don't
what
I'm
saying
is
we
don't
necessary
have
to
start
there
where
I
would
like
to
start
is
on
that
big
epic
and
trying
to
just
kind
of
like
make
sense
of
it
in
some
way
and
and
find
out.
B
B
Step
is:
did
you
do
some
kind
of
survey
or
customer
contact
out
of
that
epoch
and
say
hey?
You
know
we're
coming
back
around
to
this.
Here's
all
the
issues
that
we
found
and
here's
the
teams
that
we
found
them.
Here's
all
the
comments
that
were
in
there
and
here's
the
themes
in
the
comments
that
we
found.
You
know,
how
would
you
where?
Would
you
like
us
to
start
considering
all
these
things
like
you
know,.
A
B
B
A
B
B
Yeah,
maybe
we
need
a
collaborative
space
as
well.
I,
don't
know
I'm
totally
open
to
whatever
UX
research
approach.
Other
groups
are
using,
otherwise
I'll
just
do
whatever
I
do
anyway
and
then
we'll
work.
What
it
may
not
be
the
most
efficient
and
so
I'm
happy
to
be
informed
and
led
a
little
bit
and
when
it
comes
to
figuring
out
the
UX
research
stuff,
yeah.
A
No
worries,
don't
worry,
son,
yeah,
well,
I
think
what
Andre
and
I
need
to
do
is
put
our
heads
together
now
that
we
go
chance
to
talk
with
you
and
got
some
more
context
around
that
that
epic
and
got
a
lot
more
information
than
had
before
and
then
we'll
come
up
with
a
plan
and
I
love
the
idea
of
a
big
group
kickoff
and
having
a
place
for
us
all
to
kind
of
talk
about
this.
Nobody
else
is
doing
it.
Yet
this
is
like
the
biggest
it's
real
first
strategic
kind
of
situation.