Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate Jenkins master and slave building #84

Open
Metallion opened this issue Jan 19, 2017 · 0 comments
Open

Automate Jenkins master and slave building #84

Metallion opened this issue Jan 19, 2017 · 0 comments

Comments

@Metallion
Copy link
Contributor

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

  • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant