Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #18157

Closed
Open
Opened Jun 03, 2016 by Arthur@aclement

Multiple .gitlab-ci.ymls MVC

Hi,

Today the .gitlab-ci.yml is placed in the root directory and triggered at each push or merge. It's perfect to handle a single repo for a single project. I would like to create a monorepo where each project (aka a directory) has its own .gitlab-ci.yml script.

If I want to do CI against this repo, I don't see another option than trigger the root .gitlab-ci.yml and perform CI against every projects. But I don't need to do CI against project A if I update project C.

I feel it could be interesting to be able to have a .gitlab-ci.yml wherever we want, like a .gitignore file.

The behavior I would like to have : if I change a file in the project C, it would trigger the closest .gitlab-ci.yml in the upper directory hierarchy. And if I need a CI dependence between 2 projects, I would put my .gitlab-ci.yml in the directory containing these two projects. If A and C are updated at the same time and have both a .gitlab-ci.yml, both CI scripts will be triggered (2 builds).

Does it make sense ?

Edited Oct 12, 2018 by Jason Yavorska
Assignee
Assign to
Next 7-13 releases
Milestone
Next 7-13 releases
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#18157