I have this problem too. We have configured our pipeline to allow manual deploy to the dev environment from any branch. Now every historical pipeline in all of our projects is changing state from “manual action” to “failed” with this reason:
The deployment job is older than the previously succeeded deployment job, and therefore cannot be run
When I merge an MR, every pipeline related to that branch for which I chose not to do the dev deploy is marked as failed. Please make these emails stop!
Similar to our manual dev deploy, we also have a manual step for promoting a build to production. We do not need a failure notification for every build which is not promoted to production.
We deploy multiple to development/staging environments before production, and its set as a “manual” step, but some times we deploy to development a few times before eventually going to production
we’re getting spammed for every repo that we have deployed…