I rencently upgraded my gitlab-ce to 13.12 because i saw this feature, and realised I don't have Packages & Registries in my settings.
Is there anything i miss here ?
Be aware that this is a GROUP LEVEL setting and not a project level setting.
To change this select the Group containing the project, where you want this feature. Within the settings for the group, you will find a section called Packages and Registries.
Related
My question is very simple. I found a lot of examples and tutorials on how to use the registry in GitLab.I need this for my angular libraries, but why I can't show the Registry button. Gitlab is hosted on my server.[
I assume what you need is npm registry, that you need version at least 11.7
in the project, go to settings -> general -> visibility, project features, permissions
under 'Repository', you will see the last item 'package', enable it and save change, you will see the packages registry then
if you want to use docker container registry, you may try edit the gitlab.rb and find gitlab_rails['registry_enabled'], set it to 'true' and reconfigure. Hope this helps.
I am trying to publish a package to gitlab pypi registry. What is the repository url we need to use to publish to a group package registry?.
I tried using this https://gitlab.example.com/api/v4/groups/id/packages/pypi
but it is throwing 404 now found.
The api https://gitlab.example.com/api/v4/groups/id/packages/ returns a empty array for me.
But when I manually take the registry from the UI pypy, npm etc are present.
Publishing to individual project repositories is working fine.
https://gitlab.example.com/api/v4/projects/id/packages/pypi
I run into the same problem.
As far as I understand, groups don't have their own registries. If you go in your group settings, you won't see the option to activate it.
Groups are only placeholders to organize projects, they don't hold any data.
What you see in the UI when clicking on the group registry is the aggregation of all the registries of the projects inside that group.
This is only a search UI, not a registry per se.
Bottom-line is that you have to publish your artefacts to a specific project.
Note that you can have a dedicated project to hold only your registry, and have all your code repositories publish in the same registry.
I am trying to use gitlab mirror repository functionality of gitlab but under Mirror direction, it only shows push option to me, dropdown menu is greyed out. I can not select pull option.
Gitlab version : Gitlab EE 12.8.5-ee Ultimate.
My user account is maintainer.
Am I missing something?
Thanks in advance.
After searching a bit on this got the answer why the pull option was disabled:
Answer :
It appears that the ability to disable mirrors was introduced in GitLab 10.3
So after upgrading gitlab, Admin has to specifically Enable mirror configuration
Enable single checkbox in Admin -> Application Settings -> Repository:
If this checkbox is unchecked, even project owners can't administer mirrors, though the text only says push mirrors.
Reference : https://gitlab.com/gitlab-org/gitlab/issues/13769
From Repository Mirroring
check if the repo was not already configured for pushing (and can no longer be modified for pulling)
some prerequisite might prevent any pulling option.
I'm working in a company using one Mantis bug tracker hosting several projects.
The project I am working on needs specific statuses and I don't want these to be seeable in other project pages.
I see in the doc how to add a status but they seem to be global and not project specific.
The only way I see how to do it is to add global states and remove them from all other projects' workflows.
Do you know if (and how) it is possible to add project specific workflows ?
Thanks :)
Almost everything you can set in config_inc.php can also be defined in the database, either globally (all projects) or for specific projects.
You can do this using the Manage | Manage Configuration | Configuration Report page; at the bottom of the page, a section lets you define custom config options. Define the enums as appropriate and described in the documentation (you should still define the translations globally, including all valid values in the string)
To set a custom workflow, just set your current project as appropriate and use the Manage | Manage Configuration | Workflow Transitions to define it.
I just installed GitLab 6.0.0 and I am now trying to create a group in order to share a common repository with other users. So I created the group and then added the users I want as owners of this group.
The problem is that the group members don't seem to be able to choose the corresponding namespace when they creating a new project.
Is this a bug? or am I missing something?
Any help is welcomed, thanks.
Best regards,
Michael Pinheiro
It looks like this bug: issue 4900
workarounds:
I should also mention that if User B now creates a Group Y, he is now able to create projects for Group X and Y. (which is a simple workaround)
The other work-around is to have the user create the project in their personal namespace first, then when the repo is created go to settings -> dangerous settings -> change namespace option.
A patch should be proposed soon to fix that bug, which seems to be related to app/models/user.rb (lines 293-295 and lines 331-333)