Cannot pull packages from group-level package registry if a subgroup contains the same
Summary
A group's projects contribute packages to their groups's registry (e.g. Maven) which one uses to pull dependencies. If the group has a subgroup, packages published to the subgroup's projects also appear in the parent group's repo. Now, if the artifacts overlap, and one tries to pull, that doesn't work. For example I use maven repos with Gradle and jars are not getting pulled.
Steps to reproduce
- have a group and subgroup, with a project in each
- publish artifact through the project-level URL of the parent group project
- publish same artifac(s) throuhg the project-level URL of the subgroup project (the 2 projects need not have the same name)
- attempt to resolve dependencies via the parent group's group-level URL
Example Project
What is the current bug behavior?
Artifacts do not download.
What is the expected correct behavior?
What I would prefer is to be able to ignore the subgroup artifacts, i.e. have a configuration to say that subgroups don't contribute packages to their parent groups' repos.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)