Github user nsuke commented on the pull request:
https://github.com/apache/thrift/pull/450#issuecomment-95710395
@Jens-G, can you take a look at #459 before reverting ?
As to the Travis-CI failure, I'm aware that "true" CI is the Jenkins but it
would be nice if Travis failures get more attention, because it is easily
accessible to all contributors, not only to maintainers.
To name a few key differences:
* I can run builds and tests on my own Travis-CI account and verify PRs
before submitting, not for Jenkins
* I can suggest working Travis-CI test changes though PRs but don't know
any way to do it for Apache Jenkins servers
IMO, @jeking3's way of being very serious about Travis failure is good way
to reduce not only occasional regressions but also maintainers' work.
What is good about Jenkins setups ?
---
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.
---
