Track only important "Deployment::StatusSyncError" exceptions
Description
We started tracking invalid status transition on Deployment model. Surprisingly, we observe many invalid cases in our system. For example,
- https://sentry.gitlab.net/gitlab/gitlabcom/issues/2859096/?query=%22Deployment%3A%3AStatusSyncError%22
- https://sentry.gitlab.net/gitlab/gitlabcom/issues/2858414/?query=%22Deployment%3A%3AStatusSyncError%22
- https://sentry.gitlab.net/gitlab/gitlabcom/issues/2858524/?query=%22Deployment%3A%3AStatusSyncError%22
While it's meaningful to track these invalid cases and fix the root causes, it's also annoying to tracking all of the exceptions as some of them are not really important.
Proposal
Reduce the exception messages on Sentry
Sentry
https://sentry.gitlab.net/gitlab/gitlabcom/issues/2858524/?referrer=gitlab_plugin
Deployment::StatusSyncError: Cannot transition status via :run from :skipped (Reason(s): Status cannot transition via "run")
Edited by Shinya Maeda