From f91c2054c19819229541a263c4e9e6ccf02bf03f Mon Sep 17 00:00:00 2001
From: Ramy Asselin <ramy.asselin@hpe.com>
Date: Fri, 20 Nov 2015 10:04:16 -0800
Subject: [PATCH] Add a link to puppet-openstackci 3rd party documentation

We now have documentation for setting up an OpenStack 3rd Party
CI Solution. Let's reference it from here.

Change-Id: I322131ee8019b3a432e115d1fe54cd6995b71186
---
 doc/source/third_party.rst | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/source/third_party.rst b/doc/source/third_party.rst
index c40c4ba9c4..ac4cade52a 100644
--- a/doc/source/third_party.rst
+++ b/doc/source/third_party.rst
@@ -355,6 +355,9 @@ The `layout.yaml <https://git.openstack.org/cgit/openstack-infra/project-config/
 used by OpenStack is a good reference for real world pipeline definitions,
 and project-pipeline-job definitions.
 
+The following documentation explains how to setup a 3rd party CI system using this approach.
+`OpenStack Third-Party CI <https://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/contrib/README.md>`_
+
 Managing Jenkins Jobs
 ---------------------
 When code is pushed to Gerrit, a series of jobs are triggered that run a series