You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/09/01 02:09:45 UTC

[jira] [Commented] (CALCITE-867) Travis CI not building for PRs

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

Julian Hyde commented on CALCITE-867:
-------------------------------------

As far as I know this is not possible for Apache projects. The github user - in this case Apache - needs to enable Travis, and Apache projects don't have control over that user. Apache projects generally use Apache jenkins - and yes, Calcite needs to do that too.

> Travis CI not building for PRs
> ------------------------------
>
>                 Key: CALCITE-867
>                 URL: https://issues.apache.org/jira/browse/CALCITE-867
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Marc Prud'hommeaux
>            Assignee: Julian Hyde
>            Priority: Minor
>
> When submitting a pull request via github (e.g., https://github.com/apache/incubator-calcite/pull/125), it is nice to know when the PR breaks the build. Github usually automatically asks Travis to run a build when there is a .travis.yml file configured, but for some reason this isn't happening with Calcite.
> I suspect that it may be because Calcite's .travis.yml has a branch filter in place. If this isn't necessary, I wonder if removing it might automatically let Github run the integration tests whenever a PR is submitted?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)