Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
Description
Jenkins: v1.540
JUnit-Attachments: v1.3
The files are displayed correctly, and are available on the server (I can copy them to another machine and view them). However, when clicking on the file, the light box displays the following error:
This image failed to load.
If I attempt to open the image in a new tab/window, I get a "404 Not Found" exception.
I've checked the permissions throughout the Jenkins install and everything seems to be in order (however, this an instance that doesn't use any kind of authentication; everyone is the anonymous user with full permissions).
Clicking the "attachments" link to the left yields even more interesting results:
http://junit/<namespace>/<test class name>/attachments
It appears that the link is rather incomplete, and doesn't reference the actual Jenkins instance I'm using.
If I've missed anything, or you need additional information, please let me know!
Attachments
Issue Links
- duplicates
-
JENKINS-37026 404 error when clicking a link to the attachment which includes '%' character
-
- Resolved
-
- is related to
-
JENKINS-19430 The files are not visible from either the test or the class page
-
- In Review
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue is related to JENKINS-19430 [ JENKINS-19430 ] |
Workflow | JNJira [ 152546 ] | JNJira + In-Review [ 178248 ] |
Link |
This issue duplicates |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
I just encountered very similar behavior. I determined that my problem was that my attachment file names contained percent-encoded slashes (%2F) and Jenkins was leaving them unmodified when generating links. The files existed but the links to them were wrong. My attachment file names had been deliberately percent-encoded since they had been generated from URL paths so I worked around the problem by simply using the last path segment instead of encoding slashes. I suspect that generating file names from URLs is a common need so Jenkins should deal with URL encoding in file names.