On Wed, Apr 6, 2016 at 5:58 PM, Anthonys Lists <antli...@youngman.org.uk> wrote: > On 06/04/2016 08:21, Bjoern Michaelsen wrote: >>> >>> An alternative (which I have seen used in another project), would be to >>> let >>> >jenkins generate a source tar ball, incl. the .git directory, of the >>> > latest >>> >sane build. >> >> No, thats horrible -- it make onboarding to git even harder. >> > What quite do you mean? If the tarball includes the .git directory, then > it's effectively a clone, so they get a "known good" clone. > > That said, I'd rather not do that ... > > If we're going down that sort of route (and I had this discussion on the > firebird list) then remember that "git clone" does not work well over a > flaky internet connection, and if it bombs you typically have to restart > from scratch. And flaky connections tend to be pay connections, making it an > expensive business :-( > > Imho, IF we do something like this, we should use the git facilities to > create a shallow clone backup, that people can then use ftp or rsync or some > other interruptible protocol to download.
We have been doing that for years: http://dev-www.libreoffice.org/bundles/ _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
