[ 
https://issues.apache.org/jira/browse/FINERACT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981323#comment-16981323
 ] 

Michael Vorburger commented on FINERACT-779:
--------------------------------------------

FINERACT-800 picks this up and finishes it.

> Travis CI breaks due to excessive audit logs when adding Spring Boot Actuator
> -----------------------------------------------------------------------------
>
>                 Key: FINERACT-779
>                 URL: https://issues.apache.org/jira/browse/FINERACT-779
>             Project: Apache Fineract
>          Issue Type: Bug
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Major
>             Fix For: 1.4.0
>
>
> similarly to FINERACT-732,
> the Travis CI integration for PRs to Fineract which I recently set up seems 
> to be broken,
> AGAIN?
>  
> Example on [https://github.com/apache/fineract/pull/618]  "The job exceeded 
> the maximum log length, and has been terminated.", again?
> Reminds me FINERACT-732], but seems to be a new issue... did we very recently 
> change something which is causing more extensive logging of ITs - I see A LOT 
> of the following, do we really need to log this at level INFO, or could we 
> just make these DEBUG:
> {noformat}01:21:21.119 [SimpleAsyncTaskExecutor-49243] INFO 
> o.s.b.a.audit.listener.AuditListener - AuditEvent [timestamp=Sat Feb 23 
> 01:21:21 IST 2019, principal=mifos, type=AUTHENTICATION_SUCCESS, 
> data=\{details=org.springframework.security.web.authentication.WebAuthenticationDetails@957e:
>  RemoteIpAddress: 127.0.0.1; SessionId: null}] 01:21:21.124 
> [http-bio-8443-exec-87] INFO o.a.f.i.s.f.TenantAwareBasicAuthenticationFilter 
> - 
> \{"startTime":1550865081114,"totalTime":10,"method":"GET","url":"https://localhost:8443/fineract-provider/api/v1/recurringdepositaccounts/142","parameters":{"tenantIdentifier":["default"]}}
>  {noformat}
> Or perhaps Travis CI (suddenly?) got more strict?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to