Fixed the path to folder destination of download with JDK file #15314
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
added 3 commits
September 22, 2021 09:44
|
Do we have test coverage for this? |
anatolybolshakov
approved these changes
Sep 23, 2021
added 2 commits
September 23, 2021 19:47
alexander-smolyakov
approved these changes
Sep 28, 2021
|
/azp run |
|
Azure Pipelines failed to run 4 pipeline(s). |
… of https://github.com/microsoft/azure-pipelines-tasks into users/v-aopareva/bug14214_fix_path_java_tool_installer
|
/azp run |
|
Azure Pipelines failed to run 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 4 pipeline(s). |
added 5 commits
October 6, 2021 18:18
… of https://github.com/microsoft/azure-pipelines-tasks into users/v-aopareva/bug14214_fix_path_java_tool_installer
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.
Task name: JavaToolInstallerV0
Description: fix the path to folder destination of download with JDK file
In past - if we have on the Azure Blob storage path to the JDK like:
azureCommonVirtualFile: 'foldername/nameJDK.tar.gz'and destination
jdkDestinationDirectory: './destination'the task failed with error:
##[error]ENOENT: no such file or directory, stat '/azagent/_work/1/destination/foldername/nameJDK.tar.gz''
Now we can use any subdirectory for JDK - always we will use the right directory for unpacking, like /azagent/_work/1/destination/nameJDK.tar.gz
Tested for structures:
folder1/nameJDK
folder1/nameJDK
folder2/nameJDK
folder1/nameJDK
folder2/level2/nameJDK
nameJDK
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) #14214
Checklist: