Add option to use shallow clone to save disk space when you just want to access the latest version of a repository.

[jsenko]

Cloning git repositories can cause high load on git server as well as on network. If would be nice to have an option in git plugin to perform only shallow clone. It could significantly reduce amount of transfered data.

[buildhive]

Jenkins » git-plugin #52 UNSTABLE
Looks like there's a problem with this pull request
(what's this?)

[jsenko]

I am new to Jenkins, what is the best way to disable merging and git publisher (cannot merge and push when using shallow clone), when shallow clone is being used?

[ndeloof]

reading http://blogs.gnome.org/simos/2009/04/18/git-clones-vs-shallow-git-clones/
"
The git clone man page says that you cannot push your commits if you have a shallow clone. Apparently, there is no error message when you actually push your commits, so it is a situation that might bring problems in the repository in the future.
"
so I suggest when this option is set to check GitPublisher isn't used

[ndeloof]

Should explain the feature from a user point of view, not about implementation details to use --depth.

[buildhive]

Jenkins » git-plugin #53 UNSTABLE
Looks like there's a problem with this pull request
(what's this?)

[jsenko]

That is odd. All tests pass when i build this on my computer.

[buildhive]

Jenkins » git-plugin #57 UNSTABLE
Looks like there's a problem with this pull request
(what's this?)

[vjuranek]

I can confirm, that the tests pass fine locally. It seems Buildhive has some problem with creating file, most of the tests fail on assertion which checks whether newly created file exists. Fails for other pull requests (e.g. pull #82)

[ndeloof]

merged

[scrobbleme]

Could it be that this is broken? This options doesn't seem to work for us. Our checkouts are still very very large. Using --depth=1 locally works great.

We use the latest Jenkins and versions of the plugin.