travis-ci continuous testing about octopus HOT 11 CLOSED

Ok, so I have a branch on my fork with passing tests for Ruby 1.8.7, 1.9.2, and ree. I did have to set one test to pending though and may require some assistance in getting it corrected. Please take a look at my branch at bramswenson/octopus named fix_travis_ci_builds. Here is the green run on travis http://travis-ci.org/#!/bramswenson/octopus/builds/437983

from octopus.

Also, appraisal may be redundant if you guys decide to use travis-ci. I would be happy to clean out the appraisal items in favor of letting travis solve the same issues. It would clean up the root project directory a little bit, and lower the number of development dependencies. I'm not sure if this is an acceptable trade off for you all however, so I'll wait for some input.

from octopus.

Finally, in my forked branch listed above, there is a single test that I had to set to pending for all Rubies. I have added some notes, but left the code in place. It is my intent to solve this issue before issuing a proper pull request, but I could use some input on this one. I toyed with it a bit, but wasn't able to narrow it down past locating the exact place we run into trouble. Here is the commit bramswenson/octopus@1c2ea56

from octopus.

Hi Bram,

Thanks for all your efforts on running Octopus on travis-ci. Besides having appraisal + travis sounds redundant, I'd like to run all specs against all versions of rails before pushing the commit to the master branch. So I think appraisal should stay, but I will be happy to merge your travis-ci config and enable it.

Send me a pull request with the config, and the instructions to enable it.

Thanks,

Thiago

from octopus.

@tchandy can you configure travis-ci?

I'm not able to configure the travis since the repository is in your account :)

from octopus.

+1 for using travis instead of appraisal

For local testing it's always possible to use gemsets with different versions of AR installed.

from octopus.

@ragalie I contacted travis on twitter to know if it possible to me configure the project there.

If is not, I will slap @tchandy to configure :)

from octopus.

You folks want me to sync my feature branch where travis was working (mostly)? I haven't looked at it in some time but I'm sure it won't be to hard to synchronize.

from octopus.

Would be great!

Sent from my iPhone

On 23/01/2013, at 03:43 AM, Bram Swenson [email protected] wrote:

You folks want me to sync my feature branch where travis was working (mostly)? I haven't looked at it in some time but I'm sure it won't be to hard to synchronize.

—
Reply to this email directly or view it on GitHub.

from octopus.

I seem to be having some problems getting the tests to run locally, much less on travis. It seems some things have changed with regards to the test setup procedures. The current guidelines provided in the contributors section of the README file not longer seems to work. Anyone have any suggestions?

@sobrinho I've been testing octopus on travis by configuring my own branch with it: https://travis-ci.org/bramswenson/octopus At least one can test with travis even without control over the primary repo.

from octopus.

Good news!

Travis is running now: https://github.com/tchandy/octopus

I will review the build script today but I'm closing the issue since it's running.

Thanks @tchandy! ❤️

from octopus.