holdenk opened a new pull request, #59695: URL: https://github.com/apache/spark/pull/59695
### What changes were proposed in this pull request? Probe issues.apache.org before relying on JIRA and, when the SPARK backend is down, returns a 5xx (e.g. the 503 the reverse proxy serves when the backend is unhealthy), or is too slow to answer, disable all JIRA steps for the run and log it instead of failing or hanging the merge. The committer reconciles the ticket by hand afterward. When JIRA is live, access stays mandatory as before. The probe reuses the client's read timeout (hoisted from a hardcoded 30 into the new JIRA_READ_TIMEOUT) as its budget, so there is no separate liveness timeout concept. This addresses https://github.com/apache/spark/issues/59693 ### Why are the changes needed? JIRA goes down sometimes ### Does this PR introduce _any_ user-facing change? No, infra/dev facing only. ### How was this patch tested? Ran ./dev/merge_spark_pr.py while ASF JIRA was down. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 5.5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
