[JENKINS-54735] Pipeline retry clause: optionally delay between retries

I use a retry block to perform requests on a remote server that I don't control (e.g., Apple's Code Signing or Notarization service), and sometimes that remote server is offline.

Currently retry immediately retries upon failure, so when the remote server is offline for an extended period of time, my pipeline project quickly retries and then the build fails.

It would be nice to have the ability to make retry wait after each failure, with optional exponential backoff (doubling the wait time after each failure), to give these builds a greater chance of success.  For example:

retry(tries:5, waitSecondsBetweenFailures:30, doubleWaitTimeAfterEachFailure:true)

---
Originally reported by smokris, imported from: Pipeline retry clause: optionally delay between retries

• status: Open
  
• priority: Major
  
• component(s): workflow-basic-steps-plugin
  
• label(s): pipeline
  
• resolution: Unresolved
  
• votes: 19
  
• watchers: 21
  
• imported: 20251215-220547
  

I use a retry block to perform requests on a remote server that I don't control (e.g., Apple's Code Signing or Notarization service), and sometimes that remote server is offline.


Currently retry immediately retries upon failure, so when the remote server is offline for an extended period of time, my pipeline project quickly retries and then the build fails.


It would be nice to have the ability to make retry wait after each failure, with optional exponential backoff (doubling the wait time after each failure), to give these builds a greater chance of success.  For example:


retry(tries:5, waitSecondsBetweenFailures:30, doubleWaitTimeAfterEachFailure:true)

Inizia individuando l’implementazione della clausola di retry in workflow-basic-steps-plugin e verificando come viene testato il comportamento attuale dei retry. Definisci il ritardo e il comportamento opzionale di exponential backoff rappresentati dall’esempio, quindi verifica che i retry attendano come specificato senza modificare il comportamento esistente quando le opzioni vengono omesse.

Scritto dal modello di indicizzazione a partire dal testo della issue.