Open Radiergummi opened 11 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-releases for triage ⏲️
@HazAT can you have someone on your team take a look at this?
Failed to route for Product Area: Other. Defaulting to @getsentry/open-source for triage ⏲️
Daniel's out of the office, we'll have to revisit this in a month.
@HazAT if I may, I'd like to kindly remind you of this issue?
@Radiergummi (great username btw) is this actually a proper fork? Could we just merge your changes?
great username btw
thank you heh
It's a proper fork, and you probably could actually merge the changes, although I'd advise reviewing it. I haven't touched the pipeline for quite a while now, and your APIs have changed a bit, I think. I'll help if I can, though!
@Radiergummi ok because I couldn't find your link/fork in the fork section of our Repo - can you submit a PR?
Core or SDK?
Core Sentry product
Which part? Which one?
https://bitbucket.org/sentryio/sentry-new-release/src/master/
Description
The BitBucket pipeline to create sentry releases from a BitBucket CI pipeline is heavily outdated, somewhat buggy, and lacking features.
Suggested Solution
A year ago, I created a fork which implements lots of the missing stuff, works well, and actually sees some usage from others. I also mentioned the project in the issues of your pipeline repository on BitBucket, but I can imagine that nobody actually looks there, so I thought I'd go ahead and mention it here.
The fork is available here:
https://bitbucket.org/matchory/sentry-release/src/main/
It would be neat to ~get rid of the maintenance burden~ have this move over into your more responsible hands. If you need any advice or aid with the pipeline, I'll help where I can.