getsentry / getsentry/sentry

Perforce changelist association with release

Open
#115,985 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Product Area: Releases Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

What are you trying to accomplish?

I have a self-hosted instance with perforce integration enabled. (Thank you very much for adding this integration.)
In that instance, I have an Unreal engine project.
I have a Horde build system that creates a sentry release for each precompiled binaries release.
I now want the horde build to associate perforce commits with my release, but I can't figure out how it works.

How are you getting stuck?

I use the cli to associate a P4 changelist with the release. Here is my command : .\sentry-cli-Windows-x86_64.exe releases set-commits -c //MyRepo@12345 MyReleaseName.

When I go to the web interface for the release, the associated commits list now contains all commits for which the CL is >= to the linked CL.
Reading the documentation, I understood that it should associate all commits from the previous release, or at maximum 20, but it is not what I see.
I also tried to specify a CL range of 1 element, in the form 1234..1234 to try to pinpoint only one CL, but this time the CL list contains all commits for which the CL is > to the linked CL.

What did I miss ?
How can I associate only one CL to the release, or all CLs since the previous release ?

Where in the product are you?

Releases

Link

No response

DSN

No response

Version

26.4.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the sentry-cli releases set-commits entry point and its documentation, using the reported Perforce commands with a single changelist and a range. Compare the resulting release commit list in the web interface with the documented previous-release behavior. Done means the command associates only the requested changelist or the commits since the previous release.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.