You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Jenkins master and the slave on which we run unit tests and rpmbuild have been built manually. If they break, we're fucked. We should write scripts to build and rebuild them.
Currently both machines are VirtualBox VMs. I don't think this is ideal because it is not possible to run KVM inside of VirtualBox. This is something we will likely want to do for OpenVDC in the future but as long as VirtualBox is running on bare-metal, it is not possible to run KVM on the same machine. The main advantage of VirtualBox is that it will run on any OS but I don't think that is relevant for Jenkins. We are not likely to run it locally.
I would suggest to rebuild them as either KVM machines or docker containers.
Solution
Have a meeting (or chat) to decide what hypervisor we should run Jenkins on.
Write the scripts to automate building these. For KVM I'd suggest something similar to multibox and for Docker a Dockerfile (of course).
We should probably also store the jenkins configuration on a private github repository that we periodically update so we can pull from there in the build script.
The text was updated successfully, but these errors were encountered:
Problem
Currently the Jenkins master and the slave on which we run unit tests and rpmbuild have been built manually. If they break, we're fucked. We should write scripts to build and rebuild them.
Currently both machines are VirtualBox VMs. I don't think this is ideal because it is not possible to run KVM inside of VirtualBox. This is something we will likely want to do for OpenVDC in the future but as long as VirtualBox is running on bare-metal, it is not possible to run KVM on the same machine. The main advantage of VirtualBox is that it will run on any OS but I don't think that is relevant for Jenkins. We are not likely to run it locally.
I would suggest to rebuild them as either KVM machines or docker containers.
Solution
The text was updated successfully, but these errors were encountered: