Skip to content

docs: add use case for failing a pipeline on upload failures#24

Open
jthDEV wants to merge 1 commit into
mainfrom
docs/uc04-fail-on-upload-failure
Open

docs: add use case for failing a pipeline on upload failures#24
jthDEV wants to merge 1 commit into
mainfrom
docs/uc04-fail-on-upload-failure

Conversation

@jthDEV

@jthDEV jthDEV commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Adds Use Case #4 – Fail a Pipeline on Upload Failures under Usage → Use Cases.

Why

ts-scan upload intentionally exits with code 0 even when the transfer fails, so a transient platform issue doesn't break an otherwise green CI/CD pipeline. That's the right default, but it means a failed upload (and thus a missing SBOM in TrustSource) can go unnoticed. This use case documents how to opt into hard-failing where a missing SBOM is a real compliance gap.

Contents

  • Explains the intentional exit-code-0 behaviour.
  • Shows how to capture the output and grep for the failure marker to fail explicitly (shell + GitHub Actions snippets).
  • Documents the common Missing Authentication Token pitfall: it's an API Gateway unknown route response, usually caused by putting /v2 in --base-url (ts-scan appends /v2/core/... itself).

Changes

  • New page docs/uc04-failOnUploadFailure.md
  • Nav entry in mkdocs.yml

🤖 Generated with Claude Code

ts-scan upload intentionally exits 0 on a failed transfer so a transient
platform issue does not break CI/CD. Document how to react to a failed
transfer when a missing SBOM is a real compliance gap, including the
base-url pitfall behind "Missing Authentication Token".
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