Expose refspec and depth to runner

What does this MR do?

This MR exposes refspecs and depth (for git-fetch) to runners according to this specification.

GitLab-Runner uses the exposed spec and depth in order to checkout source code.

We're going to use merge request's refs (e.g. refs/merge-requests/:iid/head) in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25504.

Sample response on POST jobs/request

When the job is not associated with a merge request

{
   "id":6594,
   "token":"FNWRozxyDZ4Q1HHWyW-1",
   "allow_git_fetch":true,
   "job_info":{
      "name":"deploy",
      "stage":"test",
      "project_id":89,
      "project_name":"prospective-merge-pipelines"
   },
   "git_info":{
      "repo_url":"http://gitlab-ci-token:FNWRozxyDZ4Q1HHWyW-1@localhost:8181/root/prospective-merge-pipelines.git",
      "sha":"abb6076c965eec51b92667388be8e7ef559f9ca3",
      "before_sha":"0000000000000000000000000000000000000000",
      "ref":"patch-7",
      "ref_type":"branch",
      "refspecs":[
         "+refs/heads/*:refs/remotes/origin/*",
         "+refs/tags/*:refs/tags/*"
      ],
      "depth":0
   },
   ...
}

What are the relevant issue numbers?

Related: https://gitlab.com/gitlab-org/gitlab-ee/issues/7380

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• [-] Documentation created/updated via this MR
• [-] Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• [-] Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• [-] Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
• Security reports checked/validated by reviewer

changed milestone to %11.9

added Deliverable + 1 deleted label

assigned to @dosuken123

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has randomly picked a candidate for each review slot. Feel free to override this selection if you think someone else would be better-suited, or the chosen person is unavailable.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not (yet?) automatically notify them for you.

Category	Reviewer	Maintainer
backend	Oswaldo Ferreira (@oswaldo)	Douglas Barbosa Alexandre (@dbalexandre)

Generated by Danger

added 1 commit

• 36abee8d - fix

Compare with previous version

/cc @alessio @ayufan @darbyfrey

resolved all discussions

added 1 commit

• f5ffc41e - fix and fix

Compare with previous version

mentioned in merge request !25237 (closed)

added 1 commit

• dfa38d30 - Expose merge ref to runner

Compare with previous version

added 1 commit

• f7770354 - Support backward compatibility

Compare with previous version

added 1 commit

• ece5071b - Use ref path

Compare with previous version

changed the description

@ayufan This is a counter part of gitlab-runner!1092 (closed). Would you mind to perform an early review?

assigned to @ayufan

added 60 commits

• ece5071b...d9328cb3 - 57 commits from branch master
• 3dc4fd01 - Expose merge ref to runner
• cf669a16 - Support backward compatibility
• 82d69c59 - Use ref path

Compare with previous version

added 1 commit

• 40b809ef - Runner feature flag

Compare with previous version

I think showing full ref path is correct behavior. It indicates that the pipeline used the merge ref, not branch ref.

However, this breaks the functinoality to jump to the proper branch page.

added 1 commit

• 1dc6888e - Simplify the things

Compare with previous version

added 83 commits

• 1dc6888e...1cd080c7 - 78 commits from branch master
• 653d8947 - Expose merge ref to runner
• 19592a6a - Support backward compatibility
• d9f1d9e0 - Use ref path
• 01973c3f - Runner feature flag
• 5b9e892a - Simplify the things

Compare with previous version

added 1 commit

• 283546f9 - Support fork workflow (Public only)

Compare with previous version

added 1 commit

• 05a1511d - Expose ref spec

Compare with previous version

mentioned in issue gitlab-runner#3983 (closed)

changed title from Expose merge ref to runner to Expose ref-spec and depth to runner (and expose merge ref)

assigned to @dosuken123

added 1 commit

• 92911ad7 - Use refspec

Compare with previous version

changed title from Expose ref-spec and depth to runner (and expose merge ref) to Expose refspec and depth to runner (and expose merge ref)

added 1 commit

• 48fa9fb5 - Expose refspec and depth to runner

Compare with previous version

changed the description

added 1 commit

• 8263463e - Expose refspec and depth to runner

Compare with previous version

changed the description

I'm going to decouple merge ref related changes to https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25344

added 1 commit

• 34efa286 - Expose refspec and depth to runner

Compare with previous version

changed title from Expose refspec and depth to runner (and expose merge ref) to Expose refspec and depth to runner

added 1 commit

• d20e6f08 - Add changelog

Compare with previous version