Create Task
Maniphest T11871

Accessing detailed warning reports is no longer possible
Open, Needs TriagePublic
Actions

Description

Trying open a file for curtain warning in "Warning" section leads to this.

Expected behaviour, that the file with code (which cause the warning) will appear.

P.S. Not sure, that for sysadmin tickets should be used for Jenkins problems, but on the Jenkins site I haven't found form for feedback.

Related Objects

Restricted Application added a subscriber: sysadmin. · View Herald TranscriptOct 13 2019, 1:23 PM
bcooksley edited projects, added build.kde.org; removed Sysadmin.Oct 14 2019, 9:49 AM
bcooksley added a subscriber: bcooksley.

Unfortunately this is likely the result of continued bitrot of the old Warnings module which we're using.

It looks like the filename extraction is including timestamps which are being embedded within the log files by the Jenkins Timestamper plugin - causing copying of the files to fail.
This is likely the result of changes the Jenkins developers are doing to how Jenkins stores and makes log files accessible to plugins.

We had a similar issue reported as T10505.

From my understanding the Jenkins developers essentially require people to move to the Next Generation Warnings plugin to fix issues like this. As we're going to move to Gitlab CI for duties such as this, i'm not sure it's worth investing the time porting our Pipelines from the Warnings plugin to the Warnings NG plugin.

bcooksley renamed this task from Possible Jenkins CI problem to Accessing detailed warning reports is no longer possible.Oct 14 2019, 9:50 AM
bcooksley changed the visibility from "Custom Policy" to "Public (No Login Required)".
bcooksley changed the edit policy from "Custom Policy" to "All Users".
bcooksley merged a task: Restricted Maniphest Task.Oct 30 2019, 8:45 AM
bcooksley added a subscriber: hindenburg.