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.
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.