FAQ
I am working on an extension which works on 1-3-stable versions of Spree
without any issue, also whenever I push changes to github, it gets tested
on travis-ci with no issue. So, I recently upgraded the extension for spree
2.0.0 for 2-0-stable versions, and when I pushed the changes to github,
travis-ci is not able to run test cases as it was running for previous
version.

It gets stuck at this command:
*$ bundle exec rake test_app*
*Generating dummy Rails application...*
*Setting up dummy database...*
*Running extension installation generator...*
* append app/assets/javascripts/store/all.js*
* append app/assets/javascripts/admin/all.js*
* insert app/assets/stylesheets/store/all.css*
* insert app/assets/stylesheets/admin/all.css*
* run bundle exec rake railties:install:migrations
FROM=spree_active_sale from "."*
*Would you like to run the migrations now? [Y/n]*

Now, tavis-ci console expects an input, where it should have continued, and
have not asked for anything. I can ensure that this is happening only when
I upgraded Spree to 2.0.0 in my gemspec, and not in 1.3.x versions.

How do i fix this?

--

Please consider the environment before printing this email.

Regards,
Surya

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 3 | next ›
Discussion Overview
groupspree-user @
categoriesrubyonrails
postedJun 20, '13 at 4:18p
activeJun 21, '13 at 6:50a
posts3
users2
websitespreecommerce.com
irc#RubyOnRails

2 users in discussion

Surya: 2 posts Jdutil: 1 post

People

Translate

site design / logo © 2022 Grokbase