Commit ce4e30e8 authored by Marcel Amirault's avatar Marcel Amirault

Merge branch 'document-missing-job-failure-reasons' into 'master'

Document missing job failure reasons

See merge request gitlab-org/gitlab!23889
parents bf51d68c 8b0989b3
......@@ -2521,6 +2521,12 @@ Possible values for `when` are:
- `runner_system_failure`: Retry if there was a runner system failure (e.g. setting up the job failed).
- `missing_dependency_failure`: Retry if a dependency was missing.
- `runner_unsupported`: Retry if the runner was unsupported.
- `stale_schedule`: Retry if a delayed job could not be executed.
- `job_execution_timeout`: Retry if the script exceeded the maximum execution time set for the job.
- `archived_failure`: Retry if the job is archived and cannot be run.
- `unmet_prerequisites`: Retry if the job failed to complete prerequisite tasks.
- `scheduler_failure`: Retry if the scheduler failed to assign the job to a runner.
- `data_integrity_failure`: Retry if there was a structural integrity problem detected.
### `timeout`
......
......@@ -95,14 +95,20 @@ describe Gitlab::Ci::Config::Entry::Retry do
# values are valid. If they are not it means the documentation and this
# array must be updated.
RETRY_WHEN_IN_DOCUMENTATION = %w[
always
unknown_failure
script_failure
api_failure
stuck_or_timeout_failure
runner_system_failure
missing_dependency_failure
runner_unsupported
always
unknown_failure
script_failure
api_failure
stuck_or_timeout_failure
runner_system_failure
missing_dependency_failure
runner_unsupported
stale_schedule
job_execution_timeout
archived_failure
unmet_prerequisites
scheduler_failure
data_integrity_failure
].freeze
RETRY_WHEN_IN_DOCUMENTATION.each do |reason|
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment