Limiting the retries of builds on non-master branches via code repo

Ask the Community
,
1

Hello Community,

Problem statement:
When I trigger a build via the code repository and my compute fails for some reason, the build is retried two more times. This happens on non‑master branches.

Is there a solution to limit the number of retries to one for non‑master branches?

So far I found that I can create a schedule on the non‑master branch and then limit retries, but I’m looking for a solution that uses the code repository only (no schedules).

2

Hi STR,

The way I would do this, is:

  • have an additional output, where:
    • I have a column with the timestamp
    • and another column with the Success and Failed
  • in the code I would verify the last x entries if it failed or not and proceed accordingly.

Hope it helps,

Rita

(ps. to add an output as also a reference for input, there is a need to use @incremental but the logic can stay the same and if using snapshot )

3

work around seems worthy trying but I am not a big fan of seeing fx in my lineage but this for sure reduces the retries.