[JIRA] (JENKINS-57944) project_name tag set incorrectly

3 views
Skip to first unread message

mandy.j.prescott@raytheon.com (JIRA)

unread,
Jun 10, 2019, 5:40:03 PM6/10/19
to jenkinsc...@googlegroups.com
Mandy Prescott-Courville created an issue
 
Jenkins / Bug JENKINS-57944
project_name tag set incorrectly
Issue Type: Bug Bug
Assignee: Aleksi Simell
Components: influxdb-plugin
Created: 2019-06-10 21:39
Environment: Operating System: Windows 7
Oracle JRE - 1.8.0_201
Jenkins - 2.164.2
InfluxDB plugin - 1.17
Chrome web browser
Priority: Minor Minor
Reporter: Mandy Prescott-Courville

Since upgrading from InfluxDB plugin version 1.14 to 1.17 the jenkins_data measurement is now prefixing the project_name tag with an underscore.  From a quick look at the source code it appears that when the "replaceDashWithUnderscore" parameter is false (which is the default) then the code assumes you must have a custom prefix and prepends the project_name tag with customPrefix + "_".  If your Jenkins job doesn't have a custom prefix you end up with an underscore prefixed to the project name.  Looks like the code needs to be changed to something like:

 

String projectTagName;

if (this.replaceDashWithUnderscore)

{             projectTagName = renderedProjectName;        }

else if (customPrefix != null)

{             projectTagName = customPrefix + "_" + build.getParent().getName();        }

else

{         projectTagName = build.getParent().getName();        }

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

aleksi.simell@eficode.com (JIRA)

unread,
Jun 27, 2019, 4:39:02 AM6/27/19
to jenkinsc...@googlegroups.com
Aleksi Simell updated Bug JENKINS-57944
 

Fix implemented. Will be available in the next release.

Change By: Aleksi Simell
Status: Open Fixed but Unreleased
Resolution: Fixed

aleksi.simell@eficode.com (JIRA)

unread,
Aug 5, 2019, 1:28:03 AM8/5/19
to jenkinsc...@googlegroups.com
Change By: Aleksi Simell
Status: Fixed but Unreleased Closed
Released As: 1.23
Reply all
Reply to author
Forward
0 new messages