Gitlab-plugin: Jenkins update center not showing newer releases

[LucasSymons]

Issue

The Jenkins update centre still shows version 1.5.13 as the current build of the plugin.
My team is hesitant to build from the source as they are not sure if it will break future update integration or cause other issues, but we would really enjoy some of the latest fixes.
Would it be possible to have 1.5.17 pushed to the Jenkins update centre?

Context

• Jenkins Gitlab plugin version: 1.5.13
• Github version: 1.5.17
• Jenkins version: 2.218
• Job type: Publish???

[markyjackson-taulia]

@Akin2Silver yeah, there are some problems with the Jenkins infra.. As soon as that gets sorted out, I will push this version to the update center

[LucasSymons]

@Akin2Silver yeah, there are some problems with the Jenkins infra.. As soon as that gets sorted out, I will push this version to the update center

Thanks very much! I really appreciate it.

[jblamotte]

Any news about that ?

[mat1e]

@markyjackson-taulia, do you have any news ?

[markyjackson-taulia]

Hi all,
I will hopefully have this out this weekend to the update center

[reinholdfuereder]

(See #1018)

[artbycrunk]

any update on this? is it an issue on the jenkins update center end?

[cr-lgl]

Not solved yet?

[LucasSymons]

Is there anything I can do to help this one along?

[markyjackson-taulia]

We had a few infra issues and have been sick. I will get back on this this week

[LucasSymons]

Just wanted to follow up on this one, see if there was any help i could provide even if you just need me to dig through some docs or some thing?

[reinholdfuereder]

@markyjackson-taulia *Begging*

(1.5.17 was released on 09 Feb 2020: https://github.com/jenkinsci/gitlab-plugin/releases/tag/gitlab-plugin-1.5.17)

Maybe as already mentioned in #1018 a very able Jenkins core dev/expert like @oleg-nenashev can help? (Extremely naive guess: May that be because of the version being a "snapshot" only in the "pom.xml"? Cf. <version>1.5.17-SNAPSHOT</version>)

[markyjackson-taulia]

Will take a look this weekend

[jluk-scms]

@markyjackson-taulia I'm willing to help you with this, but I need some hints about what needs to be done :)

[markyjackson-taulia]

Thank you kindly. The issue is with deploying to artifactory. I will work on that this weekend

[jluk-scms]

Hi @markyjackson-taulia , how it's going?

[jluk-scms]

@omehegan Maybe you can help here. I found your username in the jenkins-infra repo: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-gitlab-plugin.yml

I'm still willing to help if any work is needed to be done to push this forward, just need pointers where to look. Cheers.

[markyjackson-taulia]

@omehegan Maybe you can help here. I found your username in the jenkins-infra repo: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-gitlab-plugin.yml

I'm still willing to help if any work is needed to be done to push this forward, just need pointers where to look. Cheers.

The problem is with how the HPI artifact is pushed to artifactory. I am working to fix this. Just need a little more time.
Appreciate everyone and sorry this has taken so long.

[kanata2]

Any news about this problem? (Sorry to rush you...)

[Boulet-]

Can we help you on this?

[frank-aurich]

Can we please get some update on this issue?
The last version was released in Feburary, 7 months ago, but unless you build it yourself you cannot use it because the Jenkins plugin system doesn't know about the latest version.

Can we assist in any way in fixing this issue?

[sandeepnagori87]

@markyjackson-taulia Would appreciate if this can be done ASAP.thanks

[sandeepnagori87]

@markyjackson-taulia Would appreciate if this can be done ASAP.thanks

Seems @markyjackson-taulia step back from open source projects. @MarkEWaite Could you please help to have 1.5.17 gitlab plugin in jenkins update center. Thanks a lot.

[MarkEWaite]

Thanks for asking, @sandeepnagori87. Unfortunately, I'm not available to assist with this plugin. I fear that my assistance would cause more harm than help.

I'm not a frequent user of GitLab and cannot commit the time and energy necessary to become experienced enough to be a viable maintainer of the GitLab plugin.

The Jenkins project encourages those interested in a plugin to volunteer to maintain that plugin by "adopting the plugin". If you're a frequent user of the GitLab plugin and are interested in assisting with its development, please use the "adopt a plugin" process to ask to be allowed to help.

If you need the 1.5.17 release sooner than "adopt a plugin" allows, you could checkout the 1.5.17 tag from git, build the plugin from source code, and use that plugin locally on your instance. If you detect issues with that version, you could propose fixes for those issues as pull requests to the plugin.

In my case, I needed a version of the GitLab plugin that did not bundle an outdated version of JGit. I created a branch from 1.5.13 with a commit that removed JGit from the packaging, then built that version and placed it in my Docker image. If your needs are the same as mine, you're welcome to install that plugin version in your environment.

In case someone needs a locally built version of the 1.5.17 GitLab plugin and isn't able to create it themselves, I've uploaded a version that I built locally with JDK 8u282. The version I built locally does not meet my needs because it still includes JGit 3.5.2. I don't know if it will meet the needs of others.

gitlab-plugin-1.5.17-SNAPSHOT.zip

[sandeepnagori87]

Thanks for asking, @sandeepnagori87. Unfortunately, I'm not available to assist with this plugin. I fear that my assistance would cause more harm than help.

I'm not a frequent user of GitLab and cannot commit the time and energy necessary to become experienced enough to be a viable maintainer of the GitLab plugin.

The Jenkins project encourages those interested in a plugin to volunteer to maintain that plugin by "adopting the plugin". If you're a frequent user of the GitLab plugin and are interested in assisting with its development, please use the "adopt a plugin" process to ask to be allowed to help.

If you need the 1.5.17 release sooner than "adopt a plugin" allows, you could checkout the 1.5.17 tag from git, build the plugin from source code, and use that plugin locally on your instance. If you detect issues with that version, you could propose fixes for those issues as pull requests to the plugin.

In my case, I needed a version of the GitLab plugin that did not bundle an outdated version of JGit. I created a branch from 1.5.13 with a commit that removed JGit from the packaging, then built that version and placed it in my Docker image. If your needs are the same as mine, you're welcome to install that plugin version in your environment.

In case someone needs a locally built version of the 1.5.17 GitLab plugin and isn't able to create it themselves, I've uploaded a version that I built locally with JDK 8u282. The version I built locally does not meet my needs because it still includes JGit 3.5.2. I don't know if it will meet the needs of others.

gitlab-plugin-1.5.17-SNAPSHOT.zip

Thanks Mark.I will have a look on "adopt a plugin" .Since this is was little urgent I try to use your private 1.5.17 gitlab plugin unfortunately I still see same issues [Jenkins triggers for non code changes]which got fixed in https://github.com/jenkinsci/gitlab-plugin/pull/998.

@ababushk Can you try to use this plug-in and see if it solves issues at your end.

[sandeepnagori87]

Thanks for asking, @sandeepnagori87. Unfortunately, I'm not available to assist with this plugin. I fear that my assistance would cause more harm than help.
I'm not a frequent user of GitLab and cannot commit the time and energy necessary to become experienced enough to be a viable maintainer of the GitLab plugin.
The Jenkins project encourages those interested in a plugin to volunteer to maintain that plugin by "adopting the plugin". If you're a frequent user of the GitLab plugin and are interested in assisting with its development, please use the "adopt a plugin" process to ask to be allowed to help.
If you need the 1.5.17 release sooner than "adopt a plugin" allows, you could checkout the 1.5.17 tag from git, build the plugin from source code, and use that plugin locally on your instance. If you detect issues with that version, you could propose fixes for those issues as pull requests to the plugin.
In my case, I needed a version of the GitLab plugin that did not bundle an outdated version of JGit. I created a branch from 1.5.13 with a commit that removed JGit from the packaging, then built that version and placed it in my Docker image. If your needs are the same as mine, you're welcome to install that plugin version in your environment.
In case someone needs a locally built version of the 1.5.17 GitLab plugin and isn't able to create it themselves, I've uploaded a version that I built locally with JDK 8u282. The version I built locally does not meet my needs because it still includes JGit 3.5.2. I don't know if it will meet the needs of others.
gitlab-plugin-1.5.17-SNAPSHOT.zip

Thanks Mark.I will have a look on "adopt a plugin" .Since this is was little urgent I try to use your private 1.5.17 gitlab plugin unfortunately I still see same issues [Jenkins triggers for non code changes]which got fixed in #998.

@ababushk Can you try to use this plug-in and see if it solves issues at your end.

Sorry my mistake. I did not check "Build only if new commits were pushed to Merge Request" option in jenkins UI before doing test.

Looks like it is working fine. Thanks alot. If someone can push it in jenkins update center then it would be great.:)

[MarkEWaite]

Looks like it is working fine. Thanks alot. If someone can push it in jenkins update center then it would be great.:)

That's what maintainers do. If you'd like to become a maintainer, "adopt a plugin" is the path to become a maintainer.

[sandeepnagori87]

Looks like it is working fine. Thanks alot. If someone can push it in jenkins update center then it would be great.:)

That's what maintainers do. If you'd like to become a maintainer, "adopt a plugin" is the path to become a maintainer.

Sure. I will have a look.
BTW I was trying to build plugin locally but got some connection issues e.g. . Appreciate your help

Failed tests:
com.dabsquared.gitlabjenkins.connection.GitLabConnectionConfigTest.doCheckConnection_proxy(com.dabsquared.gitlabjenkins.connection.GitLabConnectionConfigTest)
Run 1: GitLabConnectionConfigTest.doCheckConnection_proxy:102
Expected: a string containing "Connection refused"
but: was "Client error: HTTP 404 Not Found"

[MarkEWaite]

I don't know the source code of the plugin. It may be assuming there is a GitLab server at a specific URL or it may be failing to create a mock GitLab server.

[Stikus]

Plugin is looking for adoption: #1098 - FYI

[omehegan]

If someone can fix the broken master branch build, I can at least get a release out. Any volunteers?

[MarkEWaite]

@omehegan I've submitted ##1106 that fixes compilation on the master branch. I don't know if it passes tests. Too late in my day to check that. I tried to find the minimum subset of changes that would fix compilation before end of day.

[bulanovk]

@omehegan Master brach already fixed in this MR https://github.com/jenkinsci/gitlab-plugin/pull/1103

[omehegan]

1.5.19 was finally released successfully yesterday! Thanks to everyone who helped resolve issues to get this done.