Skip to content

ci: report AmplifyCLI-PR-Testing batch status to GitHub from cloud-pr - #14965

Closed
sarayev wants to merge 1 commit into
devfrom
ci/cloud-pr-report-batch-status
Closed

ci: report AmplifyCLI-PR-Testing batch status to GitHub from cloud-pr#14965
sarayev wants to merge 1 commit into
devfrom
ci/cloud-pr-report-batch-status

Conversation

@sarayev

@sarayev sarayev commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Description of changes

scripts/cloud-pr.sh starts the AmplifyCLI-PR-Testing CodeBuild batch manually via aws codebuild start-build-batch, but did not pass --report-build-batch-status-override. Because this project has no GitHub webhook, CodeBuild never posted the required commit-status AWS CodeBuild BuildBatch us-east-1 (AmplifyCLI-PR-Testing) back to the PR head SHA. The required check therefore stayed stuck on "Expected", blocking merges even when the manual batch actually succeeded.

This adds --report-build-batch-status-override to the start-build-batch invocation so CodeBuild posts the commit status back to the PR head commit when the batch completes, allowing the required check to resolve. The CodeBuild project source already has reportBuildStatus enabled, so only the override flag is required.

Issue #, if available

N/A

Description of how you validated changes

  • bash -n scripts/cloud-pr.sh passes (script parses).
  • Change is limited to adding a single CLI flag plus an explanatory comment; no batch was triggered.

Checklist

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
  • Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

cloud-pr.sh started the PR-Testing batch without
--report-build-batch-status-override, so the required GitHub
commit-status "AWS CodeBuild BuildBatch us-east-1
(AmplifyCLI-PR-Testing)" was never posted to the PR head commit.
As a result the required check stayed stuck on "Expected" and
blocked merges even when the manual batch actually succeeded.

Adding --report-build-batch-status-override to the
start-build-batch invocation makes CodeBuild post the commit
status back to the PR head SHA when the batch completes, so the
required check resolves correctly. The project source already has
reportBuildStatus enabled, so only the override flag is needed.
---
Prompt: Make cloud-pr report the AmplifyCLI-PR-Testing batch
status back to the GitHub PR so the required check no longer stays
stuck on Expected.
@sarayev

sarayev commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Closing — the --report-build-batch-status-override change does not reliably make CodeBuild post the required commit-status for these runs. Not pursuing this approach; the status will be handled separately.

@sarayev sarayev closed this Jul 27, 2026
@sarayev
sarayev deleted the ci/cloud-pr-report-batch-status branch July 27, 2026 11:20
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