Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #42861
Closed
Open
Issue created Feb 07, 2018 by Damian Nowak@NowakerContributor

Move "include external files in .gitlab-ci.yml" from Starter to Core

This is a community request to move the recently introduced feature #20868 (closed) from Premium to Core.

Problem to Solve

GitLab previously decided that "include" feature in gitlab-ci.yml is a feature "that [is] most relevant for large organizations" and therefore belongs to GitLab Premium. https://about.gitlab.com/stewardship/#what-features-are-ee-only

This feature however, in terms of reusing code/definitions, is important to all good implementations of CI. Furthermore, bringing this feature into broader availability will ensure the CI definitions are more compatible between CE/EE, promoting code reuse and shared templates without having to bifurcate the user base or provide CE and EE separate examples.

Solution

We will update this feature to be available for all CE users

Edited Sep 10, 2018 by Jason Yavorska
Assignee
Assign to
Time tracking