I have solved that problem by creating symbolic links between the data and the workspace, as part of the script running the job (Jenkins calls a script to run the job and create the links). The only thing copied by the Copy Artifacts plugin are a few small reports. For the HTML Reports which suffered the same problem, the HTML data is also not copied. Instead there is a web server pointing directly at the data, and the HTML report in Jenkins is simply a http link to the other web server. Moving data from the Jenkins workspace is an expensive operation, I avoid it by creating the data in its final resting place from the get go, instead of creating the data in the workspace. This final resting place of most of my data is not in Jenkins. What I store in Jenkins are references and links to the data, not the data itself.
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
