Get Started
Terminology
Key terms for working with Ocuroot
Term | Description |
---|---|
Organization | An Ocuroot instance distinct from all others. May represent a business, department or team. Contains one or more Environments and Repos. |
Environment | A distinct “location” where Builds of Packages may be deployed. For example, you may have a staging and production Environment. |
Repo | A single Git repository that contains one or more Packages. |
Package | A collection of code that may be built and deployed independantly. |
Change | A snapshot of the state of a Git repository at a given time. This may specify a commit and optionally an uncommitted diff on top of it. |
Build | The output of building a Package at a specific Change. |
Deployment | The result of deploying a Package to an Environment. This may be depended on by downstream Deployments. |
Policy | Custom rules that define whether or not a Build may be deployed to an environment. |
Target | The desired state of a Package within an Environment, which may include a Build and a set of inputs, or the expectation that the Package is not running. |