-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stop running cdk tests and linting on every push #2546
Conversation
Deploy build 9377 of
|
Deploy build 9610 of
|
Deploy build 9610 of
|
Deploy build 9610 of
|
For me it was the opposite. I was working with CDK and I lost so much time waiting for the CI to fail in GitHub. So I'd say, we can improve it by running CDK tests only if files inside the CDK folder have changed? Also suggested by @andrewHEguardian & @rupertbates |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for bringing this up - good improvement!
I was working on another project recently and noticed the pushes were really quick. I noticed they take around 20s on this project even with trivial changes. After looking into why they are so slow, it seems like we are running CDK linting and tests on every push.
This PR changes it so it only runs when you change cdk/* so otherwise push finishes before I even click away (1-2 seconds).
Script courtesy of @AndreaDiotallevi via AI!
Original PR adding the check is here #2199