Iāve a Build trigger created from Dato web UI following excellent guidance it provides. It triggers the right CI Pipeline in our self hosted GitLab CE instance and the pipeline runs and finishes correctly just as it should. āPipeline eventsā webhook (per Dato UI guidance) is also set up and according to GitLab it works. Response from webhooks.datocms.com is 200 OK.
Problem is, the trigger never finishes in Dato project dashboard. Build status never changes from āBuild in progressā¦ā to anything else (Iāve let it go on over a weekend ). Only option is to click āAbort and mark as failedā. In addition, sometimes triggering a new build, or aborting an āongoingā one, invokes three or more notifications in the UI.
Our use case is to provide our customer (weāre an agency) means to make a new release to production when they think everything is ready. (They also have a livepreview and staging environments for validation separate from this.)
Please ask if in need of any details or more information. Thank you.