Retry mechanism on tasks

step
#1

Description of the feature request

Give the opportunity to the user to choose an attempt count to a step so that if the step fails it can be re-tried up-to this maximum.
This is especially useful for specific tasks, like tasks that rely on 3rd-party platforms that cannot ensure 100% reliability.

Use case / for what or how I would use it

Initial request: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues/39
When using Virtual-Device-Testing for Android we’ve noticed that sometimes the 3rd-party platform that provides Android devices doesn’t work as expected. Google is working on it, but Bitrise should be able to provide a mechanism to avoid this kind of issues to block builds.

As an alternative, maybe just consider a way to mark the build as Ignored instead of Failed?
(Something to distinguish builds that didn’t run as expected due to the step itself, from builds that have run as expected but the result is failing due to broken tests for example.)

0 Likes

#2

Thanks for the feature request, this is a work in progress already :upside_down_face:

0 Likes

#3

Great to hear that! And thanks for the super-quick feedback :grinning:

Is it related to this ticket: Option to Auto Retry/Rebuild When Build Fails

My initial idea was more step-retry than build-retry but build-retry could work for me… if it can handle the difference between test failure and step failure. (And if it can, my ticket is irrelevant and can be closed.)

1 Like

#4

No problem, I’m not really sure on the process of this but I see it being implemented on different steps in the past weeks.

0 Likes