Only run tests related to the component if possible

[atoulme]

Component(s)

No response

Describe the issue you're reporting

The current approach to CI is monolithic and consists in running tests for all receivers, exporters, processors and so on even though most changes are going to apply to a specific component.

I propose that we organize CI to reduce the jobs running based on patterns of change, unless a label "Run all tests" is set. This would only apply to unit tests and leave integration tests, load tests and so forth untouched.

[TylerHelmuth]

This would be great. It would need to be intelligent enough to run any tests for dependent components. If we change something in pkg or internal anything using those dependencies should have their tests run.

[Aneurysm9]

IIRC we tried this once before and got hung up on dependency resolution, though I can't seem to find the related issues/PRs. I believe that pre-dated crosslink, though, and with that tool we should be able to identify modules that depend on a module with changes and ensure that tests in those modules are also run.

While I think it would be good to reduce the scope of PR test runs in this manner, we do need to ensure we're still running the full test suite on merge and probably on a subset of PRs.

[TylerHelmuth]

Definitely on any merge to main and any release prep PR

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.