Last date of deploy -date is wrong

🆘 Support
#1

I have two environments in GitLab and I have built two build triggers to build and deploy my site to two different Firebase Hosting sites. There is a staging environment and a production environment. But when building & deploying just the staging environment, the production also says in Dato that the Last date of deploy would be the same as in the staging environment.

I think this is because of the webhook is triggered by a pipeline event, event if the pipeline is not for the production environment.

Is there a way to read the Request body to know for example which stage is the trigger affecting? Because now it is very confusing to see that the production version also went live, when the aim was only preview the changes in the staging environment.

#2

Screenshot 2021-09-08 at 14.24.14

#3

Screenshot 2021-09-08 at 15.10.20

#4

Hello @pepita.kautto each build trigger should have different success/failure endpoints that you should call.

Are you sure that you are using the appropriate one for each trigger? Meaning the Gitlab CI for staging using the staging endpoints, etc?

#6

Hello,

I have a repository that includes two environments, production and staging. Also in Dato, I have two build triggers, that trigger each job that will build and deploy the code from master branch to its designated environment. I’m using the custom environment variable from Dato to tell the ci/cd job which one I want to trigger.

The problem seems to be that the pipeline event webhook from Dato is triggered every time any pipeline event happens. The request body is telling which environment was supposed to be updated but as there is a pipeline event, both of these will give the updated Last date of deploy in the UI.

Is there a way to read the environment part of the request body and pair that with the notification of the last date of deploy? Or do you have any other suggestions how this date could be updated correctly? Or then just hide the text so it does not confuse our client too much?

#7

Can you please confirm that you are using the two different webhooks, one per production and a different one per staging that you can find here:

Screenshot from 2021-09-15 09-43-48
Screenshot from 2021-09-15 09-43-48879×433 46.8 KB

If so, maybe we should have a call together to understand if there’s a problem in your setup or a bug on our end. Feel free to book a slot here: Calendly - DatoCMS

Thanks

1 Like
#8

Hello,
yes, I do have two webhooks, one for each environment. But as the webhook is triggered by any pipeline event in the repository, both webhook will get triggered!

Thanks, I will book us a call! :blush:

#9

Hi,
do we have any updates on this issue? :nerd_face:

#10

sorry, not yet, but I think we can do something about it. We’ll be in touch!

#11

Hi @pepita.kautto !

It seems that you misconfigured your build triggers. When creating two different build triggers, you need to specify two different branches for each trigger, otherwise DatoCMS won’t be able to tell which Gitlab branch triggered the webhook.

DatoCMS-docs 2021-11-04 at 09.38.47

If you need more detailed assistance, please write to support@datocms.com

Thanks!