Lifecycle Event Definitions
The types of Events supported by the CTO.ai platform are divided among a pair of categories: Deployment Events and Change Events. The purpose of this page is to document the different types of Events currently recognized by the CTO.ai platform.
When an Event is sent to our platform from an integration, it is transformed into a standardized format in line with the schemas documented on this page. In all cases, the raw Event data—from both known and unknown Event types—is also stored in our database for possible use in the future.
Event State Definitions
This section describes the different workflow states that are currently represented within the CTO.ai platform. Irrespective of source, all supported Events received from our integrations are transformed into one of these states before being processed by our platform or used to calculate Insights metrics.
Deployment Lifecycle States
Deployment Events represent the different states of your infrastructure as a deployment occurs.
For deriving Insights about your deployment processes, we currently use just two events—Success and Failure—which record the completion status of a deployment process. However, we still collect other events for use in workflow triggers and other future uses.
| Name | Event Description |
|---|---|
| Success | Deployment of new change has completed successfully. |
| Failure | Deployment of new change has failed. |
| Started | Deployment of new change has started. |
| Progressing | Deployment of new change is in progress. |
| Blocked | Deployment of new change is blocked. The cause of the blocked deployment is dependent on the source infrastructure. (For example, the deployment mechanism may have features that allow deployments to wait for approval.) |
For more information on the expected format of Deployment Events sent to our platform, see the Deployment Events Schema reference documentation.
Change Lifecycle States
Change Events represent different stages of the development (change) lifecycle.
Two events matter for deriving Insights about your development processes: Open and Merge. However, we still collect other events for use in workflow triggers and other future uses.
| Name | Event Description |
|---|---|
| Open | New Pull Request has been created at the source. |
| Review Requested | Review has been requested on the Pull Request. |
| Change Requested | Changes have been requested by the reviewer of the Pull Request. |
| Change | Changes have been made by the author in response to the requested review of the Pull Request. |
| Merge | Pull Request and the changes it contains have been merged into base branch. |
| Close | Pull Request has been closed without merging commits into base branch. |
| Reopen | Pull Request that was closed has been opened for review. |
For more information on the expected format of Change Events sent to our platform, see the Change Events Schema reference documentation.