Avoid redundant db-testing pipeline builds
Why this issue?
To address the duplicate pipeline jobs getting triggered for the same commit and fixing it.
Examples
Desired outcome
-
If a new job is re-triggered after it fails, it should start a new pipeline -
If a new job has changes to helpers or background migrations since the last run, it should start a new pipeline -
If the migrations, helpers, and background migrations are the same, the job should not start a new pipeline
Edited by Alex Ives