Difference between revisions of "Continuous integration"

From CRIU
Jump to: navigation, search
(Travis CI)
m (typo fix)
Line 9: Line 9:
  
 
== Mr Jenkins ==
 
== Mr Jenkins ==
We use Jenkins to execute tests. It works only for the criu upstream repo and isn't available to users yet. If you visit [https://ci.openvz.org/view/CRIU/], you will find more than dozen jobs for different configurations. We try to test all criu features. In addition, we execute out tests on linux-next to be sure that nobody breaks us in a kernel space.
+
We use Jenkins to execute tests. It works only for the criu upstream repo and isn't available to users yet. If you visit [https://ci.openvz.org/view/CRIU/], you will find more than dozen jobs for different configurations. We try to test all criu features. In addition, we execute our tests on linux-next to be sure that nobody breaks us in a kernel space.
  
 
== Links ==
 
== Links ==

Revision as of 17:32, 1 March 2016

Travis CI

It's a public service, which is integrated with github and it's available for everyone.

We use "The Trusty beta Build Environment", where we have a full root access and an ability to execute docker containers. We use Travis to check compilation on x86_64, arm and aarch64. In addition, we execute all tests which have to work on the Trusty kernel.

The most interesting part of this work is how to build CRIU for other platforms on x86_64. We use Docker to get a container for a target platform and qemu-static to run this container. qemu-static doesn't exist in all distributions, so we download it from Debian and extract binaries from it [1].

It's highly recommended to enable Travis for your criu repo on github and check changes before sending them to the mail list.

Mr Jenkins

We use Jenkins to execute tests. It works only for the criu upstream repo and isn't available to users yet. If you visit [2], you will find more than dozen jobs for different configurations. We try to test all criu features. In addition, we execute our tests on linux-next to be sure that nobody breaks us in a kernel space.

Links