-
Bug
-
Resolution: Unresolved
-
Blocker
-
PRODUCTION
Hi,
We are working on a Production issue to measure the benchmarking our system latency and other factors.
When i try to configure the benchmark-evaluator plugin it throws me an error, that fileset is not reachable.
i have created a simple git project "test-plugin", with report/abc.csv
and when i configure this project, i do a "git checkout <myreponame>" at workspace root.
meaning, it should be at <WORKPACE>/test-plugin.
my filesetpath will be : "test-plugin/report/abc.csv"
but this does not work on our jenkins cluster.
Tried both ways declarative and UI. both throws the same error to check the filesetpath.
Regards
Ram
[JENKINS-70628] Fileset not accessible for plugin with relativepath to workspace
Ram
created issue -
| Epic Link | Original: JENKINS-49379 [ 188252 ] |
| Sprint | Original: Declarative backlog [ 621 ] |
| Comment |
[ It appears that root ('/') is the current working directory, and a relative path is resolved relative to it: It remains functional even after I remove the leading slash from an absolute route. https://gorillatag.io/
] |
| Comment | [ If you're encountering a "Fileset not accessible for plugin with relative path to workspace" issue, it likely indicates that the plugin or tool you're using cannot access the specified fileset due to a relative path problem within your workspace. Check and ensure that the relative paths are correctly configured, and the necessary files are accessible from the plugin. Verify the plugin's documentation or seek assistance from the tool's support/community for specific troubleshooting steps related to your workspace setup. [Cat Needs Best|https://www.catneedsbest.com/] ] |
| Comment | [ I would want to express my gratitude for this post and inform you that I will be taking a short hiatus. I much appreciate the effort you put into writing this; I found it extremely beneficial. https://backyardbaseball.io/ ] |
