Verificando autenticación…

Skip to main content

events

All GitLab events are published to a Pub/Sub topic:

projects/sp-te-engplat-prod-cce9/topics/andes-gitlab-events

GitLab Events​

The following GitLab events are available on the Pub/Sub topic:

Code and repository events​

  • Push events - When code is pushed to the repository (all branches)
  • Tag push events - When a new tag is created
  • Wiki page events - When a wiki page is created or updated

Development events​

  • Issue events - When an issue is created, updated, closed, or reopened
  • Confidential issue events - Confidential issue events
  • Merge request events - When an MR is created, updated, or merged
  • Comments - Comments on issues or merge requests
  • Confidential comments - Comments on confidential issues

CI/CD events​

  • Pipeline events - When a pipeline status changes
  • Job events - When a job status changes
  • Deployment events - When a deployment starts, finishes, fails, or is canceled

Management events​

  • Project events - When a project is created or deleted
  • Subgroup events - When a subgroup is created or deleted
  • Member events - When a group member is created, updated, or deleted
  • Milestone events - When a milestone is created, closed, reopened, or deleted

Security and quality events​

  • Vulnerability events - When a vulnerability is created or updated
  • Project or group access token events - Access token events
  • Feature flag events - When a feature flag is enabled or disabled

Additional events​

  • Releases events - When a release is created, updated, or deleted
  • Emoji events - When an emoji is awarded or revoked

Event structure​

GitLab events follow a specific structure that contains detailed information about each event type. To learn the complete structure and available fields for each event type, see the official GitLab documentation:

📖 Webhook Events - GitLab Documentation

How to consume events​

Teams that need to consume GitLab events from the Pub/Sub topic must follow this process:

Request process​

  1. Create a ticket using ANDES Bot option 8.0

  2. Required information in the ticket:

    • Subscriber service account: Provide the service account to assign the necessary roles.
    • Domain: Domain the requester belongs to.
    • Integration owner: Name and email address.
    • Integration maintenance team: Name and email address.
    • Reason for the request: Reason or circumstance for requiring access to the events.
    • Specific event types (optional): If you only need to consume certain event types, specify which ones from the list above.
    • Subscription name: Name of the new subscription to create. It must follow these rules:
      • Between 1 and 63 characters - Naming convention: <resource-type>-<environment>-<product/application>-[function]-<correlative>
        • E.g. sub-prod-gitlab-reporter-01