FYI as the maintainer of GitLab4J I have been asked in issue gitlab4j/gitlab4j-api#1280 to create a 5.8.1 release that is still on the 5.x.x stream remove the usage of PropertyNamingStrategy to be compatible with newer Jackson version and still be on Jersey 2.

Maybe this version can be useful in this project until you move to 6.x.x

FYI as the maintainer of GitLab4J I have been asked in issue gitlab4j/gitlab4j-api#1280 to create a 5.8.1 release that is still on the 5.x.x stream remove the usage of PropertyNamingStrategy to be compatible with newer Jackson version and still be on Jersey 2.

Maybe this version can be useful in this project until you move to 6.x.x

That would be great! Thanks very much for creating that release! We have multiple issue reports from users that will be happy to have that new release included in the Jenkins plugin.

I think the gitlab4j client library is not used by this plugin. Probably parts of it were copied in this code base (or used as inspiration) a very very long time ago. So my previous comment dot not apply for this repo.

• A release was create here: https://github.com/jenkinsci/gitlab-api-plugin/
• And here: https://github.com/jenkinsci/gitlab-branch-source-plugin/

@MarkEWaite :

We have multiple issue reports from users that will be happy to have that new release included in the Jenkins plugin.

Sure. As I wrote somewhere else the report in the upstream project gitlab4j/gitlab4j-api#1280 was really weak and I could not understand the affected version concerned by the issue and the relevance for the jenkins ecosystem (which ironically we are also using in my company). I am glad it now got resolved.

@krisstern thanks for merging, I should have mentioned that this should not be released until jersey-3 plugin is released.

@alecharp is trying to get that done, see jenkins-infra/repository-permissions-updater#4663

By the way, I released Jersey3-API earlier this week.

Thanks @zbynek and @alecharp! Let me cut a new release for this plugin later this weekend.