For my project I configured Built trigger linking GitLab pipeline
GitLab webhook is also setup properly against the Build Trigger
When Build trigger starts, seeing that GitLab CI starts.
And, when GitLab CI completes, then Build Trigger enabled again.
But confusion or error is when we stopped the GitLab CI pipeline manually, that status is not being properly handled in the Build Trigger. It is keep on saying " Build In Progress " until we manually abort the process.
Hmm, it seems like our Gitlab-specific build trigger is currently only set up to handle the statuses success and failed, but apparently Gitlab can also send a skipped status (presumably for manual cancellations):
I’ll let the devs know about this to see if we can add that.
If you need it more urgently, you can use a custom webhook in DatoCMS to manually configure a similar pipeline with your own status mappings. You can also use the CMA to manually mark a build trigger as failed (presumably tying it into Gitlab’s pipeline status changes, if it allows you to do that): https://www.datocms.com/docs/content-management-api/resources/build-trigger/abort
Otherwise, I’ll report back once the devs have a chance to look into our official build hook for Gitlab. Thanks for the report!
Thank you @jeyasuriya1994. I’ll let them know about the different values.
Do you happen to know what the different statuses mean? e.g. when you stop a pipeline manually, is it canceled? What would trigger a skipped or manual or unknown status, if you happen to know?
Our devs are all focused on that at the moment, so it may take a while for us to be able to look at the build trigger issue. I will update you as soon as you can.
In the meantime, once the systems come back up, please let me know if you need help with the custom webhook workaround in the time being.
