Duplicate writes in Jenkins Pipeline retry step during transient failures
The goal is to use the Jenkins Pipeline retry step to handle transient failures without causing duplicate writes to external resources such as files or database records. The retry step re‑executes the entire block on any exception up to the configured count, and it does not provide a built‑in option to check whether a side‑effect has already succeeded or to