EU1: Codebase Expression Fails to Resolve in Pipelines Across Multiple Projects (Partial outage)

Incident Report for Harness

Postmortem

Incident Summary:We recently identified and resolved an issue that caused pipeline executions using Harness Code repositories at the project level to fail in resolving codebase-related variables. This impacted customers relying on expressions such as <+codebase.branch> or <+codebase.commitSha> in their CI pipelines. Pipelines themselves continued to run, but expressions referencing codebase variables returned null or failed silently.

Root Cause:

A recent update included logic to support hyperlinking commit references in pipeline logs for Harness Code repositories which had a bug related to parsing the repository identifiers

Remediation & Improvements:

We’ve deployed a fix that correctly parses and handles project-level repository slugs when resolving codebase variables.

To prevent this from happening again, we are taking the following actions:

  • Expanding automated test coverage to include variable resolution in CI pipelines using Harness Code at all scopes (account, org, project)
  • Introducing test scenarios that cover Harness Code as the source repo in pipelines
  • Implementing enhanced monitoring in our QA environments to detect unexpected errors introduced by new changes
Posted Jun 04, 2025 - 20:40 PDT

Resolved

Issue is resolved.
Posted May 20, 2025 - 08:52 PDT

Monitoring

Rolled back the deployment and customer confirms
Posted May 20, 2025 - 08:52 PDT

Identified

We are rolling back the deployment and validating
Posted May 20, 2025 - 08:35 PDT

Investigating

We are currently looking into an issue where codebase Expression is failing to Resolve in Pipelines Across Multiple Projects
Posted May 20, 2025 - 08:15 PDT
This incident affected: Prod Eu1 (Infrastructure as Code Management (IaCM)).