| Summary: | windows7tests slave access to /shared | ||
|---|---|---|---|
| Product: | Community | Reporter: | Andrew Niefer <aniefer> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Andrew Niefer
I believe Windows 7 Pro does have NFS tooling, but I've never tried it. Regardless, the Windows slave is not physically wired to access /shared. Can't you pull your results from the Hudson workspace from build.eclipse.org? I tried doing a get from e4Build@build.eclipse.org to (for example) https://hudson.eclipse.org/hudson/job/orion-jstest-windows/ws/N20110407-1624/IE-9.0-testResults.html This failed with a 403, the releng scripts would need to specify username/password for that. Currently it would need to be mine, I don't really like having passwords like this in the releng scripts. We could probably add the e4Build user to the job which would be better than having my personal around there. Alternatively, the job can archive the results I need, resulting in a public url like https://hudson.eclipse.org/hudson/job/orion-jstest-windows/50/artifact/N20110407-1624/IE-9.0-testResults.html The only problem is figuring out what the build job number (/50/ above) is from the build.eclipse.org side. hmm, I'm just noticing the security settings in the job, I can set anonymous to read the workspace and 403 problems go away and I can get from the URL the releng script knows: https://hudson.eclipse.org/hudson/job/orion-jstest-windows/ws/N20110407-1624/IE-9.0-testResults.html So I'm ok now. Since the build 'details' are stored on build (/shared/jobs/orion-jstest-windows/builds) could you use the 'nextBuildNumber' file or most recent file in in the builds dir to 'compute' the right url? -M. (In reply to comment #4) > Since the build 'details' are stored on build > (/shared/jobs/orion-jstest-windows/builds) could you use the 'nextBuildNumber' > file or most recent file in in the builds dir to 'compute' the right url? > > -M. I didn't know these details were here, I can definitely use that 'nextBuildNumber' Andrew, with the information that you have here, do you consider this a reasonable workaround? I'm not sure Matt or I are otherwise mentally ready to give a Windows box more access than the absolute minimum. Yes, comment #4 had what I needed. I can live without the access to /shared. |