feat: Support sequential-calls manifest field that disables concurrency when creating multiple pull requests or releases#1401
Merged
gcf-merge-on-green[bot] merged 1 commit intogoogleapis:mainfrom Apr 20, 2022
Conversation
…cy when creating multiple pull requests or releases
dazuma
force-pushed
the
pr/sequential-calls
branch
from
f2dd7ab to
657a7ca
Compare
chingor13
approved these changes
Apr 20, 2022
Contributor
|
I may open a refactor PR to try to test this, but let's try to unblock you. |
chingor13
added
the
automerge
gcf-merge-on-green
Bot
removed
the
automerge
gcf-merge-on-green Bot
pushed a commit
that referenced
this pull request
Apr 20, 2022
🤖 I have created a release *beep* *boop* --- ## [13.14.0](v13.13.0...v13.14.0) (2022-04-20) ### Features * Support sequential-calls manifest field that disables concurrency when creating multiple pull requests or releases ([#1401](#1401)) ([50f5c99](50f5c99)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running release-please on the google-cloud-ruby manifest, we're running afoul of secondary rate limits. Currently release-please runs pull request creation concurrently, and in this case, it was trying to open 33 pull requests at once which seemed to be too much. So we're introducing an option to run them sequentially using blocking calls.
This was added to the manifest config rather than the CLI options, because it seems to be a scaling-related knob that should be set per repository, rather than something that depends on how release-please is invoked.
I honestly do not know how to write a test for this. I tested manually both the sequential and concurrent cases to make sure the functionality was still correct, but I'm not sure how to test whether something happened concurrently or not.