Skip to content

fix(cli): ensure deploy command exits with error if rollout times out - #92

Merged
volkanarisli merged 1 commit into
mainfrom
feature/eco-1227-a-ci-jobs-result-tells-the-truth-about-the-deploy
Oct 23, 2026
Merged

volkanarisli merged 1 commit into
mainfrom
feature/eco-1227-a-ci-jobs-result-tells-the-truth-about-the-deploy

Conversation

@volkanarisli

Copy link
Copy Markdown
Contributor

deploy exited 0 when the rollout didn't finish within the 10-minute wait limit, so a CI job passed without the new revision serving.

Now a timed-out rollout exits 1. Ctrl-C and --skip-activation still exit 0, because the user chose to detach. The timeout message now says the revision is not confirmed to be serving.

Docs: AGENTS.md and the deploy guide now list the exit codes, and the guide has a new "What the job result means" section for CI.

@github-actions

Copy link
Copy Markdown
Contributor

Coverage report

Click to see where and how coverage changed

FileStatementsMissingCoverageCoverage
(new stmts)
Lines missing
  haystack_enterprise_sdk
  cli.py
Project Total  

This report was generated by python-coverage-comment-action

@mrchtr mrchtr left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @volkanarisli.

@volkanarisli
volkanarisli merged commit f76b603 into main Oct 23, 2026
6 checks passed
@volkanarisli
volkanarisli deleted the feature/eco-1227-a-ci-jobs-result-tells-the-truth-about-the-deploy branch October 23, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants