You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/17 12:35:00 UTC
[jira] [Commented] (DISPATCH-1363) Remove apache rat check from
main travis build and move to a sub build
[ https://issues.apache.org/jira/browse/DISPATCH-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953699#comment-16953699 ]
ASF GitHub Bot commented on DISPATCH-1363:
------------------------------------------
jdanekrh commented on pull request #592: DISPATCH-1363 - Move RAT licence check from travis builds into a sub build
URL: https://github.com/apache/qpid-dispatch/pull/592
Now easier to do when the `matrix` key is in place in `.travis.yml`.
Doing this also fixes the duplicated top level `cache` key in `.travis.yml` we had.
It appears that `matrix` is outdated syntax, and `jobs` should be preferred, https://github.com/travis-ci/docs-travis-ci-com/issues/1500. The doc page https://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix uses `matrix.include` in the text and `jobs.include` in the yaml samples. Task for another time.
----------------------------------------------------------------
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:
users@infra.apache.org
> 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
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org