Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Resolve status update issue for GitLab instances with relative paths
Issue: For GitLab instances hosted under a relative path (e.g., https://example.servehttp.com/gitlab), status updates on MR fail to propagate correctly. Although initial events like Repository CR creation, starting PipelineRuns based on webhooks from GitLab, reporting status on Pipeline start works fine. subsequent updates (e.g., marking the PipelineRun as Finished) do not reflect in GitLab, leaving the status stuck on Running state. Root Cause: The sourceProjectID and targetProjectID in the event object were being reset to for GitLab instances with relative paths, causing API requests to GitLab (https://example.servehttp.com/gitlab/api/v4/projects/gitlab/root/testpac) to fail with a 404 error. With this PR changes now status is getting updated successfully. Signed-off-by: savitaashture <sashture@redhat.com>
- Loading branch information