chore(ci): Only run CI tests when related files changed

[mydea]

This PR updates the build to only run the "special" CI test jobs when the respective packages have actually changed.

This is done using https://github.com/getsentry/paths-filter with a simple list of directories to watch. We can use the handy shared functionality to avoid duplicating the "global" dependencies.

Note that we do need to keep the internal dependencies in sync (e.g. if nextjs starts to depend on another internal package, we need to add it), but IMHO that is acceptable.

This is how that looks:

Replaces #6067

[Lms24]

I like the idea overall. This whole conditional test execution topic heavily reminds me of the academic "test case/suite selection" problem which TLDR boils down to finding a trade-off between fault detection capability (FDC) vs. test execution time. I think though that our particular case is a milder version of the problem as we can specify the dependencies pretty well and we're only making the decision on a package-level. So this doesn't make me too concerned about an overall loss in FDC

However, I think that the "we have to maintain this list" aspect is something we shouldn't underestimate and I'm thinking of two things we could do here:

• Note that this is a required pre-release step in our SDK release checklist in Notion
• Create a "package creation" checklist that contains this as a required step (this would probably be handy overall)

WDYT, does this sound reasonable?

We just all need to be aware that this exists and we need to take care of it.

[mydea]

I like the idea overall. This whole conditional test execution topic heavily reminds me of the academic "test case/suite selection" problem which TLDR boils down to finding a trade-off between fault detection capability (FDC) vs. test execution time. I think though that our particular case is a milder version of the problem as we can specify the dependencies pretty well and we're only making the decision on a package-level. So this doesn't make me too concerned about an overall loss in FDC

However, I think that the "we have to maintain this list" aspect is something we shouldn't underestimate and I'm thinking of two things we could do here:

• Note that this is a required pre-release step in our SDK release checklist in Notion
• Create a "package creation" checklist that contains this as a required step (this would probably be handy overall)

WDYT, does this sound reasonable?

We just all need to be aware that this exists and we need to take care of it.

Yeah, absolutely true!

I'd also say that in our case it is a fine tradeoff to make, as new packages are added rarely. I think adding it to checklists should be a good step to ensure we don't forget about this! 👍

[Lms24]

I vote we merge this in once the integrations entry is adjusted. Just had two consecutive Ember test flakes in the morning when releasing.

[AbhiPrasad]

Just to sanity check - does this mean we don't run these tests on master or on release branches also? We should make sure we are only skipping tests for PRs.

[mydea]

Just to sanity check - does this mean we don't run these tests on master or on release branches also? We should make sure we are only skipping tests for PRs.

Good point!
Regarding release, I will add CHANGELOG.md to the common files, so all tests will always run when that changes - does that sound reasonable? I think that should cover the release branches?

And I'll do some testing to make sure it only applies to PR runs, not any other runs! 👍