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
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