Continuous integration - Revision history

Avagin at 08:03, 16 February 2018

2018-02-16T08:03:19Z

2018-02-13T21:56:09Z

Kernel testing

2017-04-28T04:17:32Z

2017-04-28T04:17:09Z

Patchwork: +link

2017-03-27T20:34:40Z

a typo

2017-03-22T00:25:35Z

Patchwork: rm mailing list link

2017-03-22T00:24:38Z

2017-03-22T00:24:06Z

2017-03-22T00:19:06Z

Patchwork: fix heading level, expand description

2017-03-21T22:35:49Z

@@ Line 34: / Line 34: @@
 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/linux/ .
+To check the recent builds, see https://travis-ci.org/avagin/linux/builds .
 === Enable Travis CI for your repo ===

@@ Line 34: / Line 34: @@
 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).
+To check the recent builds, see https://travis-ci.org/avagin/linux/ .
 === Enable Travis CI for your repo ===

@@ Line 82: / Line 82: @@
 * [[ZDTM test suite]]
 * [[Linux-next]]
 == External links ==

← Older revision		Revision as of 04:17, 28 April 2017
Line 19:		Line 19:

	In CRIU it is used to grab patch series from the CRIU mailing list, create a new git branch which is tested by Travis, and report success/failure back to the mailing list.		In CRIU it is used to grab patch series from the CRIU mailing list, create a new git branch which is tested by Travis, and report success/failure back to the mailing list.
		+
		+	'''For more info, see [[Patchwork]]'''.

	=== Non-x86 architectures ===		=== Non-x86 architectures ===

@@ Line 11: / Line 11: @@
 * check compilation on Alpine Linux (x86_64 only)
 * execute all tests that can work on the kernel available ([[ZDTM test suite]] and some other tests).
-* collect code coverage and upload it to [https://coveralls.io/github/xemul/criu Coverall]
+* collect code coverage and upload it to [https://coveralls.io/github/xemul/criu Coveralls]
 For implementation details, see <code>.travis.yml</code>, <code>scripts/travis/</code> and <code>scripts/build/</code> in CRIU sources for details.

@@ Line 18: / Line 18: @@
 [https://patchwork.criu.org/project/criu Patchwork] is a web patch tracking system for projects using a mailing list for contributions and reviews.
-In CRIU it is used to grab patch series from the [[mailing list]], create a new git branch which is tested by Travis, and report success/failure back to the mailing list.
+In CRIU it is used to grab patch series from the CRIU mailing list, create a new git branch which is tested by Travis, and report success/failure back to the mailing list.
 === Non-x86 architectures ===

@@ Line 77: / Line 77: @@
 == See also ==
-* [[How to send patches]]
+* [[How to submit patches]]
 * [[ZDTM test suite]]
 * [[Linux-next]]