@mitsuhiko
We are using sentry for production and for our testing environment.
In production we create a new release every time the code changes so here we do not have problems because we do not need to update any artifact.
For our testing environment we have one release for every pull request so all issues are grouped in the same release.
Every time the pull request is updated a new version of the source maps need to be pushed and we need to update the existing source map artifact.

The current api doesn't support update an artifact just create and if the file already exists it fails.
So it would be awesome if you could add a flag to the create file endpoint.

this is how we are using the endpoint:

# Upload the source map
$ curl https://sentry.io/api/0/projects/$ORGANIZATION/$PROJECT/releases/$RELEASE/files/ \
  -X POST \
  -H 'Authorization: Bearer $TOKEN' \
  -F file=@main.jsbundle.map \
  -F name="/main.jsbundle.map"

We could create a new release for each time a pull request change, but this will be unmanageable, for the amount of new releases. also the issues would not be grouped under the same release.

Uh oh!

Uh oh!

Add a flag to override release artifacts #3355

Description

Metadata

Metadata

Assignees

Labels

Fields

Projects

Milestone

Relationships

Development

Issue actions