Nice, I wasn't aware of shallow or reference clones. This could be helpful.
One more note: The jenkins server is set up as a web server to the outside world. Our build machines are not exposed as servers. For security reasons no source code is allowed on the jenkins server; but it would be preferable to have this machine be in charge of running all builds. This makes sense to me from an organization standpoint, and the builds can be pretty resource-intensive so why not consolidate the build processes to run on the server. In this specific case, jenkins breaks. My server cannot both run all builds, and not clone the repository. (I work around this fine, it is just a convenience item for now, but doesn't make sense to me). On Mon, Dec 16, 2013 at 6:28 PM, teilo <teilo+goo...@teilo.net> wrote: > Sounds like you want a "shallow clone" rather than a full one. you have > thus option on the git plugin for about a year. > That way you won't have all of the history for the clone and hence less > disk space and network traffic is required. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/IwgQSKqrC6g/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
