Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ewake.ai/llms.txt

Use this file to discover all available pages before exploring further.

What you’ll get: After connecting Gerrit, ewake can track submitted changes and correlate them with production behaviour, particularly useful in organisations that run Gerrit alongside a separate CI/CD system.

Prerequisites

  • A Gerrit instance with HTTP access enabled
  • A Gerrit account with read access to the projects you want to monitor

Configuration

1

Generate HTTP credentials in Gerrit

In Gerrit, go to your user avatar (top right) → SettingsHTTP Credentials → click Generate Password.Note your username (shown above the password section) and copy the generated HTTP password.
2

Connect in ewake

In your ewake dashboard, go to IntegrationsGerrit → click Configure.
FieldValue
Gerrit Base URLYour Gerrit instance URL (e.g. https://gerrit.your-domain.com)
UsernameYour Gerrit username from Step 1
HTTP PasswordThe password generated in Step 1
Click Test Configuration, then Save.
Gerrit is connected. Ewake can now correlate production incidents with submitted changes.

Ewake uses read-only access to Gerrit. It never submits, abandons, or comments on changes.