Don't track MR deployment more than once for the same environment
What does this MR do?
It intoduces MergeRequest.not_deployed_to(env) scope that allows filtering MRs that are not deployed on a given environment(s)
With that new scope, we don't track MR deployment more than once for the same environment.
When a MR is already deployed on a given environment, i.e. it was cherry-picked, it should not be linked again on the next deployments.
Related to #199256 (closed)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry - [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team