[JIRA] Commented: (HUDSON-3385) 1.292: m2 job marked unstable by violations is not honored in emails

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-3385) 1.292: m2 job marked unstable by violations is not honored in emails

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139148#action_139148 ]

mindless commented on HUDSON-3385:
----------------------------------

Do you still see this problem in a recent Hudson release?

> 1.292: m2 job marked unstable by violations is not honored in emails
> --------------------------------------------------------------------
>
>                 Key: HUDSON-3385
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-3385
>             Project: Hudson
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: hoodja
>
> Using Hudson 1.292 w/ latest violations plugin.
> Running a native maven job on a multimodule project, one of the violations
> components (CPD in this case) marks the build 'unstable' based on the
> configurable settings. However, at the end of the build, SUCCESS is reported in
> the console log and the "Hudson build is back to stable" email is sent.
> When viewing the build through the web, the build is shown as unstable.
> So (without having any understanding of the system), the internal model of the
> build seems to be correct, but the component which decides to send out the
> email seems to be unaware of the unstable state.
> Please let me know what else I can provide to help debug the issue. My read of
> the release notes of 1.293 and 1.294 seemed like this would not be fixed, but
> I'm happy to try to upgrade first.
> Last few lines of console output (edited for anonimity):
> [INFO]
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] ------------------------------------------------------------------------
> [INFO] XXX :: Core ..................................... SUCCESS [51.005s]
> [INFO] XXX :: Core API ................................. SUCCESS [21.715s]
> [INFO] XXX :: Core Resolution APIs ..................... SUCCESS [4.212s]
> [INFO] XXX :: Core Persistence API ..................... SUCCESS [4.046s]
> [INFO] XXX :: Core Implementation of Resolution APIs ... SUCCESS [11.862s]
> [INFO] XXX :: Core XmlBeans Mappings ................... SUCCESS [20.442s]
> [INFO] XXX :: Core API Reference Implementation ........ SUCCESS [38.734s]
> [INFO] XXX :: Core Distribution ........................ SUCCESS [4.733s]
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 55 seconds
> [INFO] Finished at: Mon Mar 30 10:30:22 CDT 2009
> [INFO] Final Memory: 121M/575M
> [INFO] ------------------------------------------------------------------------
> Sending e-mails to: [hidden email]
> channel stopped
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> [WARNINGS] Parsing warnings in log file...
> [WARNINGS] Found 4 annotations (0 new, 0 high, 4 normal, 0 low)
> [WARNINGS] Don't changing build status, no threshold has been exceeded
> Finished: SUCCESS

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]