[
https://issues.jenkins-ci.org/browse/JENKINS-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161275#comment-161275
]
Richard Taylor commented on JENKINS-13352:
------------------------------------------
Searching jenkins.err.log for show no errors for the a build where the artifact
link is broken.
05-Apr-2012 08:35:38 hudson.model.Run run
INFO: evo11-PKG #126 branches/evo11dx11 main build action completed: SUCCESS
> Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory
> could not be found" when trying to download artifacts.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-13352
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13352
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Server Win2k8 - Jenkins ver. 1.455 and 1.457 (server has
> zero executors)
> Slave Win2k8 R2 - Slave ver. 2.12 (21 slaves)
> WebBrowser - Firefox 11.0 and Chrome 18.0.1025.142 m
> The build which is failing to archive artifacts is tied to a single slave.
> Reporter: Richard Taylor
>
> We have started getting bad links to artifacts from some runs of our package
> build job.
> * The build completes with out error.
> * The artifacts are sucesfully copied back to the server.
> * The artifacts can be copied and verified ok using SMB drive share.
> * Approx 50% of the builds now give the following error when attempting to
> down load artifcts.
> This web page has not been found
> Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found.
> From the client side there is no way to tell if a link will work or not.
> Working link
> http://nw01-evotools:8080/job/evo11-PKG/123/artifact/evo11-0.0.123.12542.exe
> Failing link
> http://nw01-evotools:8080/job/evo11-PKG/124/artifact/evo11-0.0.124.12606.exe
> Our QA dept are no longer able to download packages for testing and this is
> major issue for our workflow.
> Any suggestions about temp fixes or work arounds appreciated.
> Thanks
> Richard.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
