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.
Related
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.
Yesterday, I have moved my GitLab installation to another machine.
It was installed with docker-compose, and I followed the official GitLab guide to back up and restore GitLab including the 'secrets' files.
Everything works so far, except the CI/CD variables in the admin area.
I get the error 'There was an error fetching the variables.' when I navigate to this site.
Can you give me a hint in which log I can found more information about this error?
Finally I could solve the problem.
With the Doctor Rake tasks I could determine where the problem was.
Afterwards I followed the steps to reset the runner registration tokens.
Finally I deleted al the instance variables in the dbconsole, by deleting them out of the database.
Check first if this is similar to gitlab-org/gitlab issue 218913 which includes two possible root causes:
Either you have an adblocker on, which could affect that functionality
Or:
go to the project settings general -> Visibility, project features, permissions
In Pipelines (Build, test, and deploy your changes) select Only Project Members
I had the same issus after restore a backup :
My solution was to delete variables from the database :
sudo gitlab-rails dbconsole --database main
gitlabhq_production=>delete from ci_instance_variables;
gitlabhq_production=>delete from ci_variables;
then it works
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 have successfully installed older versions of gitlab and hosted them at a location like this:
mydomain/gitlab
with the new version of gitlab doing all of the config though the gitlab-ctl and via me editing the /etc/gitlab/gitlab.rb I'm not sure how to achieve this set-up.
I find lots of documentation on stackexchange for older versions of gitlab that did not use gitlab-ctl for configuration but not for the new version. Presently I have gitlab installed and running fine at:
mydomain
I want to move it to:
mydomain/gitlab
Anybody know how to do this for version 7.4.3?
Thanks :)
Serving from a relative URL root seems to be simply not implemented on Omnibus GitLab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/ed51ec97401bba955c93e61f8ef860520f745837/files/gitlab-cookbooks/gitlab/templates/default/gitlab.yml.erb#L24 (since no template variable is inserted there)
You could work around that by modifying all the required configuration files manually as explained in the comment on gitlab.yml, but that would really be a lot of manual work and those configs would get overwritten if you reconfigure, so I recommend you request the feature at: http://feedback.gitlab.com/forums/176466-general and send a pull request implementing that.
This problem was also raised at: Omnibus GitLab on IP without a domain-name and with custom relative_url_root
I ran across this same issue this week and set out to find a solution. I'm not all that familiar with RoR so I ended up creating a Bash script to automate the process instead.
Now it'd be a lot nicer if we could just automate all this through /etc/gitlab/gitlab.rb and hopefully somebody sets that up at some point (maybe someone has that I just can't find?), but in the meantime feel free to use this script as needed. Run as root on a system with a GitLab Omnibus-package installation. Tested on GitLab CE 7.9.0 with Bash 4.2.
GitLab Relative URL Setter