Dmp 4658 armrpo add max retry logic #2492
Closed
Conversation
This file contains 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
karen-hedges
requested review from
davet1985,
jackmaloney,
hemantasharma1129,
cpareek,
jyothi-balla and
varun-vijayagopal
and removed request for
a team
karen-hedges
force-pushed
the
DMP-4658-ARMRPOAddMaxRetryLogic
branch
5 times, most recently
from
6e62acc to
b4c329b
Compare
Started to add batchsize to ArmRpoPolling automated task
Added more tests
Added more tests
Added more tests
karen-hedges
force-pushed
the
DMP-4658-ARMRPOAddMaxRetryLogic
branch
from
b4c329b to
54a3190
Compare
Added more tests
hmcts-jenkins-cnp
bot
added
ns:darts-modernisation
prd:darts
rel:darts-api-pr-2492
labels
|
closing in favour of Dmp 4667 which was branched off of this PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DMP-4658
Change description
Added max retry logic for RPO polling
Does this PR introduce a breaking change? (check one with "x")