►
From YouTube: GitLab Code Quality: Speed Run
Description
An update to this video has been created and uploaded showing features implemented since the original recording: https://youtu.be/4pJcrvZfGQU.
In this project I show how to add the code quality job to a pipeline and how changes to code quality are shown in the merge request.
Code Quality documentation: https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html
The project from the demo: https://gitlab.com/jheimbuck_gl/jh_java_example_project
A
So
here
we
have
just
a
really
small,
simple
hello
world
Java
project
and
I've,
already
added
our
code
quality
job
into
the
get
lab,
CI
llamo
file.
You
can
see
it
here
in
the
get
live,
CI
llamo.
You
include
for
the
template.
That
includes
everything
we
need
for
the
job
and
then
I've
also
specified
an
artifact
path.
That's
gonna!
Let
me
download
that
resulting
JSON
every
time
this
job
runs.
A
So
if
I
look
at
the
merge
request
that
I
added
this
in
will
see
that
my
code
quality
job
ran,
but
I
don't
have
in
this
merge
request
anywhere
the
code
quality
widget
showing
me
what's
changed
and
that's
because
this
is
the
first
time
that
is
right.
But
if
we
go
into
the
job
itself,
we'll
see
that
there
is
a
job
artifact,
the
resulting
JSON,
that
we
specified
and
see
it
uploaded
the
artifact
there
that's
great,
we
can
browse
to
it
and
we
can
then
download
it,
and
in
this
case
it's
just
an
empty
file.
A
There's
nothing
really
going
on
in
this
hello
world.
Yet
that
is
it.
No
I
also
want
to
call
out
that
here
it
says
that
the
artifact
is
going
to
be
removed
in
six
days,
so
by
default.
That
file
is
kept
around
for
seven
days.
So
if
you're
only
running
your
pipeline's,
you
know
once
every
two
weeks
or
once
a
month,
you
might
want
to
override
that
with
the
expire
in
keyword,
and
you
can
set
that
to
keep
for
you
know
30
days,
if
you
need
so
you
always
have
access
to
that
report.
A
All
right.
So,
let's
get
back
into
our
little
hello
world,
and
here
we
just
have
well
Java
file
and
I'm
gonna
get
into
the
web
IDE.
It's
my
favorite
way
to
make
changes.
So
I
know
that
the
climate
engine
that
we're
using
is
going
to
come
if
the
method
has
a
whole
bunch
of
different
inputs.
So
I'm
just
gonna,
add
a
bunch
more
of
these
here
and.
A
All
right,
sir
pipeline
finish
running
and
we
can
see
in
merger
quest
to
update
our
helloworld.java
file.
We
have
now
that
could
quality
merge,
request,
widget,
as
we
call
it,
we
can
see
the
code.
Quality
degraded
on
one
point
mean
expand
this
and
it's
going
to
show
us
all
of
the
various
changes
more
there's
degredation
Zoar
improvements.
If
those
happen
in
the
in
there
as
well,
and
then
it'll
link
you
to
where
there's
that
change,
and
so
here,
as
we
see
here
it,
there
are
a
number
of
arguments
and
that
method
is
just
too
high.
A
It
exceeds
the
four
allowed.
We
should
consider
refactoring
that
so
it's
smaller
method
and
a
link
to
that
file.
So
we
could
go
back
and
fix
that
up
and
take
care
of
it.
So
that's
how
that
code,
quality
code,
quality,
feature,
works
and
kind
of
the
default
code.
Climate
engines,
kind
of
the
things
that
they're
going
to
trigger
on
and
one
of
the
things
that
they're
going
to
trigger
on.
So
that's
how
we
go
ahead
and
get
that
set
up.