Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

resources: Release sequenced resources in parallel. #7991

Merged
merged 3 commits into from
Nov 18, 2020

Conversation

ghost
Copy link

@ghost ghost commented Nov 17, 2020

This isn't used much, but has been bothering me for a while. While we acquire the resources in parallel, we used to release them sequentially. This reimplements sequence so they're released all at once.

Pull Request Checklist

  • Read and understand the contribution guidelines
  • Include appropriate tests
  • Set a descriptive title and thorough description
  • Add a reference to the issue this PR will solve, if appropriate
  • Include changelog additions in one or more commit message bodies between the CHANGELOG_BEGIN and CHANGELOG_END tags
  • Normal production system change, include purpose of change in description

NOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with /AzurePipelines run to
trigger the build.

This isn't used much, but has been bothering me for a while. While we
acquire the resources in parallel, we used to release them sequentially.
This reimplements `sequence` so they're released all at once.

CHANGELOG_BEGIN
CHANGELOG_END
@ghost ghost requested a review from stefanobaghino-da as a code owner November 17, 2020 16:31
@ghost ghost added the automerge label Nov 18, 2020
@mergify mergify bot merged commit 87eee30 into master Nov 18, 2020
@mergify mergify bot deleted the samir/libs-scala/resources/parallel-release-sequence branch November 18, 2020 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants