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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to