Ability to specify another repo for CI script/yml

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

The following issues gitlab-ce#20826, gitlab-ce#20461 as well as the UX surrounding them and the various sub-comment requests for permissions, build-script sharing, etc. would be solved if the CI settings included a repository path.

Specifying a repo path:

  • allows build scripts to be shared between repositories
  • allows CI to be separately developed by a CI team
  • prevents breaking or evading CI tests, coverage requirements, etc.
  • allows for workflows in environments with stricter security needs

Proposal (paths are relative to repo CI root):

  • UX is a simple text box on the CI settings page
    • CI Repo URI : [      <empty text box>       ]
    • Checked to be a valid git repo URI
    • Doesn't have to be within gitlab even
    • Doesn't have to be the root (optional feature, but would be nice)
  • CI repo, regardless of it's name, is
    • cloned the same way repos are cloned
    • sumodule init/update as with a regular CI repo
    • placed in an explicitly named subdir ./.gitlab-ci
  • Path ./.gitlab-ci/gitlab.yml is copied to ./.gitlab-ci.yml before CI is run
Edited by 🤖 GitLab Bot 🤖