summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMichael Santana <msantana@redhat.com>2019-03-25 11:32:08 -0400
committerThomas Monjalon <thomas@monjalon.net>2019-03-26 22:31:40 +0100
commit99889bd85228bdf6fa28e160308444d82dca68cd (patch)
treed313e69fefcb6f86de34bd4bc342aa997a8d6774 /doc
parent866bc6742c5478023219d5f795d44a0254a3ee88 (diff)
downloaddpdk-next-eventdev-99889bd85228bdf6fa28e160308444d82dca68cd.zip
dpdk-next-eventdev-99889bd85228bdf6fa28e160308444d82dca68cd.tar.gz
dpdk-next-eventdev-99889bd85228bdf6fa28e160308444d82dca68cd.tar.xz
ci: introduce Travis builds for GitHub repositories
GitHub is a service used by developers to store repositories. GitHub provides service integrations that allow 3rd party services to access developer repositories and perform actions. One of these services is Travis-CI, a simple continuous integration platform. This series introduces the ability for any github mirrors of the DPDK project, including developer mirrors, to kick off builds under the travis CI infrastructure. For now, this just means compilation - no other kinds of automated run exists yet. In the future, this can be expanded to execute and report results for any test-suites that might exist. This is a simple initial implementation of a travis build for the DPDK project. It doesn't require any changes from individual developers to enable, but will allow those developers who opt-in to GitHub and the travis service to get automatic builds for every push they make. The files added under .ci/ exist so that in the future, other CI support platforms (such as cirrus, appveyor, etc.) could have a common place to put their requisite scripts without polluting the main tree. Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Michael Santana <msantana@redhat.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
Diffstat (limited to 'doc')
-rw-r--r--doc/guides/contributing/patches.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index 90927a5..d8404e6 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -32,6 +32,10 @@ The mailing list for DPDK development is `dev@dpdk.org <http://mails.dpdk.org/ar
Contributors will need to `register for the mailing list <http://mails.dpdk.org/listinfo/dev>`_ in order to submit patches.
It is also worth registering for the DPDK `Patchwork <http://patches.dpdk.org/project/dpdk/list/>`_
+If you are using the GitHub service, you can link your repository to
+the ``travis-ci.org`` build service. When you push patches to your GitHub
+repository, the travis service will automatically build your changes.
+
The development process requires some familiarity with the ``git`` version control system.
Refer to the `Pro Git Book <http://www.git-scm.com/book/>`_ for further information.