Job Retries

On March 7, 2018, Buildkite introduced an update that preserves job history when a retry is performed. Previously, the original job's history was lost upon retries. Now, with this new feature, the history remains intact and a new job is created. Additionally, users can now see whether a job has been retried, as well as if it was retried automatically or by a user. The number of retries is also available as an environment variable on the job. Furthermore, Buildkite allows for fine-grained control over retry conditions, enabling users to specify when steps should be retried based on exit codes and prevent retries on important steps like deployments. An example code demonstrating different retry configurations is provided in the command step docs.