dotCMS / dotCMS/core

CI/CD: Skip Claude AI Orchestrator step when Claude service is unavailable

Open
#35,328 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Description

Currently, the CI/CD pipeline is blocked when Claude AI service is down, preventing builds from completing. The Claude AI Orchestrator step should gracefully skip when the service is unavailable rather than blocking the entire pipeline.

Example of blocked run: https://github.com/dotCMS/core/actions/runs/24461196854

Rationale
  • CI/CD reliability should not depend on external AI service availability
  • Pipeline failures due to Claude being down cause unnecessary delays for the engineering team
  • Other PR checks and validations should still be able to complete

Acceptance Criteria

  • Claude AI Orchestrator step detects when Claude service is unavailable
  • When unavailable, the step skips gracefully with a clear warning message (not a failure)
  • Pipeline continues with remaining steps when Claude is unavailable
  • When Claude is available, the step runs normally as expected
  • Consider adding a timeout mechanism to avoid long waits during service degradation

Additional Context

Slack discussion: https://dotcms.slack.com/archives/C06SSEX2TS8/p1776270907489129?thread_ts=1776269966.484939&cid=C06SSEX2TS8

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the GitHub Actions workflow containing the Claude AI Orchestrator step and compare it with the blocked run linked in the issue. Trace how service-unavailable responses and long waits are handled, then verify that unavailable-service runs warn and continue while available-service runs still execute normally.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.