We recently upgraded our commander test server from 4.1 to 4.2.4 .
The reports that are linked via artifacts directory are not working in default workspace. I can see reports being copied in the expected directory, but the links are not working fine.
It does work on custom workpaces.
I see below error
The agent returned error 404. resolveFile failed with code: [NoSuchWorkspace] message: 'Workspace 'artifacts' does not exist'
xcopy "C:\Build\Report\*.*" "\\commanderserver\workspace\XYZ Build Procedure on XYZ_Pool (4945598)\artifacts\" /e /i /y
ectool setProperty "/myJob/artifactsDirectory" --value "/commander/jobs/4945598" ectool setProperty "/myJob/report-urls/Qunit Report" /commander/jobs/4945598/artifacts/jscoverage.html
Answer by lrochette · Jul 01, 2014 at 01:34 AM
This is a known issue that has been fixed in 4.2.5 that happened to be released this past Monday
So my advice would be to update to this latest version. Here is the way I created my report links
ectool setProperty "/myJob/artifactsDirectory" --value "." ectool setProperty "/myJob/report-urls/Qunit Report" /commander/jobSteps//file.html
That has been working for me local and shared workspaces
How to register second AR to a Commander server which already has 'default' AR? 1 Answer
How do I publish reports to the EC web server? 1 Answer
custom reports 1 Answer
/runProcedure URL - How to pass parameters to the procedure? 1 Answer
restricting resourceSummary report to certain resources 1 Answer
Electric Cloud powers Continuous Delivery, helping organizations developing deliver better software faster by automating and accelerating build, test, and deployment processes at scale. Industry leaders like Qualcomm, SpaceX, Cisco, GE, Gap, and E*TRADE use Electric Cloud solutions to boost DevOps productivity and Agile throughput.