►
Description
Testing changes in triage-ops policy using dry-run:custom job
Documentation https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/scheduled/index.md#special-schedules
A
Hello,
everyone,
I'm
Alina
part
of
engineering,
productivity
team
and
today
I'd
like
to
share
how
to
test
the
changes
in
policies
for
Tria
jobs
in
order
to
to
see
if
everything
goes
well.
So
in
this
case
we
had
an
issue
to
change
the
filtering
on
documented
the
contribution
sections
under
the
team
report.
A
We
had
to
filter
out
issues
created
by
a
bot
and
after
this
change
was
added.
We
also
had
to
generate
all
the
policies
and
see
this
issue
see
this
change
reflected
for
all
the
groups
and
now,
let's
see
how
to
test
this-
and
we
have
this
in
our
documentation
for
policies
how
to
test
this.
So
we
have
the
dry
run
custom
job
in
our
multiquest,
we'll
go
there
in
in
to
see
how
that
works.
We
have
to
set
up
that
react
policy
file
environment
variable.
A
A
So
in
the
Emoji
Quest
we're
going
to
the
pipelines
tab
we're
going
to
see
our
last
Piper
pipeline
check
that
everything
was
green
and
then
we
have
the
dry
custom
job.
This
will
only
show
the
logs
and
will
not
actually
run
the
report
so
going
there.
We
see
we
have
a
field
to
introduce
the
triage
policy
file
and
then
the
actual
five
part
path,
I'm
testing
with
the
source
code
group,
because
so
there
were
some
issues
there
created
by
the
gitlab
QA
bot.
So.