Added Travis CI support. #172

Merged
merged 8 commits into from Jan 16, 2013

Conversation

Projects
None yet
4 participants
Contributor

qubyte commented Jan 16, 2013

Note that tests pass for zmq2, but not zmq3. This behaviour was confirmed locally.

Contributor

qubyte commented Jan 16, 2013

All tests now pass.

Collaborator

ronkorving commented Jan 16, 2013

Looks good, thanks!

ronkorving merged commit 75fb4cc into JustinTulloss:master Jan 16, 2013

Collaborator

ronkorving commented Jan 16, 2013

I've merged it, but the build status stays unknown.
@JustinTulloss , could you enable the Travis service hook?

Owner

JustinTulloss commented Jan 17, 2013

I enabled it, it still says unknown. I think it might be building? I'll look into it again shortly if it doesn't update.

Contributor

qubyte commented Jan 17, 2013

You may need to enable this from the Travis side. There's a box in the service hooks travis CI tab. I used the instructions in there to get it working for me. Make sure that the active box is checked. I made that mistake initially. Probably the problem is the token though.

Even when it is properly set, the build takes a while. The config file I wrote will spawn four workers, so four tests are entered into the queue. When at least one gets the top of the queue and starts the build state will go amber within Travis CI, and if you inspect it you can see the build process itself. It's a little difficult to describe how to navigate that, but you'll know when it's working.

screen

Collaborator

ronkorving commented Jan 21, 2013

@JustinTulloss so, now after the weekend, it still says build status unknown. Could you have another look? (see @qubyte 's response above)

Collaborator

AlexeyKupershtokh commented Jan 21, 2013

Is it enabled on this page: https://travis-ci.org/profile ?

Travis CI - Free Hosted Continuous Integration Platform for the Open Source Community - Google Chrome_054

Contributor

qubyte commented Jan 21, 2013

@AlexeyKupershtokh Try hitting the Sync now button and seeing if the list updates with the repo. Once it appears, switching to on should complete the configuration. It may or may not require some action (such as a merge into master) to activate a build after this.

Collaborator

AlexeyKupershtokh commented Jan 21, 2013

@qubyte I don't have any problems :) Just hinting where @JustinTulloss should look for enabling the repo as well.

Contributor

qubyte commented Jan 21, 2013

@AlexeyKupershtokh Ah! My bad. I was on automatic and thought I was talking to @JustinTulloss. :)

Collaborator

ronkorving commented Jan 25, 2013

@JustinTulloss any update on this?

Owner

JustinTulloss commented Jan 27, 2013

Appears to be working now.

Collaborator

ronkorving commented Jan 27, 2013

Awesome, thanks!

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