Jeremy Stanley 5e063d7f1d General updates for the Test Environment chapter
Test Environment hasn't been touched in a while and needs a bit of a
refresh to reflect changes to our systems in recent years as well as
removing some OpenStackisms and a bit of rewording in places for
added clarity.

Change-Id: I69156ed7ef88d9584638d59825d44f982d0cf4b4
2023-01-30 18:15:58 +00:00
2020-03-20 16:07:06 +01:00
2014-05-26 20:25:48 -04:00
2020-03-05 16:37:12 +01:00
2020-03-27 09:28:57 -07:00
2020-03-04 21:08:06 +01:00
2019-05-30 21:19:53 +02:00

OpenDev Manual

To build the manual, execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory.

Terminology

A note on terminology use in the manual:

This manual is in service of OpenDev, but does so primarily by documenting how developers and project drivers can use the infrastructure to accomplish their work.

We strive for consistent terminology that matches what developers and our tooling use, even if some hosted projects use different terminology.

Generally speaking these terms should be used as follows:

Project: The overall idea that there is a bunch of people working on a bunch of code/text/etc. It can also refer to that actual collection of code/text/etc (for instance, a project can be bundled up into a tarball, and extracted into a directory). When a tool interacts with that collection of code/text/etc, it interacts with the project (even if it does so via the mechanism of git).

Repository: There are times when one needs to refer to the actual source code management system of a project, that is, "git", and the actual technical implementations of that SCM. In those cases where it is important to distinguish the actual attributes of the SCM from the project, it is useful to use the word "repository".

Description
OpenDev Manual
Readme 4.4 MiB
Languages
Python 100%