►
Description
Jason Colyer, Support Operations Manager, takes us through setting up a repo on gitlab.com and having it mirror to an ops instance. This is specifically for when the source project (ie the one on gitlab.com) does exist.
A
Greetings
all
my
name
is
jason
keller,
I'm
a
support
operations
manager
here
at
git
lab
and
today
we're
going
to
cover
taking
a
repo
that
is
in
getlab.com
and
doing
all.
Let's
see
cid
cd
there
and
moving
it
to
the
ops
instance.
So
ci
cd
is
run
there,
but
code
is
maintained
in
gitlab.com
so
to
get
started.
We
will
make
a
new
project,
we're
just
going
to
call
it
automations.
A
A
A
A
So
what
we
were,
what
we're
going
to
do
for
that
is
we're
going
to
go
to
settings
and
access
tokens
and
we're
going
to
create
one
due
to
the
sense
of
nature
of
an
access
token,
I'm
going
to
do
that
off
screen,
but
essentially
we
give
it
a
name,
select
the
scopes
that
we
need
and
create
the
access
token.
A
A
We
need
the
clone
url
we're
going
to
paste
it.
There
give
it
my
username.
We
are
doing
a
push
for
this
one
we're
going
to
the
targets
token
and
we're
only
mirroring
protected,
so
we're
going
to
go
ahead
and
click
that
to
set
that
up
all
right,
that's
good
to
go
now.
One
thing
we
want
to
do
is
go
to
our
go
to
our
repository
settings
here.
A
And
just
make
sure
that
this
branch
that
we're
going
to
be
marrying
to
isn't
there
so
unprotect
that.
A
A
A
Awesome
so
with
the
mirroring
setup,
we
are
good
to
go
now.
What
we
need
to
do
is
set
up
the
ci
cd
on
the
ops
instance.
So
what
we'll
do
is
set
up,
so
we
need
to
set
up
some
variables
now.
The
first
one
we're
going
to
want
is
run
job
and
that's
going
to
be
set
to
true
on
the
ops
instance.
A
What
we'll
also
need
to
do
is
set
up
the
rest
of
those
due
to
the
nature
of
their
due
to
them
being
a
sense
of
nature.
I'm
going
to
do
that
off
screen,
so
we
would
go
to
ci
cd
go
to
our
variables
and
we're
going
to
just
continue
adding
the
various
ones
that
we
need.
A
So
we're
going
to
go
ahead
and
add
the
url
it's
going
to
use.
So
we'll
add
that.
A
So
I've
got
my
api
token
here.
We
want
to
always
make
sure
we
use
a
unique
one,
so
we
can
tell
them
part
all
right.
So
I'll
go
ahead
and
refresh
here,
so
we
can
see
the
other
ones
were
added
there
we
go.
Those
are
the
ones
we
need
now
over
on
our
main
instance
we'll
go
to
our
ci
cd
and
the
only
one
we
need
is
that
run
job,
so
we're
gonna
set
run
job
to
false.
A
And
we
can
refresh
and
see
it
should
just
have
the
run
job
awesome,
that's
what
we
want
all
right
now,
with
this
in
place,
we're
pretty
much
good
to
go.
It
will
push
over,
but
we
need
to
edit
our
ci
cd
to
match
this
new
system
to
do
that,
we're
going
to
add
some
rules,
but
the
honestly
the
easiest
way
to
do
that
is
to
kind
of
use
ones
we
already
have.
A
A
And
we'll
paste
this
in
there
now
to
give
a
quick
run
through
ruby
3.0.
These
are
the
stages
that
we
use.
This
is
our
script.
We've
got
the
gather.
This
will
run
every
time
on
both
instances
and
then
these
three,
the
from
zendesk,
compare
and
sync
jobs,
will
only
run
if
run.
Job
is
true,
which
is
only
the
case
on
the
ops
instance
over
here.
A
So
we
can
do
that
and
updating
ci
for
mirroring,
we'll
create
our
patch
and
we'll
get
that
pushed
over
and
yeah.
So
once
we
push
that
over
it'll
sync
over
here
and
then
we'll
have
the
ci
cd
running
correctly
in
both
instances,
that's
all
there
actually
is
to
doing
this.
So
I
hope
you
found
this
educational
and
I
look
forward
to
seeing
you
in
the
next
recording.