Github user dcaba commented on the issue:
https://github.com/apache/mesos/pull/165
Hi @kaysoky , @haosdent !
thanks so much for your comments. Yep, I see this is not new for the
project, and I was missing a lot of context when I initiated this PR. So now we
have two options, from my point of view:
- Dismiss this PR. This integration brings small or no value to the project
(at a cost of a .travis.yml and keeping the integration active), as the free
version of travis does not meet all the CI requirements you currently have
covered with Jenkins.
- Accept the PR. This will fix the "red flag" we can see in all the PRs,
and this job will potentially provide quicker feedback as we are only compiling
in the end (while Jenkins will bring the results of all the test coverage later)
Please, make the decision bearing in mind what's more convenient for the
project... No rancor at all if you close without merge ;) (it was an exercise
requiring small efforts). But I'd appreciate the related Jira issue is closed
(MESOS-5655) an you actually disable Travis to prevent these red crosses to add
noise to all PRs.
Best,
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
