Skip to content

Update CI to report build failure as warning - #50997

Merged
Weidong Xu (weidongxu-microsoft) merged 1 commit into
mainfrom
kaylieee/report-build-warning
Oct 28, 2026
Merged

Weidong Xu (weidongxu-microsoft) merged 1 commit into
mainfrom
kaylieee/report-build-warning

Conversation

@kaylieee

Copy link
Copy Markdown
Member

Update CI for auto spec PR runs to report successful generation and failed build as warning instead of failure

Test PR run: Azure/azure-rest-api-specs#47663
CI Job: https://dev.azure.com/azure-sdk/public/_build/results?buildId=7005637&view=results

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
35 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

The scoped status change matches the intended behavior while preserving generation failure reporting and compilation-gated artifacts.

No open issues 🎉

What changed in this PR

Updates Java SDK generation automation so qualifying spec PR runs report successful generation followed by a failed build as a warning rather than a failure.

Changes:

  • Tracks generation and compilation outcomes separately.
  • Reports build failures as warnings when generation succeeds and clean-folder fallback is enabled.
  • Keeps artifact publication conditional on successful compilation.
File Description
eng/​automation/​generate_data.py Separates generation and build status to support conditional warning results.

Review effort: Balanced

@weidongxu-microsoft
Weidong Xu (weidongxu-microsoft) merged commit 589fd71 into main Oct 28, 2026
34 checks passed
@weidongxu-microsoft
Weidong Xu (weidongxu-microsoft) deleted the kaylieee/report-build-warning branch October 28, 2026 03:32
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.

3 participants