Skip to content

Allow Watson deployment job to continue on failure - #5

Merged
ocularminds merged 1 commit into
masterfrom
codex/tolerate-watson-deploy-failure
Jul 29, 2026
Merged

Allow Watson deployment job to continue on failure#5
ocularminds merged 1 commit into
masterfrom
codex/tolerate-watson-deploy-failure

Conversation

@ocularminds

Copy link
Copy Markdown
Owner

Summary

  • set continue-on-error: true on the production deployment job
  • keep IBM Cloud authentication and deployment failures visible in step logs
  • prevent an expired or missing Watson/IBM Cloud key from failing the overall workflow run

Observed failure

The latest deployment stopped during IBM Cloud login with BXNIM0415E because the configured API key could not be found. The run also exposed empty region and resource-group values.

Behavior change

This is intentionally job-scoped. Any failure in the deploy job—not only credential expiry—will be tolerated by the workflow until the deployment credentials are restored.

Validation

  • actionlint -shellcheck '' .github/workflows/deploy-code-engine.yml
  • git diff --check

Actionlint also reports two pre-existing shell-script advisories when ShellCheck integration is enabled; neither is related to this one-line change.

@ocularminds
ocularminds marked this pull request as ready for review July 29, 2026 11:53
@ocularminds
ocularminds merged commit 6a452bf into master Jul 29, 2026
2 checks passed
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.

1 participant