User Story

As a developer using the PaC integration, I want to consistently receive a final "Pipeline run completed" comment (whether successful or failed) in my GitLab Merge Request, so that I am immediately notified when my pipeline process is truly finished without needing to manually check Konflux or GitLab status dashboards.

Description

This issue relates to inconsistent feedback mechanisms provided by the PaC integration after a Konflux pipeline run is triggered.

Currently, we observe that the initial "starting pipeline run" comment is reliably posted. However, the subsequent "completed pipeline run" comment (indicating success or failure) is often missing, leaving the user without confirmation that the job has concluded. This occurs even in cases where the pipeline run status in GitLab is correctly updated (i.e., it is not a "zombie" run).

The behavior should be consistent: if we send a "started" comment, we must send a "completed" comment. If the "started" comment is also deemed unnecessary, that should be addressed as part of this investigation.

Related Context: Pipelines (For Reference)

• Primary Jira Ticket: KONFLUX-10902 (https://issues.redhat.com/browse/KONFLUX-10902)

• Example GitLab MR (where comments were inconsistent): https://gitlab.cee.redhat.com/openstack-konflux/openstack-13/-/merge_requests/686

This bug is often conflated by users with another known issue (SRVKP 8318) where PaC fails to update the final pipeline status in GitLab, leaving the pipeline stuck in a "running" (zombie) state even after Konflux completes it (often due to timeouts). The fix for the comment issue should be designed to handle both scenarios, ensuring the comment is sent regardless of whether the final status update attempt failed or succeeded.

Acceptance Criteria

1. PaC should post a final completion comment (success or failure) to the relevant artifact (e.g., GitLab MR) immediately after the pipeline run completes in Konflux, regardless of the run's final status.
2. The completion comment must accurately reflect the final state of the pipeline run (e.g., success, failed, cancelled).
3. The team should investigate and confirm the intended product behavior of the "starting pipeline run comment," deciding whether it should be consistently sent or removed entirely.
4. If a pipeline run fails to update its status in GitLab (the "zombie" scenario), Pac must still attempt to post the final completion comment to provide user feedback.