[JENKINS-19664] Archived artifact of promoted build corrupted after download!

[timja]

We currently have one archived artifact that we created during a promotion process (think it does not matter...). The file is perfectly fine if accessed directly on the server folder or via windows share but using the url to the archived artifact creates a file where the last few hundred bytes are different and the file can not be opened anymore.
The build was created on the master not any slave!
The download for this artifact fails 100%. No other artifact behaves like that.
Happy to install any patch/create log/etc.

This is really urgent!

---

Originally reported by stleusc, imported from: Archived artifact of promoted build corrupted after download!

• assignee: gbois
• status: Resolved
• priority: Major
• resolution: Incomplete
• resolved: 2015-06-15T17:41:10+00:00
• imported: 2022/01/10

[timja]

kevinwelker:

We see this periodically too. Are you running out of the native winstone container, or are you running in another container like Tomcat? We are currently running right out of the jar using the included Winstone container.

[timja]

gbois:

What is the Content-type of the file?

[timja]

danielbeck:

Is the file really different, or rather truncated?

[timja]

danielbeck:

No comments asking for additional information in months, so resolving as Incomplete.

[timja]

lucamoscato:

Hi all, sadly I'm facing the same issue, here is my environment
jenkins 2.7.4
jdk 1.8.40 (too old?)
centos 6.8 (package updated every night).
It happens that artifacts download (both .zip and other formats) fails often when, in office, the network appears slow. For fail I intend that from browser the download process seems ends correctly ok, but the file downloaded has smaller size and, in case of .zip, can't be opened.