You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We just updated to Jenkins 2.150.1 and the scoverage plugin stopped working for the build-specific reports.
For instance, for the run number 71, jetty returns a
HTTP ERROR 404
Problem accessing /<orgName>/job/<projectName>/71/scoverage-report. Reason:
Not Found
When viewing the report for the project, instead, that is correctly reachable at /<orgName>/job/<projectName>/scoverage/
I double checked the directories created on the master instance, and files are correctly stored, e.g. for build 71 in <jenkinsHome>/jobs/<projectName>/builds/71/scoverage-report...
Has anyone seen this and found a workaround? It looks like an update to jenkins (possibly the stapler dependency) broke this...
The text was updated successfully, but these errors were encountered:
The problem is in the ovverride of StaplerProxy in ScovergeBuildAction - since it returns null, jenkins throws a 404.
Removing the implementation fixes the problem, I'm not sure if it breaks compatibility with older versions of jenkins.
We just updated to Jenkins 2.150.1 and the scoverage plugin stopped working for the build-specific reports.
For instance, for the run number 71, jetty returns a
When viewing the report for the project, instead, that is correctly reachable at
/<orgName>/job/<projectName>/scoverage/
I double checked the directories created on the master instance, and files are correctly stored, e.g. for build 71 in
<jenkinsHome>/jobs/<projectName>/builds/71/scoverage-report
...Has anyone seen this and found a workaround? It looks like an update to jenkins (possibly the stapler dependency) broke this...
The text was updated successfully, but these errors were encountered: