Documentation

Commit hash visibility delay in Cloud Manager pipeline

Last update: Wed Nov 19 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When triggering a pipeline in Cloud Manager with a private GitHub repository, the commit hash appears only after the build or code quality step completes. This is because the system updates the commit hash after code checkout inside the build container.

Description description

Environment

Cloud Manager

Issue/Symptoms

  • The commit hash for the source code isn’t visible in the Cloud Manager UI at the moment the pipeline is triggered.
  • It becomes visible only after completion of the build or code quality step.

Resolution resolution

To address this issue, follow these steps:

  1. Trigger the pipeline in Cloud Manager using a private GitHub repository.
  2. Wait for the build or code quality step to finish.
  3. Check the Cloud Manager UI to confirm the commit hash appears.
  4. Confirm that the commit hash appears only after code checkout inside the build container.

Note: This behavior is by design. The commit hash updates only after code checkout inside the build container. There is no supported method to display the commit hash instantly at trigger time.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f