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

ASF GitHub Bot commented on DISPATCH-1363:
------------------------------------------

ganeshmurthy commented on issue #594: DISPATCH-1363 - Move Rat licence check 
from travis builds into GitHub Action
URL: https://github.com/apache/qpid-dispatch/pull/594#issuecomment-543738782
 
 
   @jdanekrh This looks good to me. 
   
   @gemmellr can you please take a quick look at this PR and comment ?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Remove apache rat check from main travis build and move to a sub build 
> -----------------------------------------------------------------------
>
>                 Key: DISPATCH-1363
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1363
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.7.0
>            Reporter: Ganesh Murthy
>            Assignee: Jiri Daněk
>            Priority: Minor
>              Labels: CI/CD
>
> Currently, when a Travis build fails, we are unable to tell if the the 
> failure was due to the rat check failure or due to a system test failure. You 
> have to scroll all the way to the bottom of the build output page to find out 
> if the rat check failed.
> An improvement would be to move the rat check to a sub build so that it is 
> easy to visually identify if the build failure is due to the rat check or 
> system test failure.



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

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

Reply via email to