search

rtyler / vagrant-plugin

An experimental Vagrant plugin for Jenkins
https://wiki.jenkins-ci.org/display/JENKINS/Vagrant+Plugin
103 stars 45 forks source link

Facing an issue in Vagrant plugin in Jenkins #34

Open vishnudxb opened 11 years ago

vishnudxb commented 11 years ago

I install vagrant plugin in Jenkins (1.522version) and when I try to build, I am getting the below errors. Please help me to solve this issue

Started by user anonymous Building in workspace /var/lib/jenkins/jobs/testvagrant/workspace Running Vagrant with version: 1.0.2.dev FATAL: (ArgumentError) wrong number of arguments calling initialize (1 for 0) org.jruby.exceptions.RaiseException: (ArgumentError) wrong number of arguments calling initialize (1 for 0) at RUBY.initialize(/var/lib/jenkins/plugins/vagrant/WEB-INF/classes/vendor/gems/jruby/1.8/bundler/gems/vagrant-8a5b1ad0d1ef/lib/vagrant/environment.rb:77) at RUBY.setup(/var/lib/jenkins/plugins/vagrant/WEB-INF/classes/models/vagrant_wrapper.rb:63) at RUBY.setUp(/var/lib/jenkins/plugins/vagrant/WEB-INF/classes/vendor/gems/jruby/1.8/gems/jenkins-plugin-runtime-0.1.26/lib/jenkins/model/environment_proxy.rb:7)

rmarpozo commented 11 years ago

The same thing is happening to me. I don't know anything about Ruby so I'm clueless here. Any help?

ghost commented 11 years ago

I get this exact error on a freshly installed Jenkins 1.531 server with Vagrant Plugin 0.1.4.

I'm using Ubuntu Desktop x64 12.10, VirtualBox 4.1.18, Vagrant 1.0.3, and Ruby 1.9.3p194. I'll just write a shell script.

ConnorDoyle commented 11 years ago

The problem apparently has to do with the plugin's use of a forked version of a 1.x version of Vagrant, which uses a config file format that is incompatible with all of the current (2.x) examples. Not sure how much work it would take to update this plugin to be compatible with the current version of vagrant.

niksite commented 10 years ago

Does anyone know any fork of the plugin which has this issue fixed?

pbuyle commented 10 years ago

The fork of the Vagrant gem happened to fix #8. The changes needed for #8 have been merged back in https://github.com/mitchellh/vagrant/pull/803.

Later, additional changes where added to fix #14 by working around a bug of jRuby which has been fixed in https://github.com/jruby/jruby/pull/128.

So my understanding is that the fork is not needed anymore. Maybe the plugin could be reverted to use the original gem and update it to a version supporting Vagrant 2.x configuration files.

pbuyle commented 10 years ago

Actually, the code in rtyler/vagrant-plugin already uses the non-forked gem. However, jenkinsci/vagrant-plugin does not.

But installation of Vagrant as a gem is not supported anymore.

jcii commented 10 years ago

Hi All,

Is it possible to use the code from rtyler's repo as-is, or does it require some hacking?

I have no experience with jenkins or ruby, but I am tasked with using a co-worker's vagrant scripts in a CI environment. I am willing to learn and contribute back, but I'm starting from near zero. any pointers would be appreciated.