[Question] What has changed with the shift from “triggers” to “webhooks”?

[EliottPaillard]

Hey @costas80,

We have an external tool that uses ITB version 1.28.5 with what were then still called “triggers,” primarily to retrieve test reports.
Since upgrading to a newer version of ITB—specifically version 1.29.0 and the change from “triggers” to “webhooks”—the tool still retrieves the test reports but can no longer display the test status as it did before (it consistently returns “undefined”).

I know this is a rather sparse description, but these are the only details I have myself.

So my question is: “Aside from this feature name change, have any other changes been made?”

I imagine that some variables potentially containing a direct reference to the term “trigger” might have been renamed, for example. But if you know of any others, I’d love to hear about them :)

Thank you !

[costas80]

Hi @EliottPaillard.

The renaming of "triggers" to "webhooks" was purely a labelling change. We initially didn't use the term "webhooks" because in the ITB these can be used to do more that a fire-and-forget webhook typically does (you can also return configuration data). However this distinction was quite niche, and we chose to go for "webhooks" to make the concept immediately understandable. So, in brief, the "webhook" renaming is just a labelling change.

the tool still retrieves the test reports but can no longer display the test status as it did before (it consistently returns “undefined”)

This point is surprising and any changes to this behavior were unintended (or unrelated). Can you provide a bit more information on this (what operation you used and what you saw before vs what you see now)?