Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #235467
Closed
Open
Issue created Aug 11, 2020 by Nicolò Maria Mezzopera@nmezzoperaMaintainer

Publish composer packages to a project without a group

Problem to solve

You can use the GitLab Package Registry to publish and install your Composer dependencies to your Group right alongside your source code and pipelines. The problem is that there are many cases in which you want to publish packages to your project instead of your group. For example, if you have a project that doesn't belong to a group or if you are trying to publish all of your dependencies to one central project to make it easier to download and share dependencies.

Proposal

Create a new project-level endpoint for the GitLab Composer repository that will allow PHP Developers to specify a specific project in their workflows.

Further details

Currently, some of our tests create projects without a group, this will then, in turn, fail when a function is trying to use the group property of a project

This prompted an investigation where it seems not possible to use parent or a project instead of a group to configure a composer package in one's project

Edited May 12, 2021 by Tim Rizzi
Assignee
Assign to
Time tracking