[ 
https://issues.jenkins-ci.org/browse/JENKINS-12602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159767#comment-159767
 ] 

Ulli Hafner commented on JENKINS-12602:
---------------------------------------

Integrated in !http://faktorzehn.org:8081/images/16x16/blue.png! [Jenkins 
Analysis Plug-ins (Compile) 
#411|http://faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20(Compile)/411/]
     [FIXED JENKINS-12602] Don't evaluate build health if no threshold is 
(Revision 7dc673e3064361b361efbc9b71e6c7643dc856e8)

     Result = SUCCESS
                
> Detection of first build seems to be broken
> -------------------------------------------
>
>                 Key: JENKINS-12602
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12602
>             Project: Jenkins
>          Issue Type: Bug
>          Components: tasks-plugin
>            Reporter: Ulli Hafner
>            Assignee: Ulli Hafner
>            Priority: Trivial
>
> 13:24:42  [TASKS] Found 0 files to scan for tasks
> 13:24:42  Found 0 open tasks.
> 13:24:42  [TASKS] File encoding has not been set in pom.xml, using platform 
> encoding UTF-8, i.e. build is platform dependent (see <a 
> href="http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding";>Maven
>  FAQ</a>).
> 13:24:43  [TASKS] Ignore new warnings since this is the first valid build
> 13:24:43  [TASKS] Not changing build status, since no threshold has been 
> exceeded
> 13:24:43  [TASKS] Computing warning deltas based on reference build #23

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to