[dpdk-ci] [PATCH] doc: add an introduction

[Thomas Monjalon]

Signed-off-by: Thomas Monjalon <thomas.monjalon at 6wind.com>
---
 README | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)
 create mode 100644 README

diff --git a/README b/README
new file mode 100644
index 0000000..fc4cb6a
--- /dev/null
+++ b/README
@@ -0,0 +1,46 @@
+DPDK has a distributed Continuous Integration (CI) system.
+
+It is discussed in the mailing list ci at dpdk.org.
+
+
+When are run the tests?
+-----------------------
+
+The tests can be run at any time:
+- manually
+- regularly to monitor a git tree
+- after each patch submission to avoid accepting a bad patch
+
+
+Where are run the tests?
+------------------------
+
+The tests can be run anywhere:
+- in a private lab
+- in a public/reference lab
+
+There is no reference lab yet.
+
+
+How to view CI results?
+-----------------------
+
+The test of a patch is viewable in patchwork (http://dpdk.org/dev/patchwork)
+if the report has been sent from a trusted lab.
+The patchwork overview shows a counter column S/W/F for Success/Warning/Failure.
+A bad performance can be seen as a failure.
+More details are found in the detailed view of a patch.
+
+Every test reports can be seen at http://dpdk.org/ml/archives/test-report/.
+
+There is no summarized view on regular or manual tests yet.
+
+
+How to add a CI report?
+-----------------------
+
+A test report can be sent to test-report at dpdk.org.
+The sender must be trusted (whitelisted) by dpdk.org.
+
+If a report has the format of a "per-patch" test,
+it is automatically integrated in patchwork.
-- 
2.7.0