dustingetz / react-cursor

Immutable state for React.js
1.03k stars 50 forks source link

Add Travis CI configuration. #58

Closed lijunle closed 9 years ago

lijunle commented 9 years ago

Use Travis virtual screen to run test in Chromium: http://stackoverflow.com/a/25661593/1436671

lijunle commented 9 years ago

@dustingetz To enable Travis, you also need to enable the project in Travis home page. See its docs.

dustingetz commented 9 years ago

Thank you! will merge soon

lijunle commented 9 years ago

@dustingetz could you like to merge this? A CI build is important to keep the code quality. :white_check_mark:

dustingetz commented 9 years ago

If I click merge right now, what will happen? I haven't used this feature before

lijunle commented 9 years ago

Nothing happens.

You need to go the http://travis-ci.org to enable your repo. After that, when new commit push to this repo, or somebody send a PR, Travis will trigger a build to run the tests.

Here is a passed example. You can click on one job to see the console log - all tests are run and green. :smiley:

lijunle commented 9 years ago

@damassi are you going to enable it now? If enabled, I can re-push my another RP to trigger a build - you can see some interesting things. :)

dustingetz commented 9 years ago

It's enabled, go ahead and re-push

On Tue, Nov 3, 2015 at 12:14 PM, Junle Li notifications@github.com wrote:

@damassi https://github.com/damassi are you going to enable it now? If enabled, I can re-push my another RP to trigger a build - you can see some interesting things. :)

— Reply to this email directly or view it on GitHub https://github.com/dustingetz/react-cursor/pull/58#issuecomment-153421737 .

lijunle commented 9 years ago

Finally, the failure is resolved.

Look on the RP page, you will find there is some :x: and :white_check_mark: , which indicate that commit is passing the test or not. You can click on those icons to check the detail build output.

The Travis build ensure the RP won't break the test accidentally. Enjoy it. :ghost: