From 3a0f235ede035a9a3e160043deaf80956ce34034 Mon Sep 17 00:00:00 2001
From: Guillem Jover <gjover@sipwise.com>
Date: Thu, 27 Apr 2017 19:05:23 +0200
Subject: [PATCH] TT#14963 Improve perlcritic output message

Give more information relevant when fixing the reports, state the
perlcritic tag, and the line that triggered the error.

In addition point to the Sipwise overrides that we are applying so
that it is clear when we diverge from the suggested best practices.

Change-Id: I795a29306d0f9923a402170c93cca73bbf730f14
---
 modules/jenkins/files/perlcriticrc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/jenkins/files/perlcriticrc b/modules/jenkins/files/perlcriticrc
index 2f0b357..63d1e3e 100644
--- a/modules/jenkins/files/perlcriticrc
+++ b/modules/jenkins/files/perlcriticrc
@@ -2,8 +2,8 @@
 
 # NOTE: When switching the output format we also need to adjust perlcritic_tap
 # accordingly:
-# verbose = %f line %l col %c\n    [%s] %p (%e) = %m\n    %r\n
-# The ouput format, another nice one is 8, the [%s] is the severity.
+verbose = %l:%c [%s] %p = %m (with Sipwise overrides from <https://gerrit.mgm.sipwise.com/gitweb?p=puppet-sipwise.git;a=blob;f=modules/jenkins/files/perlcriticrc>) near '%r'\n
+
 severity  = 4
 
 program-extensions = .pl .t