opendev/system-config
Code Issues Proposed changes

Correct stackforge .gitreview docs.

Browse Source 
The manage projects script adds a gitreview file for you if the new
projects does not have an upstream. Make it clear that you only need to
add the .gitreview file on projects with an existing upstream.

Also, fix a tiny typo in the Jenkins document.

Change-Id: I74c07d9cd952509bd9ddc883a833cb3e22b13b38
Reviewed-on: https://review.openstack.org/18570
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
This commit is contained in:
Clark Boylan 2012-12-21 15:53:34 -08:00 committed by Jenkins
parent e13eea405e
commit c74ac6ab8b
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/jenkins.rst
View File

@ -15,7 +15,7 @@ all code should be reviewed and tested before being merged in to trunk,
and that as many tasks around review, testing, merging and release that
can be automated should be.
Jenkis is essentially a job queing system, and everything that is done
Jenkins is essentially a job queing system, and everything that is done
through Jenkins can be thought of as having a few discreet components:
* Triggers - What causes a job to be run

6
doc/source/stackforge.rst
View File

@ -185,9 +185,9 @@ change to review.openstack.org.
Add .gitreview file to project
==============================
Once the change created following the above steps is merged and applied
to Gerrit, Jenkins, et al you will want to add a ``.gitreview`` file to
your repository in order to use the ``git review`` tool.
If the new project you have added has a specified upstream you will need
to add a ``.gitreview`` file to the project once it has been created. This
new file will allow you to use ``git review``.
The basic process is clone from stackforge, add file, push to Gerrit,
review and approve.::