-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the v4 GitLab API #19
Comments
Now it's urgent. :) |
See GEBIT@fca1c4b. The corresponding java-gitlab-api is at https://github.com/GEBIT/java-gitlab-api/commits/gebit although it might be possible to use the upstream version by now. |
@cpfeiffer can you explain how to run a Docker container with API v4 support? Received the following error while building the container:
|
I just checked and unfortunately there is no new release of the original java-gitlab-api yet (c.f. timols/java-gitlab-api#289). I did and still do not intend to release our own fork on maven-central, since it was just meant as a temporary measure until upstream releases a new version. At that point, I would remove our own fork and use upstream directly. The easiest way would be to use jitpack and replace the dependency in pom.xml like this:
New:
Then it should work. I personally never tried the Dockerfile though. |
Actually 4.0.0 seems to have been released a while ago, and we are currently using it with the latest gebit version of glghproxy. Is there anything wrong with that version? |
timols/java-gitlab-api#245 was merged after 4.0 was released. But that's not really a problem, just a minor performance difference. |
Thank you @cpfeiffer, i've updated the pom.xml (changed dependency and added jitpack) but now i'm receiving the following error:
|
I'm happy to accept merge requests on this anytime. |
@Nick-Jansen Thanks, this is fixed now. |
@cpfeiffer I am facing the same issue. If I try updating the version from |
There's a new release of the original java-gitlab-api (4.1.0), but from a first check it look like there's some small API changes. I don't have the time right now to fix this, but it shouldn't be very hard. |
I've released 0.5.0 based on java-gitlab-api 4.1.0. |
@cpfeiffer thank you. |
That would be surprising, see here: https://github.com/timols/java-gitlab-api/blob/4.1.0/src/main/java/org/gitlab/api/GitlabAPI.java#L39 Also my nginx/gitlab_access.log indicates the usage of /api/v4/. |
ok, I tried again and I could now create the connection to GitLab but JIRA can't fetch the list of repositories:
|
@muhlba91 |
@dka23 this is a great project, thanks for this ❤️
GitLab now has a v4 of its API: https://docs.gitlab.com/ce/api/v3_to_v4.html
As of timols/java-gitlab-api#207, it looks like the API client you're using supports this API. This isn't urgent right now, but it would be good to switch at some point 🙂
The text was updated successfully, but these errors were encountered: