Open praveen-mummasani opened 5 years ago
we just re-trigger the build again from Jenkins
That is why MR is not updated in GitLab. Because Jenkins does not have MR context when manually triggered. So it can not wire up pipeline run with GitLab MR.
and need to push dummy commit again to get the latest status as green
Instead you can use "Comment (regex) for triggering a build" GitLab plugin property to specify MR discussion message that will re-trigger build in Jenkins.
Hello @antonovicha,
I'm facing a similar issue. I tried the fix you proposed (re-triggering via Gitlab comment). Unfortunately, this does not resolve the issue. The second pipeline is successful, but the Gitlab pipeline status is still "failed". Is this a bug in the plugin or in Gitlab itself?
Issue
When we create a MR,we are able to see build status as running in the GitLab.Due to any issue the build fails and we just re-trigger the build again from Jenkins,gitlab is not showing latest build status and just showing build status as failed from the previous build.
Context
Logs & Traces
No Logs in the GitLab
Problem description
Describe your problem in a meaningful way: