|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Thanks!
We ran into this behavior change in a fresh install. The ssd on our server died, so we re-ran the deployment scripts on the new disk. In hindsight, I should have protected myself by deploying a known version of Jenkins so we could separate upgrading Jenkins from server disaster recovery.
I should have done my due diligence, but I'd gotten lucky in the past. Fortunately we were able to recover reasonably quickly.
We use Jenkins for incremental build of a 1 GB, 1 Million LOC perl project. The incremental build is often only seconds vs ~30 minutes to run all our tests. Rsync only needs to copy the changed files. We release several times a day to several offices located in different countries, so the bandwidth savings really matter to us.