GitHub user kops opened a pull request:
https://github.com/apache/cxf/pull/60
Enable travis-ci to help contributors submit valid pull-requests
I work on a PR (#55) to enable toolchains for codegen plugin. It's not
really difficult to implement this feature. I spent most of my effort checking
the full build is OK.
Enabling Travis CI may help contributors validating their work and it may
help maintainers qualifying contributions.
- test execution is split in 2 test suites, I'm aware that my choice may
not a good one. Travis builds is limited to 50 minutes. When the build exceed
this time they recommand splitting test execution :
http://docs.travis-ci.com/user/speeding-up-the-build/
- Travis CI log output is limited to 10 000 lines, that's why I enabled
maven _quiet_ mode
- Some network based tests failed, I had to enable
`java.net.preferIPv4Stack` parameter
Please note that I had to exclude 4 tests to get a successful build on
Travis CI environment.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kops/cxf feature/enable_travis
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf/pull/60.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #60
----
commit 6f860331263b138cfe49bb925890791c5465beff
Author: kops <[email protected]>
Date: 2015-03-28T00:47:14Z
Enable travis-ci
Test execution is separated in two test suites because CXF build takes more
than 50 minutes on travis-ci environment.
commit 860212c93e48f36bfc07f058b5eb91bf92bfd099
Author: kops <[email protected]>
Date: 2015-03-28T12:41:36Z
Exclude 4 tests not passing on travis-ci environment
WSDiscoveryClientTest.java
ThreadPoolTest.java
NoAriesBlueprintTest.java
JAXRSClientServerTikaTest.java
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
