Open vgropp opened 2 years ago
Thanks for reporting this @vgropp!
You can disable the new feature by setting the successComment
option to false
.
Other than that I think it would make sense to add proper handling of such cases to this plugin.
@vgropp Have you seen this behavior recently? In https://github.com/semantic-release/gitlab/pull/728 we learned that the underlying HTTP library does actually have a quite powerful retry logic. I'd like to understand why this is not enough in your case. 🙇
We are running into the gitlab API limit on some projects when multiple semantic-releases are running at the same time from share IPs.
As far as I understand the code https://github.com/semantic-release/gitlab/blob/3051799160efc127585d30a4ef776ccf34185fee/lib/success.js#L72 for very Commit the script is looking for a MR, with those MR the script is searching for an resolved issue. So there will be at least commits * MR Requests. As we do not use gitlab issues (but like the MR comment), what about a configuration to disable the Issue Comments and hence those requests? This will limit the requests to count of commits.
Another Option would be rate limiting the requests, but that seems like a lot more work but more sustainable solution.