CCM-981 #457
Merged
CCM-981 #457
Conversation
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
Periodically this step in the pipeline will fail - this requires APIM producers to have to press the retry button in order to get a successful build. The manual retry process is normally successful after only 1 retry. The error thrown here is a 401 - this makes me believe that token created within the `Get Apigee Access Token` step was failing. `jq` is being used to extract the .access_token path from the JSON response - previously it was not returning an error code when the payload did not contain the path. This updates the `jq` call with the `-e` flag which will error when `.access_token` is not within the response. An automated retry mechanism for when this error occurs has been added to this step. It uses the built in azure devops retryCountOnTaskFailure which will automatically back off on subsequent failures. See https://learn.microsoft.com/en-us/azure/devops/pipelines/process/tasks?view=azure-devops&tabs=yaml#number-of-retries-if-task-failed
PhilipSkinner
force-pushed
the
CCM-981-proxy-deployment-retries
branch
from
cfb7e35 to
8cfd805
Compare
Author
|
Updated the PR with where I believe the issue is occuring - within the |
Author
|
I updated this script to look for an invalid path within the JSON response -
|
acarriedev
approved these changes
Sep 18, 2023
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.
Summary
Periodically this step in the pipeline will fail - this requires APIM producers to have to press the retry button in order to get a successful build. The manual retry process is normally successful after only 1 retry.
The error thrown here is a 401 - this makes me believe that token created within the
Get Apigee Access Tokenstep was failing.jqis being used to extract the.access_tokenpath from the JSON response - previously it was not returning an error code when the payload did not contain the path. This updates thejqcall with the-eflag which will error when.access_tokenis not within the response.An automated retry mechanism for when this error occurs has been added to this step. It uses the built in azure devops retryCountOnTaskFailure which will automatically back off on subsequent failures.
See https://learn.microsoft.com/en-us/azure/devops/pipelines/process/tasks?view=azure-devops&tabs=yaml#number-of-retries-if-task-failed