| Summary: | decouple build and test components of build | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kim Moir <kim.moir> |
| Component: | Releng | Assignee: | Kim Moir <kim.moir> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | akurtakov, Mike_Wilson, overholt, stephan.herrmann |
| Version: | 3.5 | ||
| Target Milestone: | 3.7 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 247332 | ||
|
Description
Kim Moir
*** Bug 247330 has been marked as a duplicate of this bug. *** Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement. Should investigate using the EC2 plugin on the hudson server to investigate running tests in the cloud. I was looking at this problem recently. I think the best approach is 1) Run the regular hudson eclipse build without tests and fingerprint the artifacts. 2) The first build will trigger a subsequent per platform builds to run JUnit tests as a post build step. 3) The parameterized JUnit build will check the sdk.tests portion of eclipsebuilder as well as basebuilder. It will use Ant get to fetch the SDK, and other zips. p2 will be used to fetch the test bundles into a local repo. 4) Run the tests 5) Update build directory to point to JUnit results on hudson machines. For milestone and release builds, the JUnit test results should be copied to the build directory. This is a good post regarding parameterized builds and splitting build and splitting build and test components. http://barnashcode.blogspot.com/2010/07/split-hudson-jobs.html From bug 296290, locations of vms on windows test machine are c:\Program Files\Java\ jre6 jre1.5.0_22 jdk1.5.0_22 jdk1.6.0_20 This has been solved as part of bug 295393. |