Spike :: Conditionally run test jobs based on changed files
In the quest to reduce the time from committing to deploy we should consider whether we can exclude some test jobs based on the changed files.
We need to identify:
- a mechanism to identify which file changes should trigger which test jobs
- a mechanism to exclude test jobs from executing based on point 1
We need to be careful that we don't run into a scenario where we exclude a test job based on the changed files and it introduces a regression to tests not running.
Edited by Jean du Plessis