chore(codebuild): add region constraints and fix fleet deletion timeouts in integ tests

[aemada-aws]

Issue # (if applicable)

Closes #.

Reason for this change

Several CodeBuild integration tests were failing across multiple error categories:

1. Unrecognized resource types: [AWS::CodeBuild::Fleet] — AWS::CodeBuild::Fleet CloudFormation resource is not available in all regions
2. LambdaCompute feature is not supported in region — Lambda compute mode is only available in 10 regions
3. Region X is not supported for WINDOWS_SERVER_2022_CONTAINER — Windows Server 2022 environment type is only available in 8 regions
4. Fleet deletion timeout (NotStabilized) — AWS::CodeBuild::Fleet resource deletion takes ~40 minutes, exceeding the CFN resource handler's ~21 minute stabilization timeout
5. macOS fleet build assertion timeout — macOS dedicated host provisioning takes 20-30+ minutes, exceeding the assertion framework's timeout limits

Description of changes

Region constraints (all 11 tests):
Added regions property to IntegTest constructors, with per-test comments explaining the specific feature constraint:

• Fleet tests: AWS::CodeBuild::Fleet not available in all regions
• Lambda tests: ARM_LAMBDA_CONTAINER / LINUX_LAMBDA_CONTAINER not available in all regions
• Windows fleet tests: WINDOWS_SERVER_2022_CONTAINER not available in all regions
• macOS fleet tests: MAC_ARM only available in 5 regions
• Windows image test: WINDOWS_SERVER_2022_CONTAINER not available in all regions

Fleet deletion workaround (8 fleet tests):
Added cdkCommandOptions.destroy.expectError = true because AWS::CodeBuild::Fleet deletion consistently takes ~40 minutes, exceeding the CFN resource handler's ~21 minute stabilization timeout (verified via CloudFormation events across multiple regions).

Assertion timeout increases (6 fleet tests):
Increased waitForAssertions totalTimeout from 5 to 15 minutes for fleet tests to account for fleet instance provisioning time before builds can execute.

Hardcoded name removal (5 fleet tests):
Removed hardcoded fleetName properties ('MyFleet', 'MacOsFleet14', 'MacOsFleet15') to avoid NAME_COLLISION on re-runs.

macOS test simplification (2 tests):
Removed startBuild/batchGetBuilds assertions from macOS fleet tests since macOS dedicated host provisioning exceeds the assertion framework's timeout limits. The listFleets assertion is retained to verify fleet creation. Build execution on fleets is already validated by the Linux fleet tests.

Describe any new or updated permissions being added

N/A — no permission changes.

Description of how you validated changes

All 11 tests validated via yarn integ with --force --update-on-failed across 5 parallel regions: us-east-1, us-east-2, us-west-2, ap-southeast-2, eu-central-1.

Tests:    11 passed, 11 total

Validation command:

yarn integ \
  test/aws-codebuild/test/integ.project-fleet.js \
  test/aws-codebuild/test/integ.project-fleet-attribute-based-compute.js \
  test/aws-codebuild/test/integ.project-fleet-custom-instance-type.js \
  test/aws-codebuild/test/integ.project-fleet-overflow-behavior.js \
  test/aws-codebuild/test/integ.project-windows-2019-fleet.js \
  test/aws-codebuild/test/integ.project-windows-2022-fleet.js \
  test/aws-codebuild/test/integ.project-macos-fleet-base14.js \
  test/aws-codebuild/test/integ.project-macos-fleet-base15.js \
  test/aws-codebuild/test/integ.project-linux-arm-lambda-image.lit.js \
  test/aws-codebuild/test/integ.project-linux-lambda-image.lit.js \
  test/aws-codebuild/test/integ.project-windows-image.js \
  --disable-update-workflow --update-on-failed --force \
  --parallel-regions us-east-1 us-east-2 us-west-2 ap-southeast-2 eu-central-1

Not fixed (external dependency):

• integ.github-org-webhook and integ.github-webhook-batch require a pre-configured GitHub access token in the AWS account — cannot be fixed in test code.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results	408 ran	408 passed

Test	Result
No test annotations available

• View Security Guardian Results

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results with resolved templates	408 ran	408 passed

Test	Result
No test annotations available

• View Security Guardian Results with resolved templates

[Abogical]

We got the following error when trying to deploy via the workflow:

Running test /codebuild/output/src3758018834/src/actions-runner/_work/aws-cdk/aws-cdk/packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-fleet.js in us-west-2
  ERROR      /codebuild/output/src3758018834/src/actions-runner/_work/aws-cdk/aws-cdk/packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-fleet.js (undefined/us-west-2) 0.001s
      Error during integration test: ManifestLoadingError: Failed to load integ manifest 'packages/@aws-cdk-testing/framework-integ/test/aws-codebuild/test/integ.project-fleet.js.snapshot/integ.json': Cloud assembly schema version mismatch: Maximum schema version supported is 50.x.x, but found 52.0.0. You need at least CLI version 2.1107.0 to read this manifest.
      Cause: Error: Cloud assembly schema version mismatch: Maximum schema version supported is 50.x.x, but found 52.0.0. You need at least CLI version 2.1107.0 to read this manifest.

Can this be fixed?

[aemada-aws]

@Abogical done, it just needed a merge from main for the latest cdk cli. The issue is now the account is suspended by Codebuild 🫠

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-03-13 12:50 UTC · Rule: default-squash
• ✅ Checks passed · in-place
• ✅ Merged — 2026-03-13 13:32 UTC · at 795edc36a698210dc0c5ac99bd7c63e8408ab32a

This pull request spent 42 minutes 45 seconds in the queue, including 42 minutes 32 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore(codebuild): add region constraints and fix fleet deletion timeouts in integ tests #36956
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • chore(codebuild): add region constraints and fix fleet deletion timeouts in integ tests #36956
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.