Concept · entity · registered
Deployment
The act of putting a build into an environment. The same release can be deployed many times, and a deployment can fail to reach the environment while the release still exists. A deployment is not a release, not a version, and not the environment it targets. It is not a change request. The change request is the proposal, and a deployment is one way that proposal is carried out. Putting bytes into an environment is not the same as showing new behavior to users. A feature flag can do that with no further deployment. Whether the deployment reached the environment, and whether it then required remediation, is the deployment outcome.
Definition
What Deployment means
Used in data
In OVDB databases
Databases, recordsets and fields whose meaning is this concept, a kind of it, or whose values are instances of it. Rows open the OVDB Directory.
No OVDB database carries this concept yet.
Properties
What we can say about Deployment
These properties describe meanings and reference targets. Storage types, required fields, and cardinality belong to the consuming data model.
| Property | Meaning | Values and units |
|---|---|---|
| Deployment build | The build that was put into the environment. | Values reference Build |
| Deployment change request | The change request this deployment carries out, when one is recorded. A deployment can have no change request, and a change can be carried out by something other than a deployment. | Values reference Change request |
| Deployment date | When the deployment was carried out. The record may be a calendar day or an instant. It is not the identity of the release and not the version number. | Scalar meaning |
| Deployment environment | The environment the build is put into. A deployment to staging and a deployment to production are different deployments even when they carry the same release. | Values reference Environment |
| Deployment outcome | What this deployment did: whether it reached the target environment, and whether the service then had to be remediated, for example by a rollback or a follow-up fix. A deployment that never reaches production is not counted in deployment frequency and is not a change failure. A deployment that reaches production and degrades the service is counted in the frequency and in the change failure rate. The outcome of one deployment is not either of those rates. | Scalar meaning |
| Deployment release | The release this deployment puts into an environment, when the deployment is of a named release. Deploying a build that was never named as a release leaves this empty. | Values reference Release |