Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-6721

Provide Link to VirtualBox Cloud Setup Documentation

    Details

    • Similar Issues:

      Description

      Hi,

      I have been using both VBox and Hudson quite a while. I came accross the Hudson VirtualBox Plugin. My understanding is that I can use this e.g. to create/clone/start/stop build slaves. So I'd assume that I set up a VDI that could be used as template and manage instances via the plugin. Looking at the plugin configuration section in the hudson config, I'm required to provide a URL to my VirtualBox. In the VirtualBox UI I can't find any options to remote enable my VirtualBox installation neither did I find anything in the documentation. Can you point me to some info and perhaps a link to it what the prerequisites regarding the VirtualBox installation are?

      Thanks and Best Regards,

      ajag

        Attachments

        1. VBP1.png
          VBP1.png
          18 kB
        2. VBP2.png
          VBP2.png
          26 kB
        3. VBP3.png
          VBP3.png
          45 kB

          Activity

          Hide
          mrobinet mrobinet added a comment -

          The VirtualBox URL needs to match the host given to the web service exactly. So if I start the service with -h mrobinet, then I can use http://mrobinet:18083/. If you don't use the -h option, then localhost or the IP are your only options apparently.

          As evident by the stack trace, VirtualBox 3.1 is required:
          http://download.virtualbox.org/virtualbox/3.1.8/

          Show
          mrobinet mrobinet added a comment - The VirtualBox URL needs to match the host given to the web service exactly. So if I start the service with -h mrobinet, then I can use http://mrobinet:18083/ . If you don't use the -h option, then localhost or the IP are your only options apparently. As evident by the stack trace, VirtualBox 3.1 is required: http://download.virtualbox.org/virtualbox/3.1.8/
          Hide
          ventuz Alex Klein added a comment -

          I also have a lot of problems on getting this up and running. I managed to get jenkins to start up the VM, but still haven't managed for the second part of the connect where it is actually supposed to do something. A completed guide (not just the VirtualBox part) would be very helpful...

          One problem I ran into was to get the vboxwebsrv to find the VMs when starting as a scheduled windows task. The solution to this was creating a link as described here: http://code.google.com/p/phpvirtualbox/wiki/Windows2008Service

          But all the documentation of actually getting the Jenkins Slave Agent to run inside the VM seems to be obsolete/incorrect. Still haven't managed to figure this one out.

          Show
          ventuz Alex Klein added a comment - I also have a lot of problems on getting this up and running. I managed to get jenkins to start up the VM, but still haven't managed for the second part of the connect where it is actually supposed to do something. A completed guide (not just the VirtualBox part) would be very helpful... One problem I ran into was to get the vboxwebsrv to find the VMs when starting as a scheduled windows task. The solution to this was creating a link as described here: http://code.google.com/p/phpvirtualbox/wiki/Windows2008Service But all the documentation of actually getting the Jenkins Slave Agent to run inside the VM seems to be obsolete/incorrect. Still haven't managed to figure this one out.
          Hide
          hgomez Henri Gomez added a comment - - edited

          What kind of documentation do you need ?

          VirtualBox plugin requires vboxwebdrv started and then Jenkins could use it.
          See attached screenshots

          Show
          hgomez Henri Gomez added a comment - - edited What kind of documentation do you need ? VirtualBox plugin requires vboxwebdrv started and then Jenkins could use it. See attached screenshots
          Hide
          ventuz Alex Klein added a comment -

          Hi Henri,

          well, getting it all running took me a couple of days and a lot of research. Maybe it is related to my setup because I wanted the nodes to run on a windows server and have vboxwebsrv run as a scheduled task (so it gets fired up when the server is rebooted). As far as I get it, one has to:

          • Create the node in Jenkins first (otherwise the java web start stuff later on won't work).
          • Then manually (i.e. with GUI) launch the virtual box instance on the windows server
          • In that instance go to jenkins webpage and then somewhere (forgot where) click on that link to get the java web start stuff installed within the virtual box.
          • then shutdown the virtual machine and create the scheduled task to start vboxwebsrv

          One fun part is that when vboxwebsrv is started as a scheduled task, one will not see the UI at all (because it as run under the service account). So before setting up the scheduled task, one first has to get the JAVA web start up and running. Also, non of the other start up methods seemed to be able to connect from Jenkins to virtual box correctly! I always got the node to fire up the virtual box but never to actually start the build. I believe there were also problems as the scheduled task runs under the service account and therefore cannot access the usually virtualbox configuration folder (I remember something about having to create a virtual link). Also there seems to be no proper console output if the node is running in headless mode. Speaking of which, I did not find a proper explanation what the specific start up modes do. Plus there were some refresh issues where the vboxwebsrv was correctly detected but there were no machines in the list below it to select. I first had to save it without setting anything, then go back to the page and there the machine was suddenly listed.

          All in all, it was extremely difficult and frustrating! Granted, I haven't really done much with Jenkins before, but getting everything except for the virtualbox-plugin running was pretty easy. I hope to someday find the time to re-create all the steps at home and write a step-by-step guide and post it in my personal blog. But at my company, everything is working right now so I unfortunately don't have time to de-install everything just for the purpose of documentation.

          Alex

          Show
          ventuz Alex Klein added a comment - Hi Henri, well, getting it all running took me a couple of days and a lot of research. Maybe it is related to my setup because I wanted the nodes to run on a windows server and have vboxwebsrv run as a scheduled task (so it gets fired up when the server is rebooted). As far as I get it, one has to: Create the node in Jenkins first (otherwise the java web start stuff later on won't work). Then manually (i.e. with GUI) launch the virtual box instance on the windows server In that instance go to jenkins webpage and then somewhere (forgot where) click on that link to get the java web start stuff installed within the virtual box. then shutdown the virtual machine and create the scheduled task to start vboxwebsrv One fun part is that when vboxwebsrv is started as a scheduled task, one will not see the UI at all (because it as run under the service account). So before setting up the scheduled task, one first has to get the JAVA web start up and running. Also, non of the other start up methods seemed to be able to connect from Jenkins to virtual box correctly! I always got the node to fire up the virtual box but never to actually start the build. I believe there were also problems as the scheduled task runs under the service account and therefore cannot access the usually virtualbox configuration folder (I remember something about having to create a virtual link). Also there seems to be no proper console output if the node is running in headless mode. Speaking of which, I did not find a proper explanation what the specific start up modes do. Plus there were some refresh issues where the vboxwebsrv was correctly detected but there were no machines in the list below it to select. I first had to save it without setting anything, then go back to the page and there the machine was suddenly listed. All in all, it was extremely difficult and frustrating! Granted, I haven't really done much with Jenkins before, but getting everything except for the virtualbox-plugin running was pretty easy. I hope to someday find the time to re-create all the steps at home and write a step-by-step guide and post it in my personal blog. But at my company, everything is working right now so I unfortunately don't have time to de-install everything just for the purpose of documentation. Alex
          Hide
          hgomez Henri Gomez added a comment -

          I'm also using Jenkins VirtualBox slave to run scheduled tasks and never had any issues.

          When registered, a Jenkins VB Slave could be used as any standard slave.

          Closing issue for now

          Show
          hgomez Henri Gomez added a comment - I'm also using Jenkins VirtualBox slave to run scheduled tasks and never had any issues. When registered, a Jenkins VB Slave could be used as any standard slave. Closing issue for now

            People

            • Assignee:
              hgomez Henri Gomez
              Reporter:
              ajag ajag
            • Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: