Re: trim Jenkins build logs

[Sandor Molnar]

+1

On 2/15/18, 5:02 PM, "Doroszlai, Attila" <adorosz...@apache.org> wrote:

    Hi,
    
    The output of each Ambari build contains almost 20K lines (3.4 MB) for
    the eclipselink-staticweave-maven-plugin (see example below).  I doubt
    anyone ever reads these.
    
    I'd like to propose turning it lower in the pre/post-commit Jenkins
    jobs, to only show warnings or errors.  This can be achieved by
    passing -Del.log=WARN to mvn (on branch-2.5 and above).
    
    Setting it to WARN would leave us with only 6 warnings on trunk, which
    probably nobody noticed, as they are buried among the other 19922
    lines.
    
    * https://builds.apache.org/view/A/view/Ambari/job/Ambari-branch-2.6/
    * 
https://builds.apache.org/view/A/view/Ambari/job/Ambari-Github-PullRequest-Builder/
    * https://builds.apache.org/view/A/view/Ambari/job/Ambari-trunk-Commit/
    
    Thanks.
    
    -Attila
    
    
    [EL Finest]: jpa: 2018-01-19
    14:43:44.659--ServerSession(1245802592)--Thread(Thread[main,5,main])--Begin
    predeploying Persistence Unit ambari-server; session ambari-server;
    state Initial; factoryCount 0
    [EL Finest]: properties: 2018-01-19
    
14:43:44.693--ServerSession(1245802592)--Thread(Thread[main,5,main])--property=eclipselink.weaving.changetracking;
    default value=true
    [EL Finest]: properties: 2018-01-19
    
14:43:44.693--ServerSession(1245802592)--Thread(Thread[main,5,main])--property=eclipselink.weaving.lazy;
    default value=true