• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Minor
• Component/s: warnings-plugin
• Labels:

  • plugin
• Environment:

  Hide

  OS: ubuntu 14.04.02
  Jenkins Version: 1.598
  Plugins:
  analysis-core 1.70 true false
  ant 1.2 false false
  antisamy-markup-formatter 1.3 true true
  build-monitor-plugin 1.6+build.140 true false
  build-name-setter 1.3 true false
  build-timeout 1.14.1 true false
  claim 2.6 true false
  conditional-buildstep 1.3.3 true false
  configurationslicing 1.40 true false
  credentials 1.22 true true
  cvs 2.12 false true
  email-ext 2.39 true false
  external-monitor-job 1.4 true false
  greenballs 1.15-SNAPSHOT (private-02/23/2015 09:23-dolby) true false
  javadoc 1.3 true true
  jobConfigHistory 2.10 true false
  junit 1.4 true true
  ldap 1.11 false true
  mailer 1.15 true true
  mapdb-api 1.0.6.0 true false
  matrix-auth 1.2 true true
  matrix-combinations-parameter 1.0.7 true false
  matrix-project 1.4 true true
  maven-plugin 2.8 true true
  pam-auth 1.2 true true
  perforce 1.3.34 true false
  PrioritySorter 2.9 true false
  python 1.2 true false
  run-condition 1.0 true false
  scm-api 0.2 true false
  script-security 1.13 true false
  ssh-credentials 1.10 true false
  ssh-slaves 1.9 true false
  subversion 2.5 false true
  template-project 1.4.2 true false
  timestamper 1.5.15 true false
  token-macro 1.10 true false
  translation 1.12 false true
  warnings 4.46 true false
  windows-slaves 1.0 true false

  Show

  OS: ubuntu 14.04.02 Jenkins Version: 1.598 Plugins: analysis-core 1.70 true false ant 1.2 false false antisamy-markup-formatter 1.3 true true build-monitor-plugin 1.6+build.140 true false build-name-setter 1.3 true false build-timeout 1.14.1 true false claim 2.6 true false conditional-buildstep 1.3.3 true false configurationslicing 1.40 true false credentials 1.22 true true cvs 2.12 false true email-ext 2.39 true false external-monitor-job 1.4 true false greenballs 1.15-SNAPSHOT (private-02/23/2015 09:23-dolby) true false javadoc 1.3 true true jobConfigHistory 2.10 true false junit 1.4 true true ldap 1.11 false true mailer 1.15 true true mapdb-api 1.0.6.0 true false matrix-auth 1.2 true true matrix-combinations-parameter 1.0.7 true false matrix-project 1.4 true true maven-plugin 2.8 true true pam-auth 1.2 true true perforce 1.3.34 true false PrioritySorter 2.9 true false python 1.2 true false run-condition 1.0 true false scm-api 0.2 true false script-security 1.13 true false ssh-credentials 1.10 true false ssh-slaves 1.9 true false subversion 2.5 false true template-project 1.4.2 true false timestamper 1.5.15 true false token-macro 1.10 true false translation 1.12 false true warnings 4.46 true false windows-slaves 1.0 true false

1. 

   24.png

   13 kB

   2015-04-22 06:15

2. 

   31.png

   35 kB

   2015-04-22 06:15

3. 

   36.png

   56 kB

   2015-04-22 06:15

[JENKINS-27377] Custom view does not display job warnings, displays '0'

Collapse comment: Ulli Hafner added a comment - 2015-04-16 15:16

Ulli Hafner added a comment - 2015-04-16 15:16

What is a custom view? A plug-in that you have developed?

Can you please provide more information? Are the warnings correctly shown in the main view? Did you select the correct parser?

Expand comment: Ulli Hafner added a comment - 2015-04-16 15:16

Ulli Hafner added a comment - 2015-04-16 15:16 What is a custom view? A plug-in that you have developed? Can you please provide more information? Are the warnings correctly shown in the main view? Did you select the correct parser?

Collapse comment: Evan Benn added a comment - 2015-04-19 01:30

Evan Benn added a comment - 2015-04-19 01:30

By custom view I just meant the normal filtered list of jobs you can create.
The warnings are shown correctly in the job, they are being counted correctly by the parser.
The only part with an issue is that the column in the view of jobs does not display the same number as is displayed on the job page.
I will try to get a screenshot on Monday.

Expand comment: Evan Benn added a comment - 2015-04-19 01:30

Evan Benn added a comment - 2015-04-19 01:30 By custom view I just meant the normal filtered list of jobs you can create. The warnings are shown correctly in the job, they are being counted correctly by the parser. The only part with an issue is that the column in the view of jobs does not display the same number as is displayed on the job page. I will try to get a screenshot on Monday.

Collapse comment: Ulli Hafner added a comment - 2015-04-19 09:33, Edited by Ulli Hafner - 2015-04-19 09:34

Ulli Hafner added a comment - 2015-04-19 09:33 - edited

That would help! I have an acceptance test that should check the column but maybe in your case a different setup is used.

Please also note which project type is used and how many parsers are defined.

Expand comment: Ulli Hafner added a comment - 2015-04-19 09:33, Edited by Ulli Hafner - 2015-04-19 09:34

Ulli Hafner added a comment - 2015-04-19 09:33 - edited That would help! I have an acceptance test that should check the column but maybe in your case a different setup is used. Please also note which project type is used and how many parsers are defined.

Collapse comment: Evan Benn added a comment - 2015-04-22 06:05, Edited by Evan Benn - 2015-04-22 06:16

Evan Benn added a comment - 2015-04-22 06:05 - edited

I believe I was seeing the issue described above, but this is no longer visible in my project. I think it is safe to call that fix. I do have another feature request:
The number of warnings at the 'view' level is smart about replicated warnings between matrix sub-builds. Within the build, the count of total warning (for the graph, the 'Total' is just the sum of all the warnings.

This might be intended. It causes a problem as there is a mismatch between the number of errors reported by the 'view' and the graph. Another issue is we fairly regularly change the number of builds in our matrix, which causes strangeness with the graph.

I realise it is also possible the column at the 'view' level could be reading only a single sub-build instead of being smart about replicated warnings.
Screenshots to come.

I am using the Matrix build type and 1 parser per build.

Expand comment: Evan Benn added a comment - 2015-04-22 06:05, Edited by Evan Benn - 2015-04-22 06:16

Evan Benn added a comment - 2015-04-22 06:05 - edited I believe I was seeing the issue described above, but this is no longer visible in my project. I think it is safe to call that fix. I do have another feature request: The number of warnings at the 'view' level is smart about replicated warnings between matrix sub-builds. Within the build, the count of total warning (for the graph, the 'Total' is just the sum of all the warnings. This might be intended. It causes a problem as there is a mismatch between the number of errors reported by the 'view' and the graph. Another issue is we fairly regularly change the number of builds in our matrix, which causes strangeness with the graph. I realise it is also possible the column at the 'view' level could be reading only a single sub-build instead of being smart about replicated warnings. Screenshots to come. I am using the Matrix build type and 1 parser per build.

Collapse comment: Evan Benn added a comment - 2015-04-22 06:15

Evan Benn added a comment - 2015-04-22 06:15

Images showing mismatch between view level and build level number of errors.

Expand comment: Evan Benn added a comment - 2015-04-22 06:15

Evan Benn added a comment - 2015-04-22 06:15 Images showing mismatch between view level and build level number of errors.

Collapse comment: Ulli Hafner added a comment - 2015-04-22 10:51

Ulli Hafner added a comment - 2015-04-22 10:51

When you click on the 5 warnings link in image 36 do you then get to the build page in image 31? What is the warning count per axis in your build (image 31)? Did you change the number of axis in that build in the meantime?

Expand comment: Ulli Hafner added a comment - 2015-04-22 10:51

Ulli Hafner added a comment - 2015-04-22 10:51 When you click on the 5 warnings link in image 36 do you then get to the build page in image 31? What is the warning count per axis in your build (image 31)? Did you change the number of axis in that build in the meantime?