chore(cdk): increase timeout for all bootstrapping integ tests (#14819)

In a previous commit - 8395d9d - the timeout for a single test was increased to 1 hour since it was noticed to fail consistently. Since then, other tests have also failed intermittently due to CloudFormation actions taking longer than expected in some regions. Increase the timeout for all tests to 1 hour when executing in CodeBuild. To keep the dev-test cycle reasonable, maintain a 10 minute timeout when developing outside of CodeBuild.
aws · skinny85 · May 25, 2021 · Mar 29, 2021 · Mar 29, 2021 · Apr 29, 2021
commit fc91fa84b6baf1d0a4d6e94e754b356e2274f4eb
diff --git a/packages/aws-cdk/test/integ/cli/bootstrapping.integtest.ts b/packages/aws-cdk/test/integ/cli/bootstrapping.integtest.ts
@@ -3,7 +3,11 @@ import * as path from 'path';
 import { randomString, withDefaultFixture } from '../helpers/cdk';
 import { integTest } from '../helpers/test-helpers';
 
-jest.setTimeout(600_000);
+const timeout = process.env.CODEBUILD_BUILD_ID ? // if the process is running in CodeBuild
+  3_600_000 : // 1 hour
+  600_000; // 10 minutes
+jest.setTimeout(timeout);
+process.stdout.write(`bootstrapping.integtest.ts: Setting jest time out to ${timeout} ms`);
 
 integTest('can bootstrap without execution', withDefaultFixture(async (fixture) => {
   const bootstrapStackName = fixture.bootstrapStackName;
@@ -54,8 +58,7 @@ integTest('upgrade legacy bootstrap stack to new bootstrap stack while in use',
       '--force',
     ],
   });
-}), 3_600_000, // Observed in eu-west-2 that CF update takes over 10 minutes for this test.
-);
+}));
 
 integTest('can and deploy if omitting execution policies', withDefaultFixture(async (fixture) => {
   const bootstrapStackName = fixture.bootstrapStackName;