New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include Travis CI #364

Closed
svettwer opened this Issue Apr 21, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@svettwer
Member

svettwer commented Apr 21, 2018

To improve the possibility to check PRs whether all tests are running, one should consider to include Travis CI into Citrus.

@svettwer

This comment has been minimized.

Show comment
Hide comment
@svettwer

svettwer Apr 21, 2018

Member

There is already a branch from @gucce (https://github.com/gucce/citrus/tree/travis-ci) that includes a travis.yml to start with.

Member

svettwer commented Apr 21, 2018

There is already a branch from @gucce (https://github.com/gucce/citrus/tree/travis-ci) that includes a travis.yml to start with.

@svettwer svettwer added READY and removed State: To discuss labels Apr 25, 2018

@svettwer

This comment has been minimized.

Show comment
Hide comment
@svettwer

svettwer Apr 25, 2018

Member

As a result of an internal discussion, we'll use Travis CI at least for branch builds etc.

Member

svettwer commented Apr 25, 2018

As a result of an internal discussion, we'll use Travis CI at least for branch builds etc.

@svettwer svettwer added this to the SOMEDAY milestone Apr 25, 2018

@svettwer svettwer added IN PROGRESS and removed READY labels May 11, 2018

@svettwer svettwer self-assigned this May 11, 2018

@christophd christophd modified the milestones: SOMEDAY, v2.7.6 May 24, 2018

@christophd christophd modified the milestones: v2.7.6, v2.7.7 Jun 13, 2018

@svettwer svettwer added TO REVIEW and removed IN PROGRESS labels Jul 6, 2018

svettwer added a commit that referenced this issue Jul 30, 2018

Merge pull request #434 from citrusframework/feature/364
(#364) Added .travis.yml from my fork
@svettwer

This comment has been minimized.

Show comment
Hide comment
@svettwer

svettwer Jul 30, 2018

Member

builds are currently failing + had to cherrypick from master into bugfix-2.7 branch, because the PR was pointing to master.

I've downgraded testNG to 6.11 to avoid the DynamicGraph bug introduced with 6.12. This should fix the build but I do still get some timeouts from integration tests.

Member

svettwer commented Jul 30, 2018

builds are currently failing + had to cherrypick from master into bugfix-2.7 branch, because the PR was pointing to master.

I've downgraded testNG to 6.11 to avoid the DynamicGraph bug introduced with 6.12. This should fix the build but I do still get some timeouts from integration tests.

@svettwer

This comment has been minimized.

Show comment
Hide comment
@svettwer

svettwer Jul 30, 2018

Member

I can reproduce the issue locally. The recently added tests from jms topics in JmsTopicSubscriberTest are running into a timeout.

Member

svettwer commented Jul 30, 2018

I can reproduce the issue locally. The recently added tests from jms topics in JmsTopicSubscriberTest are running into a timeout.

@svettwer

This comment has been minimized.

Show comment
Hide comment
@svettwer

svettwer Aug 3, 2018

Member

I've fixed the tests so that the builds are running but due to the 4MB log limit the build aborts.

Member

svettwer commented Aug 3, 2018

I've fixed the tests so that the builds are running but due to the 4MB log limit the build aborts.

@svettwer

This comment has been minimized.

Show comment
Hide comment
Member

svettwer commented Aug 3, 2018

svettwer added a commit that referenced this issue Aug 4, 2018

@svettwer svettwer closed this Aug 4, 2018

@svettwer svettwer removed the TO REVIEW label Aug 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment