trigger-pipeline: Can you add re-try logic?

Question

The Bitbucket API intermittently returns a 500 Internal Server Error for no good reason when doing a Get operation on their pipeline APIs. I see this in my own API programs. Our use of the trigger-pipeline pipe is failing frequently even though the pipeline itself succeeded: INFO: Attempt number 30: Getting build info.✖ Failed to get the build data. Response code: 500. Error: {"type": "error", "error": {"message": "Internal server error", "id": "00885453dd1647dc80f9f12c23b4620c"}} It would be awesome if you could add some re-try logic for this case.

Halyna Berezovska · Answer

@Jay Seletz hello,  feel free to try new version 4.1.6 and ensure it fixes your issue!

Kind regards, Galyna

Oleksandr Kyrdan · Answer

Hi @Jay Seletz ,

Thank you for your feedback!

Good suggestion! We'll think about this feature in the trigger-pipeline pipe.