Glab cli tools requirements

How to Use GitLab
,
1

Problem to solve

Glab-cli use with Gitlab GitLab Enterprise Edition v16.11.7-ee:

In my company we are using a self-host giltab v16.11.7-ee, I was using release cli tools to create project releases without problems. But once the release-cli is deprecated and the suggestion of gitlab is to use glab-ci tools. I start to implement this tool.
Happens that this tool is not to be compatible with the API version of GitLab v16.11.7-ee.

When the command is run the creation of release fails with the not found project.

The glab cli are using the api endpoint with the project path to create the release p.e: https:
//myserver.com/api/v4/projects/mygroup7myproject/release but this endpoint returns a 404 error. I tried with curl and the same error was given.

But the endpoint https://myserver.com/api/v4/projects/<project_id>/release works fine.

So may questions are:

  • Is it a required API version for glab cli? Is this in the documentation?
  • Do you have this problem also? Any solution?

Versions

Please select whether options apply, and add the version information.

Versions

  • GitLab Enterprise Edition v16.11.7-ee
1 Like
2

Same with version v17.2.2-ee. The strange thing is that, using the same pipeline, in one project I can successfully run the glab release commands, while in another project, on the same server, I have the same problem above.

3

Hi @giovanni.burbi thank you for your feedback.

Can you try to request the release for both projects by API on your server? And checks which endpoints working for both projects.

4

The docs link to this issue, which discusses the release-cli migration in this thread: Proposal: Deprecate release-cli in favor of glab (#7450) · Issues · GitLab.org / cli · GitLab I linked this forum topic here, and would recommend adding feedback and ideas into the issue, where engineers and contributors are active.

1 Like
5

Thank you @dnsmichi

1 Like