Difference between revisions of "Continuous integration"

From CRIU
Jump to: navigation, search
m (typos)
(+kernel testing with Travis)
Line 7: Line 7:
  
 
Building CRIU for other platforms on x86_64 is a bit tricky. We use [[Docker build|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 [https://github.com/xemul/criu/blob/master/scripts/build/extract-deb-pkg a script] downloads it from Debian and extracts binaries.
 
Building CRIU for other platforms on x86_64 is a bit tricky. We use [[Docker build|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 [https://github.com/xemul/criu/blob/master/scripts/build/extract-deb-pkg a script] downloads it from Debian and extracts binaries.
 +
 +
=== Kernel testing ===
 +
 +
In addition to testing CRIU, we use Travis CI to test a few branches of the Linux kernel, to make sure recent changes does not break our precious software. We report found bugs to the kernel, and maintain a list of those bugs at [[Linux-next]].
 +
 +
The process consists of "git clone" the kernel, compiling it, and using kexec to reboot to a new kernel. The catch is we have to use CRIU itself to checkpoint/restore the travis control process, so that the VM is not lost to Travis upon reboot. Please see [https://avagin.github.io/travis-kexec-criu this article] for more details on the process.
 +
 +
To check the recent builds, see https://travis-ci.org/avagin/criu/branches (look for <code>linux-next-daily</code> branch).
  
 
=== Enabling for your repo ===
 
=== Enabling for your repo ===

Revision as of 22:13, 21 March 2017

This page describes various system performing automatic build verification for CRIU.

Travis CI

Travis CI is a free public service, it is well integrated with github.

To test CRIU with Travis CI, the Ubuntu 14.04 "trusty" VM is used, which has root access and an ability to run Docker containers.details. With Travis CI, we check compilation on all supported platforms (x86_64, arm, aarch64, and power), and execute all tests that can work on the kernel available. See .travis.yml, scripts/travis/ and scripts/build/ in CRIU sources for details.

Building CRIU for other platforms on x86_64 is a bit tricky. 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 a script downloads it from Debian and extracts binaries.

Kernel testing

In addition to testing CRIU, we use Travis CI to test a few branches of the Linux kernel, to make sure recent changes does not break our precious software. We report found bugs to the kernel, and maintain a list of those bugs at Linux-next.

The process consists of "git clone" the kernel, compiling it, and using kexec to reboot to a new kernel. The catch is we have to use CRIU itself to checkpoint/restore the travis control process, so that the VM is not lost to Travis upon reboot. Please see this article for more details on the process.

To check the recent builds, see https://travis-ci.org/avagin/criu/branches (look for linux-next-daily branch).

Enabling for your repo

You can test your own criu repo with Travis (and it's highly recommended to check your changes before sending patches to the mailing list).

The setup is really easy, all you need to do is:

  • Sign in to Travis CI, using your github account.
  • Wait till Travis CI synchronizes your github repositories.
  • Check your profile page and enable Travis CI for your CRIU repo.
  • Create a new branch or push a new commit to github to trigger a build.

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 [1], you will find more than dozen jobs for different configurations. We try to test all criu features.

Most part of jobs uses ZDTM Test Suite. There each test is a small program. Each job plays different scenarios with these tests:

  • dump/restore
  • dump/restore a few times
  • dump/restore with a freezer cgroup
  • dump only
  • pre-dump, dump/restore with or without page-server
  • pre-dump with duplication
  • fault injection
  • collect code coverage

In addition, we execute our tests on linux-next to be sure that nobody breaks us in a kernel space.

icon?believeme=.png icon?believeme=.png

Targets

CRIU project supports different hardware architectures and we test all of supported archs. This chapter describes targets used for CRIU testing.

  • Virtuozzo virtual machine (x86_64, Fedora?)
  • Raspberry Pi Model B Rev 2 (ARM, Raspbian)
  • Virtual machine (PPC64el)


Links