-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins ver. 2.32.3
RHEL 6.4
Java 1.8.0_60-b27
static analysis_core 1.82
When browsing warnings some of the links appear to be broken since version 1.82 of the analysis-core plugin.
I tried reverting to analysis-core version 1.81 and everything is working correctly so there has been a regression here.
To give you an example, when I browse to:
http://jenkins/job/jobname/125/warnings2Result/
There is a link shown on the "Types" tab to:
http://jenkins/job/jobname/125/warnings2Result/category.-52074025/
but following that link redirects back to:
http://jenkins/job/jobname/125/warnings2Result/
I wonder if it is related to the following bug: -JENKINS-37195
- is duplicated by
-
-
- Resolved
-
[JENKINS-42820] Regression in analysis-core:1.82 when browsing warnings
Andrew Barnish
created issue -
Andrew Barnish
made changes -
| Description |
Original:
When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin. I tried reverting to version 4.58 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] There is a link shown on the "Types" tab to: [http://jenkins/job/jobname/125/warnings2Result/category.-52074025/] but following that link redirects back to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] I wonder if it is related to the following bug: https://issues.jenkins-ci.org/browse/JENKINS-37195 |
New:
When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin. I tried reverting to version 4.58 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: [http://jenkins/job/jobname/125/warnings2Result/] There is a link shown on the "Types" tab to: [http://jenkins/job/jobname/125/warnings2Result/category.-52074025/] but following that link redirects back to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] I wonder if it is related to the following bug: https://issues.jenkins-ci.org/browse/JENKINS-37195 |
| Description |
Original:
When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin. I tried reverting to version 4.58 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: [http://jenkins/job/jobname/125/warnings2Result/] There is a link shown on the "Types" tab to: [http://jenkins/job/jobname/125/warnings2Result/category.-52074025/] but following that link redirects back to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] I wonder if it is related to the following bug: https://issues.jenkins-ci.org/browse/JENKINS-37195 |
New:
When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin. I tried reverting to version 4.58 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: [http://jenkins/job/jobname/125/warnings2Result/] There is a link shown on the "Types" tab to: [http://jenkins/job/jobname/125/warnings2Result/category.-52074025/] but following that link redirects back to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] I wonder if it is related to the following bug: |
Andrew Barnish
added a comment - in 4.58 the filter on the "Types" tab works correctly and shows the correct result.
The version of both "warnings-plugin" and "static-analysis-core" are different so I'm not sure which plugin causes the problem.
Is there some way I could enable some extra debugging in order to get to the bottom of the issue?
Andrew Barnish
added a comment - in 4.58 the filter on the "Types" tab works correctly and shows the correct result.
The version of both "warnings-plugin" and "static-analysis-core" are different so I'm not sure which plugin causes the problem.
Is there some way I could enable some extra debugging in order to get to the bottom of the issue? Andrew Barnish
made changes -
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
Fix for JENKINS-37195 is only in analysis-core: https://github.com/jenkinsci/analysis-core-plugin/commit/1dcfdc5df42790f55a51a4592923b65916385b0b
So if you downgrade the warnings plugin (without altering analysis-core) and it works afterwards then this must be something different. Is there a reason that you did not try the latest release 4.60? Which analysis-core do you use?
In 4.59 the default category has been changed to '-'. Maybe this is a problem with old builds? Happens the problem you are describing on a build that you started with the new plugin? Which types in the tab Types do you have?
Andrew Barnish
added a comment - I was using the very latest release of both warnings (4.60) and analysis-core(1.82), but I noticed the original behavior was broken so I reverted to very old releases of both warnings and analysis-core in order to see where the problematic code change occurred.
I then moved forward through the warning releases until the regression occurred. I noticed this happened when going from warnings:4.58/analysis-core:1.80 (working) to warnings:4.59/analysis-core:1.82 (not working)
Perhaps the problem is coming from analysis-core. I don't think I can run the latest warnings plugin with analysis-core 1.80.
Andrew Barnish
added a comment - I was using the very latest release of both warnings (4.60) and analysis-core(1.82), but I noticed the original behavior was broken so I reverted to very old releases of both warnings and analysis-core in order to see where the problematic code change occurred.
I then moved forward through the warning releases until the regression occurred. I noticed this happened when going from warnings:4.58/analysis-core:1.80 (working) to warnings:4.59/analysis-core:1.82 (not working)
Perhaps the problem is coming from analysis-core. I don't think I can run the latest warnings plugin with analysis-core 1.80. Andrew Barnish
made changes -
| Summary | Original: Regression in 4.59 browsing warnings | New: Regression in warnings;4.59/analysis-core:1.82 when browsing warnings |
Andrew Barnish
made changes -
| Description |
Original:
When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin. I tried reverting to version 4.58 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: [http://jenkins/job/jobname/125/warnings2Result/] There is a link shown on the "Types" tab to: [http://jenkins/job/jobname/125/warnings2Result/category.-52074025/] but following that link redirects back to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] I wonder if it is related to the following bug: |
New:
When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin and version 1.82 of the analysis-core plugin. I tried reverting to warnings-plugin version 4.58 and analysis-core version 1.80 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: [http://jenkins/job/jobname/125/warnings2Result/] There is a link shown on the "Types" tab to: [http://jenkins/job/jobname/125/warnings2Result/category.-52074025/] but following that link redirects back to: [http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/] I wonder if it is related to the following bug: - |
The plugin redirects to the main page if the link is not valid, i.e. the category does not exist anymore. Does the 4.58 version show some results?