Community
Participate
Working Groups
I'd like a new Hudson job to run Windows tests for 4.2. I'd like to mirror the approach that the Orion team has used to run their windows tests where they use JSON to invoke the tests and a token for authentication to Hudson. Previously, the (Eclipse SDK) used the approach that we had a Hudson job to run the build, which if successful, invoked several test jobs (chained build). However, this was problematic because often network timeouts caused the tests jobs to fail or if one suite caused the tests to fail, we would have to restart the entire suite. So the new approach I'm going to take is to invoke the build from cron on build.eclipse.org but use JSON to invoke the tests and copy the results. This also allows us to update the git repos with tags because the job can be run as someone with commit rights. You can copy this job for reference but give me rights on it. Please call it JUnit-win2 https://hudson.eclipse.org/hudson/job/orion-jstest-windows/ Also, do I need a new HUDSON_TOKEN separate from the one used in the Orion tests?
OK I"ve created the job. To me the tokens look to be pre-defined(click on the ? for a list) by Hudson. -M.
When I try to look at the job, it says "This job is currently disabled". Also, could you please add this job to the Eclipse and Equinox category.
So I have permissions to enable it, never mind about that :-)
Ok, done. -M.
