cli: pre-release integration test strategy for downstream tools (e.g. Amplify)

aws / aws-cdk

The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

https://aws.amazon.com/cdk

Apache License 2.0

11.68k stars 3.93k forks source link

cli: pre-release integration test strategy for downstream tools (e.g. Amplify) #31932

Open mrgrain opened 2 weeks ago

mrgrain commented 2 weeks ago

Today, any tools depending on the AWS CDK are forced to wait for a CDK release before they can execute their test suites against the latest version of the CDK. This is bad, because a change in the CDK might unintentionally break the other tool. Instead we should establish a pattern to test against pre-builds (nightlies) from main.

Primary concern will be for 1st party tools, however this could be extended to 2nd and 3rd party tooling as well.

mrgrain commented 2 weeks ago

Partially implemented by https://github.com/aws/aws-cdk/pull/31921

iliapolo commented 1 week ago

These types of test introduce the chance of bug in a downstream tool to cause delays in our release. We should have a mechanism to skip a integ test to free up a release, we want a fast mechanism that still requires 2 person review.