Difference between revisions of "Continuous integration"

From CRIU
Jump to: navigation, search
(Travis CI)
Line 2: Line 2:
 
It's a public service, which is integrated with github and it's available for everyone.
 
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, aarch64 and execute a part of tests.
+
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.
  
It's highly recommended to enable it for your criu repo on github and check changes before sending them to the mail list.
+
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 ==
 
== Mr Jenkins ==
We use Jenkins to execute tests. It works only for the criu upstream repo and isn't available to users.
+
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.
  
 
== Links ==
 
== Links ==
 
* [https://travis-ci.org/xemul/criu Travis]
 
* [https://travis-ci.org/xemul/criu Travis]
* [https://ci.openvz.org Jenkins]
+
* [https://ci.openvz.org/view/CRIU/ Mr Jenkins]
  
 
[[Category: Development]]
 
[[Category: Development]]

Revision as of 19:39, 29 February 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.

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 [1], 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.

Links