As we collect more stats that now live only on the Jenkins server, our server becomes less and less disposable. We should probably have a means to send the builds and data elsewhere.
Right now, the "builds" go right into VCS as part of the Acquia repo, but we should be prepared for situation where we deploy in way that's less coupled to keeping the full site docroot in version-control like Acquia does (like capistrano deploys of the build directory or a drush-archive tarball.
As we collect more stats that now live only on the Jenkins server, our server becomes less and less disposable. We should probably have a means to send the builds and data elsewhere.
Right now, the "builds" go right into VCS as part of the Acquia repo, but we should be prepared for situation where we deploy in way that's less coupled to keeping the full site docroot in version-control like Acquia does (like capistrano deploys of the build directory or a drush-archive tarball.
Candidates plugins to investigate: