Failure to install gitlab-hook about jenkins-gitlab-hook-plugin HOT 17 CLOSED

It might be related to the fact that, apparently, ruby-runtime got updated, and the gitlab hook plugin depend on 0.10 which is no longer in sync with the version used by jenkins... or so it seems.

from jenkins-gitlab-hook-plugin.

Hi! Will look into it, but you might be on the right track.

from jenkins-gitlab-hook-plugin.

Apparently, it seems that jenkins ruby-runtime is kind of... broken. Seems that every plugin relying on it no longer works. Aren't they using continuous integration for the jenkins ruby-runtime? :D We could recommand the team using a tool such as Jenkins to... kidding ;)

from jenkins-gitlab-hook-plugin.

Yes, there is CI for that: https://jenkins.ci.cloudbees.com/job/plugins/job/ruby-runtime-plugin/ (unless I am mistaking). But there seems to be no public data available. Well, don't know how to help ...

from jenkins-gitlab-hook-plugin.

I found a fix for the ruby-runtime on its github. It just hasn't been released yet. The ruby-runtime plugin was working fine until I tried to install gitlab-hook.

from jenkins-gitlab-hook-plugin.

I guess ruby-runtime was upgraded upon installing this plugin. I have a local Jenkins setup used for development, that had the latest plugin version already installed. After upgrading to latest Jenkins v1.519, I get the following on Jenkins startup:

...
Jun 23, 2013 3:01:47 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin gitlab-hook
java.io.IOException: Dependency ruby-runtime (0.10) doesn't exist
    at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479)
    at hudson.PluginManager$2$1$1.run(PluginManager.java:333)
    at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
    at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
    at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
    at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
    at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:722)

Jun 23, 2013 3:01:47 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin rvm
java.io.IOException: Dependency ruby-runtime (0.7) doesn't exist
    at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479)
    at hudson.PluginManager$2$1$1.run(PluginManager.java:333)
    at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
    at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
    at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
    at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
    at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:722)

So, as far as I can tell, until this ruby runtime issue is resolved, this will not be resolved as well.
Hope they release the fix soon!

P.S. If you don't mind, let me know if you find a way to circumvent this. Thanks!

from jenkins-gitlab-hook-plugin.

You must install ruby-runtime 0.11 manually. See here: jenkinsci/jenkins.rb#82 (comment)

However, you will still experience the error I have when trying to install the gitlab plug in. Ruby-runtime seems to be working fine when installing it manually this method, which is why I believe the error to be with the gitlab plug in.

from jenkins-gitlab-hook-plugin.

+1 --- experiencing the same issue as derekmaciel

from jenkins-gitlab-hook-plugin.

Hi guys, so I've taken a fresh Jenkins v1.518 instance for a ride, and this seems to be working OK with the ruby runtime v0.11-SNAPSHOT.

The steps to recreate:

• first run
  • run Jenkins war v1.518, e.g. java -Xmx2500M -jar jenkins.war --httpPort=3333 --prefix=/jenkins
• upgrade
  • upgrade all plugins, do not upgrade the core
  • restart to take effect
• install gitlab web hook plugin
  • ruby runtime and other plugins are automatically selected
  • restart to take effect
• verify the problem
  • after restart, I get the following error:
    SEVERE: Failed Loading plugin gitlab-hook
    java.io.IOException: Dependency ruby-runtime (0.10) doesn't exist
  • so, the error with ruby runtime and this plugin is verified on this fresh instance
• upgrade ruby runtime
  • stop Jenkins
  • delete JENKINS_HOME/plugins/ruby-runtime folder and JENKINS_HOME/plugins/ruby-runtime.jpi
  • download the ruby runtime v0.11-SNAPSHOT, as stated in jenkinsci/jenkins.rb#82
  • place it in JENKINS_HOME/plugins folder
  • start Jenkins again

After that, everything loads just fine.
Gitlab web hook plugin is operational, which can be seen from OK response to http://localhost:3333/jenkins/gitlab/ping

The above mentioned issue states that v1.519 is still having issues, so I didn't try with that one. But, as can be seen from the above steps, v1.518 works OK with the latest ruby runtime.

@derekmaciel & @NahimNasser, maybe you can follow the above steps closely and see if that might help? Also, if need be, I can package the plugin without any dependencies declared (or I can try, never done that) and attach it here for you to try. Let me know how that feels?

from jenkins-gitlab-hook-plugin.

I'll give it a whirl --- hopefully it isn't too hard to downgrade jenkins from 1.519 to 1.518.

Thanks for the quick response!

from jenkins-gitlab-hook-plugin.

@NahimNasser glad to help :-)
Anyway, please let me know how it goes.

from jenkins-gitlab-hook-plugin.

I can confirm its working on 1.518 --- with the 0.11 SNAPSHOT. Your steps worked great.

Thanks!

from jenkins-gitlab-hook-plugin.

@NahimNasser great, thanks for the update!
@derekmaciel any luck on your side?

P.S. I am keeping this issue open until it is resolved completely, e.g. working with latest ruby runtime release and available Jenkins version as well.

from jenkins-gitlab-hook-plugin.

I ended up switching from Jenkins to Gitlab CI, which, it goes without saying, integrates pretty well with Gitlab.

Also, You do not need to use the ruby-runtime 0.11 SNAPSHOT anymore. Ruby-runtime 0.11 has been released. This is the same as the SNAPSHOT, the only difference is that it does not need to be manually installed.

from jenkins-gitlab-hook-plugin.

Haven't tried it yet. Thanks for the ruby runtime release tip :-)

from jenkins-gitlab-hook-plugin.

Unfortunately with brand new Jenkins 1.520 and ruby-runtime 0.11 the problem still exists :(

from jenkins-gitlab-hook-plugin.

Closing this issue because it is not a problem with the gitlab-hook plugin, but with Jenkins itself. The previous problem with ruby-runtime 0.11 has been fixed, but due to Jenkins, cannot work on any version of Jenkins newer than v1.518.

from jenkins-gitlab-hook-plugin.