Add "depth" option to config runner

Can runner have "depth" option which will determin the "depth" option during cloning repository. Few of my projects are realy heavy and sometimes runner just fails during cloning operations.

@AdamiecRadek Yes I see the need for this option. Currently it should ease the stress by using git fetch plan.

Added improvement label

Milestone changed to v1.0

Milestone changed to v1.1

Milestone changed to v1.2

This should be a Runner's option or maybe an option inside of .gitlab-ci.yml?

I'm not sure if it's a good idea to configure this in Runner. Then all build will be cloned to a shalow state (and what if a user want to count commits in some job?). I think it would be better if we add such option to a job configuration in .gitlab-ci.yml file.

@ayufan what do you think?

I think that this should be part of a plan that you define in .gitlab-ci.yml. The same as we have git fetch/git clone in user interface, where we should migrate it to .gitlab-ci.yml:

git:
  policy: clone
  depth: 100

OK. So this implies changes in GitLab CE/EE. Lets move this to 1.3

Milestone changed to v1.3

This is fixed.

Status changed to closed