I was hoping to reduce our CI time and hence used ...
# general
r
I was hoping to reduce our CI time and hence used the
changed-since=main
when running test. But then this messes up with our coverage threshold and hence the CI fails. Is there any solution for this?
1
w
Have you reviewed https://www.pantsbuild.org/docs/using-pants-in-ci Also, are you using the
transitive
check as well? Is there any way you could leverage test memoization in CI?
1
b
I think test caching/memoization is the way to go. Feel free to elaborate on specific pain points w.r.t. timing in your CI pipeline
👍 1
r
yeah ideally we would like to use caching. But it’s a bit of an issue with aws cdk codepipeline. It’s not supported out of the box and they have an open issue. In the meantime, I thought why not try this. EDIT: It looks like the issue has been fixed in newer version of. So I guess I should abandon this route.