When attempting to resolve a remote dependency for templates, the pipeline builder searches the expanded remote archive for the specified folder to load. The search looks at all directories in the directory where the archive was expanded including the reference to the parent directory: '..'.
Because of this behavior, the if the current working directory where the Jenkins Pipeline Builder is run contains a folder with the same name as the desired folder, then this folder is incorrectly targeted for loading.
Scenario:
Project file specifies loading remote templates and the specified folder name to load matches that of an other folder in the current working directory.
Expected behavior:
JPB should find and load the specified folder from the remote archive and the template therein.
Current behavior:
JPB find the folder in the current working directory (outside the expanded archive) and attempts to load a template from there.
When attempting to resolve a remote dependency for templates, the pipeline builder searches the expanded remote archive for the specified folder to load. The search looks at all directories in the directory where the archive was expanded including the reference to the parent directory: '
..'.Because of this behavior, the if the current working directory where the Jenkins Pipeline Builder is run contains a folder with the same name as the desired folder, then this folder is incorrectly targeted for loading.
Scenario: Project file specifies loading remote templates and the specified folder name to load matches that of an other folder in the current working directory.
Expected behavior: JPB should find and load the specified folder from the remote archive and the template therein.
Current behavior: JPB find the folder in the current working directory (outside the expanded archive) and attempts to load a template from there.