Using GitLab, projects are missing from the API list

gitlab

I use the GitLab API to fetch a list of the projects I have access to (URL /api/v3/projects/all?private_token=xxx), but there are 6-7 projects that are not included in the list for some reason.

EDIT: My user is an administrator, and I want to list all projects like the /projects/all URL indicates.

I have access to the projects just fine using git itself and the GitLab web interface. Any suggestions why the projects wouldn't be shown in the list from the API?

All the projects missing are newer than the others. I have tried refreshing my API token; no change.

Versions:

GitLab        6.4.3
GitLab Shell  1.8.0
GitLab API    v3
Ruby          2.0.0p353
Rails         4.0.2

Best Answer

I just tested this and it looks like the GitLab API response is using pagination. According to the documentation (http://api.gitlab.org), the default number of results per page is set to 20 and the starting page is 1.

To adjust the maximum results per page, you need to use the per_page variable in the HTTP request line. You can change the page number by using page as well, if you have more repositories than the maximum value of per_page. You can specify a maximum per_page value of 100.

For example, you request may look like:

https://git.example.com/api/v3/projects/all?page=1&per_page=100&private_token=abc123

The page and per_page variables are not required as they have default values, so you do not need to include either if you don't want to.

Hopefully this solves your problem.

Related Solutions

Nginx – gitlab installation: using localhost

Verify that /home/git/gitlab/tmp/sockets/gitlab.socket actually exists and have permissions/ownership in-line with the setup instructions. Also, try running these two commands inside of the /home/git/gitlab directory:

sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

All items should be green. If not, you'll have to troubleshoot more specifically from there.

Here's a Github issue related to what you are seeing. Hopefully the above steps fix it or at least get you further!

Your database is not setup properly OR your credentials for accessing it are wrong. Please make sure you followed https://github.com/gitlabhq/gitlabhq/blob/5-0-stable/doc/install/databases.md and did one of the following as instructed for your DB platform.

Mysql

sudo -u git cp config/database.yml.mysql config/database.yml

PostgreSQL

sudo -u git cp config/database.yml.postgresql config/database.yml

What “access rights” could be blocking access to a gitlab repository

I'm pretty sure you have a configuration problem between SSH and the system because of this SSH debug message :

client_input_channel_req: channel 0 rtype eow@openssh.com reply 0

You receive this message immediately after a successful authentication and no message from bash which means no program was launched after login.

Watch in your passwd file if you have the right settings for the gitlab user :

gitlab:x:1011:1012:GitLab,,,:/path/to/gitlab:/bin/bash

Verify bash has no weird thing in configurations files such as

bash.bashrc
.profile
.bashrc

Then go up to the uper level : Gitlab-shell Verify the /path/to/gitlab/.ssh/authorized_keys has the configuration below :

command="/path/to/gitlab/gitlab-shell/bin/gitlab-shell key-2",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa A...

with /path/to/gitlab/gitlab-shell/bin/gitlab-shell owned by the gitlab user and executable.

You can be sure gitlab-shell is fully operational by launching the command :

# /path/to/gitlab-shell/bin/gitlab-shell
Welcome to GitLab, Anonymous!

If the remote login is actually working and properly connected to the gitlab-shell, you should get the same welcome message (but matched to the user whose ssh key you used to login) before it dumps you out if you try to login remotely.

$ ssh gitlab@server
Welcome to GitLab, <your user's full name>!
Connection to <server> closed.

No message here probably indicates ssh isn't connecting you to gitlab at all.

Finally, checkout your gitlab-shell configuration (config.yml) and verify if :

http_settings:
    # trailing slash is important
    gitlab_url: "https://remote_server/"
    ca_file: /path/to/webserver/certificate.crt

and eventually :

    self_signed_cert: false