5 ms·
I recently changed our Jenkins CI infrastructure to use something like this: all jobs run in their own LXC container, using BTRFS and its snapshots/clones inste
by nicolast 14y ago
I recently changed our Jenkins CI infrastructure to use something like this: all jobs run in their own LXC container, using BTRFS and its snapshots/clones instead of AUFS. Works like a charm!
The script is available at https://github.com/Incubaid/jenkins-lxc https://github.com/Incubaid/jenkins-lxc (no docs for now, and several improvements are possible). It expects CI job scripts to be contained in the job repository, e.g. https://github.com/Incubaid/arakoon/tree/1.6/jenkins https://github.com/Incubaid/arakoon/tree/1.6/jenkins
- niall_ohiggins 14y agoThat's pretty awesome. At FrozenRidge.co, we work on our own CI server called Strider and have actually integrated Docker directly: You can read about it at: http://blog.frozenridge.co/next-generation-continuous-integration-deployment-with-dotclouds-docker-and-strider/ http://blog.frozenridge.co/next-generation-continuous-integr...
- jordanthoms 14y agoThis is great, I've been wanting to do the same thing for our jenkins setup.