Glean CI Integration

Overview

Set up CI/CD for Glean enterprise search integrations: run unit tests with mocked search and indexing responses on every PR, validate connector document transforms and search quality against a staging Glean instance on merge to main. Glean indexes content across SaaS tools, so CI pipelines focus on connector data transforms, indexing API calls, and search relevance regression testing.

Prerequisites

• A CI secret reference rather than a literal token and a sandbox endpoint accepting only fictitious tenant and datasource IDs.
• Fixtures with no employee names, customer content, or production URLs; redact headers and bodies from logs.
• A protected branch and an approved rollback mechanism for any deployment or connector configuration the pipeline can influence.

Instructions

1. Run mocked unit tests first, including deny-by-default ACL and malformed-response cases.
2. Run a bounded sandbox batch with an idempotency key; prohibit production destinations in CI configuration.
3. Emit only aggregate counts, correlation IDs, and policy versions, and fail on an unexpected destination, expanded ACL, or unredacted log assertion.
4. Promote through a canary datasource after review, test both allow and deny identities, and restore the last known-good revision on failure.

GitHub Actions Workflow