Associating large amounts of commits to a release


Our current VSC provider is unsupported which means we’re currently creating releases & associating commit data manually via the API at deploy time.

We’ve run into a couple of issues with rarely deployed envs that could have 1000+ commits including x000 file changes. Posting that much data to sentry in one go often results in nginx timeouts, OOM exceptions and DB errors.

All of these can be fixed, but are obviously undesirable as it forces us to have to redeploy without commit data, try again until it succeeds or have someone spend time tweaking configuration.

From our testing it looks like it’s impossible to update an existing releases’s commits without removing any that were already there.

Is there an alternative solution that we haven’t seen or thought of?