Platform Events
Release notes
Problem to solve
As a GitLab engineer, I want to automate workflows based on events that occur in the GitLab platform, so that I can build useful features for my users.
As a system integrator, I want to integrate with GitLab and initiate workflow in other systems based on GitLab events or trigger actions in GitLab based on events from an external system, so that the users of GitLab and the other system can benefit.
Intended users
Proposal: Events is an important primitive and we should first serve our internal use cases
User experience goal
TBD
Proposal
CI/CD, SCM, Issue, and other events are not unique to GitLab. There's a proposal to standardize in the CDF Events SIG. Even though the SIG's proposal is mainly about interoperability between vendors, implementing based on an emerging standard enables to solve for GitLab's internal interoperability use cases first and provides the option to enable external interoperability.
Further details
CDF Event SIG Highlights
More details can be found in https://github.com/cdfoundation/sig-events/blob/main/vocabulary-draft/introduction.md
- CI/CD Events are CloudEvents
- Core events relate to the pipeline. E.g. PipelineRun started, queued, finished, TaskRun (a.k.a. jobs) started, queued, finished.
- Source Code Version Control Events are events that occur in the code repository. E.g. Repository created, branch deleted, change merged
- CD events relates to deployment. E.g. environment created, service rollback.
Other DevOps Events
We can create additional cloudevents that are not covered by the CDF Events SIG. For example events related to issues or when a security vulnerability is found.
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.