You could try using the Gitlab API to pull information about all the repos and do a little parsing. If you are an admin you can pull information about all the repos including the ID. Since these are private repos you are probably better off doing a call for "owned" repos to grab the IDs so its a smaller set of data to parse through. See more: http://doc.gitlab.com/ee/api/README.html
On Friday, February 26, 2016 at 11:48:13 AM UTC-8, Mike Purvis wrote: > > Hey all, > > I'm working on integrating a GitLab instance with some in-house release > plumbing, and I'm having a frustrating time with how archives are served > for private repos. On both Github and Bitbucket, you can use the usual > download URL with HTTP basic auth, eg: > > curl --user username -L -O > https://bitbucket.org/my_org/my_fancy_repo/get/[refname].tar.gz > > Where refname is a branch, tag, or commit. > > However, this doesn't seem to work on GitLab— in GitLab, for private > repos, I had to do this: > > > http://gitlab.example.com/api/v3/projects/[repoid]/repository/archive?sha=[refname] > > And that wouldn't be so bad, except that I couldn't find any call that > gets me the repoid from an org/repo pair. I had to make multiple calls to > the following, and then cache them all in order to maintain a local table > of repoid mappings: > > http://gitlab.example.com/api/v3/projects?per_page=100&page=[n] > > Is there some obvious thing that I'm missing here? Thanks, > > Mike > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/40be3f56-820e-4c0b-af9d-8de2927ff462%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
