[
https://issues.apache.org/jira/browse/MESOS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954502#comment-14954502
]
Adam B commented on MESOS-3713:
-------------------------------
Hmm.. I wonder if we're spreading our CI over too many tools. We use Jenkins
(builds.apache.org) for post-commit checks as well as periodic ReviewBot checks
on ReviewBoard. We could even enable OSX Jenkins builds, according to
http://wiki.apache.org/general/Jenkins#Are_there_recommended_or_mandatory_Jenkins_settings_for_ASF_projects.3F
We don't have any github pull verification (Travis could fill that gap), but
most of our patches are done in RB. Broken travis builds are bad, but we may be
able to just disable those rather than maintain two CI tools. (How would we
disable the travis builds?)
I asked [[email protected]] to create this JIRA with his patch proposal, but
I'd like to get feedback from somebody who's previously messed with our Jenkins
build. cc: [~benjaminhindman] [~vinodkone] [~bmahler] [~jvanremoortere]
[~tnachen]
> Add travis file to test OS X + Clang
> ------------------------------------
>
> Key: MESOS-3713
> URL: https://issues.apache.org/jira/browse/MESOS-3713
> Project: Mesos
> Issue Type: Task
> Reporter: haosdent
> Assignee: haosdent
>
> Add a .travis.yml to test "OSX + Clang".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
