[
https://issues.apache.org/jira/browse/MESOS-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954554#comment-14954554
]
Adam B commented on MESOS-3713:
-------------------------------
To get the same benefits of merging in this simple travis.yml, we would need to:
1. Disable travis CI for Mesos, so we stop getting emails about perpetual
failures
2. Add Jenkins github PR verification (`verify_reviews.py` may need to use the
-g flag of `apply-review.sh`)
3. Add OSX build configuration to CI (and ReviewBot?)
4. Increase the capacity/frequency of our Jenkins builds (travis is more free
hardware)
Disadvantages to merging this travis.yml:
1. Now we have to manage 2 different CI tools.
Honestly, I'm in favor of merging this in for now. We can always disable the
travis build later if we ever add github PR verification and/or OSX builds to
Jenkins. Unless that's easy enough to do, but I'm not very familiar with
Jenkins personally.
> 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)
