From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: ci@dpdk.org
Subject: [dpdk-ci] [PATCH] doc: add an introduction
Date: Fri, 18 Nov 2016 17:26:21 +0100 [thread overview]
Message-ID: <1479486381-24570-1-git-send-email-thomas.monjalon@6wind.com> (raw)
Signed-off-by: Thomas Monjalon <thomas.monjalon@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@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@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
next reply other threads:[~2016-11-18 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 16:26 Thomas Monjalon [this message]
2016-11-23 19:52 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479486381-24570-1-git-send-email-thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=ci@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).