Problem Statement

When CI pipelines are triggered via issue comment triggers, Harness sets CI_COMMIT_MESSAGE using the PR description instead of the latest commit message.

For PRs with large descriptions, this leads to:

Significant increase in pod.yaml size

Repeated injection of large strings into environment variables

Excessive CPU/memory requests due to aggregation

Kubernetes API rejecting pod creation with:

rpc error: code = InvalidArgument desc = Request contains an invalid argument

Expected Behavior:

CI_COMMIT_MESSAGE should contain:

The latest commit message

Business Impact:

Large PR descriptions are standard in enterprise workflows (include testing, validation, compliance info). Current behavior leads to:

Pipeline failures

Infrastructure instability

Increased debugging effort due to vague Kubernetes errors

Additional Context:

Issue reproduced even after:

Enabling CI_COMMON_ENV_POD

Reducing pipeline steps

Observed pod.yaml size inflation due to repeated env vars

Confirmed by Harness Support as expected behavior

Ticket reference: https://support.harness.io/hc/en-us/requests/109478