This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Module that failed not reported properly | ||
|---|---|---|---|
| Product: | connecteddeveloper | Reporter: | jmborer <jmborer> |
| Component: | Hudson | Assignee: | Jesse Glick <jglick> |
| Status: | CLOSED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | Hudson plugin | ||
Works for me when I connect to http://hudson.glassfish.org/ and browse to http://hudson.glassfish.org/job/Atmosphere/39/ in which atmosphere-jersey had test failures. In NetBeans, Services > Hudson Builders > Glassfish > Atmosphere > #39 > atmosphere-jersey is shown in yellow. This works because http://hudson.glassfish.org/job/Atmosphere/39/api/xml?xpath=/*/*[name%28%29=%27result%27%20or%20name%28%29=%27building%27]&wrapper=root produces <root><building>false</building><result>UNSTABLE</result></root> as expected. So what version of Hudson are you using, and what does the corresponding URL on your server produce? Hmm. Strange now it works. The only thing I changed in the confs of my projects is that only the artifacts are not kept after a week and no longer all the reporting stuff. I use Hudson 1.364. Maybe we could close the bug for now and reopen it if it comes back. Yes just reopen if it happens again; you should be able to diagnose whether the problem is in Hudson or NetBeans by checking the URL pattern I gave. |
Created attachment 100564 [details] Hudson plugin When a module has some errors during the units tests, the build appears as a yellow dot in the services tab under the Hudson node. However when you expend the yellow node, you don't see which module(s) has(ve) failed as shown in the screenshot: all are blue. The module "inch-common-positions" is the one that failed and should be yellow.