Skip to content
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

Add travis build config #574

Merged
merged 1 commit into from
Apr 21, 2018
Merged

Add travis build config #574

merged 1 commit into from
Apr 21, 2018

Conversation

magro
Copy link
Collaborator

@magro magro commented Mar 21, 2018

Tests with java8 and java7, on successful build publishes the artifacts to sonatype snapshots.

The inoio jenkins required too much maintenance and became unstable the last days.
We also need travis to be able to build/test with jdk 9/10.
An additional advantage of Travis are PR verification builds, so that it's immediately clear if anything got broken.

@NathanSweet can you please activate the Travis build according to 2. from the Getting Started guide?

@magro magro changed the title Add travis config Add travis build config Mar 21, 2018
@magro magro force-pushed the master branch 3 times, most recently from 632884f to 6390af4 Compare March 25, 2018 15:29
@magro
Copy link
Collaborator Author

magro commented Apr 1, 2018

@NathanSweet Alternatively you can make me an admin for kryo on github so that I can activate the travis build myself.

Tests with java8 and java7, on successful build publishes the artifacts
to sonatype snapshots.
@magro magro merged commit 8e81efb into EsotericSoftware:master Apr 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant