Explain error when downloading Node Alpine ARM64 #4822
Merged
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
DenisRumyantsev
force-pushed
the
users/DenisRumyantsev/explain-error-node-alpine-arm64-not-found
branch
from
7ac08b3
to
cf09be3
Compare
DenisRumyantsev
force-pushed
the
users/DenisRumyantsev/explain-error-node-alpine-arm64-not-found
branch
from
cf09be3
to
eec22ed
Compare
DenisRumyantsev
force-pushed
the
users/DenisRumyantsev/explain-error-node-alpine-arm64-not-found
branch
from
eec22ed
to
f020f9c
Compare
DergachevE
approved these changes
May 30, 2024
vmapetr
approved these changes
May 30, 2024
kirill-ivlev
approved these changes
May 31, 2024
…lpine-arm64-not-found
…lpine-arm64-not-found
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…lpine-arm64-not-found
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.
Description: Add a message which explains a possible error that can appear during the agent release pipeline run after Node version update.
Error example: