Closed Bug 703193 Opened 13 years ago Closed 13 years ago

install deps for Vagrant on Jenkins

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: fox2mike)

References

Details

In order to get Jenkins running Vagrant (bug 670471), we need the following deps installed: 1) Virtualbox (get the latest RPM from https://www.virtualbox.org/wiki/Downloads) 2) Vagrant http://vagrantup.com/ For vagrant, we really just need ruby "gem" and vagrant installed via that: # gem install vagrant We can do the rest from Jenkins.
Cool. I'll drop this into the puppet module sometime late next week.
Assignee: server-ops → shyam
(In reply to Shyam Mani [:fox2mike] from comment #1) > Cool. I'll drop this into the puppet module sometime late next week. Hey, any update on this?
(In reply to Robert Helmer [:rhelmer] from comment #0) > In order to get Jenkins running Vagrant (bug 670471), we need the following > deps installed: > > 1) Virtualbox (get the latest RPM from > https://www.virtualbox.org/wiki/Downloads) > 2) Vagrant http://vagrantup.com/ > > For vagrant, we really just need ruby "gem" and vagrant installed via that: > # gem install vagrant > > We can do the rest from Jenkins. BTW, Vagrant just hit 1.0 and they release RPMs now apparently: http://downloads.vagrantup.com/tags/v1.0.0
So sorry this took so long. Vagrant 1.0.3 is on the box. notice: /Stage[main]/Jenkins::Master/Package[vagrant]/ensure: created notice: Finished catalog run in 58.81 seconds [shyam@jenkins1.dmz.phx1 ~]$ /opt/vagrant/bin/vagrant --version Vagrant version 1.0.3 Please note the full path of the binary, please use the full path when you want to call vagrant. Let me know if you need anything else.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Also, please don't start using this for any serious stuff (if vagrant is RAM intensive) until Bug 761587 is complete.
Depends on: 761587
Installed VirtualBox too. Jun 05 06:59:32 Installed: vagrant-1.0.3-1.x86_64 Jun 05 10:19:53 Installed: 1:qt-4.6.2-20.el6.x86_64 Jun 05 10:19:54 Installed: mesa-libGLU-7.11-3.el6.x86_64 Jun 05 10:19:54 Installed: 1:qt-sqlite-4.6.2-20.el6.x86_64 Jun 05 10:19:54 Installed: xml-common-0.6.3-32.el6.noarch Jun 05 10:19:56 Installed: iso-codes-3.16-2.el6.noarch Jun 05 10:19:57 Installed: gstreamer-tools-0.10.29-1.el6.x86_64 Jun 05 10:19:58 Installed: gstreamer-0.10.29-1.el6.x86_64 Jun 05 10:19:58 Installed: lcms-libs-1.19-1.el6.x86_64 Jun 05 10:19:59 Installed: libmng-1.0.10-4.1.el6.x86_64 Jun 05 10:19:59 Installed: liboil-0.3.16-4.1.el6.x86_64 Jun 05 10:20:00 Installed: libvisual-0.4.0-9.1.el6.x86_64 Jun 05 10:20:00 Installed: cdparanoia-libs-10.2-5.1.el6.x86_64 Jun 05 10:20:01 Installed: libXv-1.0.5-1.el6.x86_64 Jun 05 10:20:03 Installed: gstreamer-plugins-base-0.10.29-1.el6.x86_64 Jun 05 10:20:06 Installed: 1:qt-x11-4.6.2-20.el6.x86_64 Jun 05 10:20:07 Installed: 1:phonon-backend-gstreamer-4.6.2-20.el6.x86_64 Jun 05 10:21:12 Installed: VirtualBox-4.1-4.1.16_78094_rhel6-1.x86_64
(In reply to Shyam Mani [:fox2mike] from comment #5) > Also, please don't start using this for any serious stuff (if vagrant is RAM > intensive) until Bug 761587 is complete. You're free to go here. 36GB of RAM on the box now.
vagrant is complaining that the virtualbox kernel extension is not loaded: https://ci.mozilla.org/job/socorro-vagrant/64/console
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I ran /etc/init.d/vboxdrv setup and now vboxmanage doesn't complain about the kernel module. Maybe jenkins has to be restarted?
I think this fixed it, haven't heard otherwise.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.