►
From YouTube: Integrating Azure DevOps SCM and GitLab
Description
Using Azure DevOps Repos to manage the code, and GitLab CI/CD to build, test and deploy it. In this video we will demo how to set this integration, and we will demo a development flow.
A
A
A
I'm
selecting
the
ci
cd
for
external
repo
and
repo
by
url,
and
I
can
paste
the
url
and
the
username
and
password
are
optional.
In
my
case,
my
repository
is
public,
so
I
don't
need
to
use
username
and
password.
I
will
give
it
a
name
and
I
will
set
visibility
label
to
public
create
project.
Now
it's
mirrored
the
project
from
azure
devops
to
gitlab
it's
going
very
fast
and
if
you
notice
this
link
mirrored
from
azure
devops.
A
That
means
that
now
any
branch
commit
and
tags
that
they
push
to
azure
devops
will
be
automatically
mirrored
via
pull
command
to
github.
The
next
step
I
will
set
up
ci
cd
in
gitlab,
so
any
push
to
azure
devops
will
trigger
ci
cd
pipeline
in
gitlab.
So
there
are
two
ways
to
make
it
one
way
is
the
easiest
one.
I
will
go
to
cicd
settings.
A
A
What
you
need
is
to
create
a
file
in
the
repository.
The
name
of
the
file
is
dot
gitlab,
ci
ml.
This
is
the
gitlab
cicd
configuration
file
based
on
yaml,
and
this
is
how
it
looks
like
it
has
all
of
the
stages
you
can
include.
Also
yaml
templates
and
here
are
all
of
the
jobs
that
we
want
to
run
so
because
I
have
it
in
the
water
directory
of
this
repository,
I'm
all
set,
and
now
I
can
just
start
the
development.
A
A
Branch
number
five,
and
this
is
what
I
added
so
this
change
now
should
be
reflected
in
gitlab,
so
I'm
going
to
get
a
window
and
I
will
go
to
the
branches
and
I
will
look
for
the
branch
and
I
see
it's
not
the
area
I
can
always
manually
sync
it.
So
I
will
go
to
the
repository
settings
and
mirror
repository.
A
A
I
can
see
now
brand
number
five
and
the
text,
and
I
see
this
icon
means
the
pipeline
is
running.
I
can
open
the
pipeline
from
here
or
I
can
go
open
it
from
here,
and
this
represents
my
pipeline
graph,
as
I
defined
in
my
gitlab
ci
cdml.
I
have
a
few
stages,
build
test,
review,
dust
performance
and
cleanup
the
builder
succeed,
and
now,
if
I
open
the
container
registry,
I
can
see
a
new
folder
for
my
branch.
I
can
click
on
it
and
I
see
the
images
that
it
created
for
my
source
code.
A
I
go
back
to
the
pipeline
and
I
see
that
it
started
at
the
test
stage
and
it
will
run
a
few
tests.
Security
scans
license
scanning
from
here.
You
can
access
each
job
and
see
what's
happening
and
on
the
right
side
you
can
see
details
about
the
job.
You
can
cancel
job,
you
can
retry
job.
If
a
job
failed,
you
don't
have
to
restart
the
entire
pipeline.
You
can
just
fix
something
and
restart
a
specific
job.
A
If
tests
are
defined
in
this
cicd
pipeline,
you
will
see
the
test
status
here.
In
this
view,
the
security
tab
lists
all
of
the
vulnerabilities
that
the
scans
found.
You
have
a
few
types
here:
container
scanning
dust
dependency,
scanning
and
zest
and
for
each
vulnerability
you
can
click
and
get
more
details.
A
A
This
will
trigger
additional
pipeline
in
gitlab.
The
new
pipeline
will
run
now
on
the
master
branch.
I
will
open
the
pipelines
and
soon
we
will
see
a
new
pipeline
starting
and
the
pipeline
will
be
different,
because
this
pipeline
will
be
not
only
continuous
integration
pipeline,
it
will
be
cicd
pipeline
new
pipeline
started
and
if
I
go
here,
the
pipeline
now
is
running
on
master,
and
this
is
the
commit
message
which
is
merged,
and
if
I
open
this
pipeline,
I
will
see
a
little
bit
different
graph.