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

What rake db tasks should we use in travis? #29

Closed
motasem-salem opened this issue Sep 5, 2014 · 5 comments
Closed

What rake db tasks should we use in travis? #29

motasem-salem opened this issue Sep 5, 2014 · 5 comments
Labels

Comments

@motasem-salem
Copy link
Member

In .travis.yml, should we use:

 - bundle exec rake db:create:all
 - bundle exec rake db:migrate
 - bundle exec rake db:seed

or

   - bundle exec rake db:setup

or

   - bundle exec rake db:schema:load 

Original discussion: #24 (diff)

@motasem-salem
Copy link
Member Author

I do not have a preference. Logically I don't think seed should be used on travis builds.

@sampritipanda
Copy link
Member

Loading the schema is much faster than migrating as migrating rebuilds the schema from scratch and loads it into the db while db:schema:load just loads the schema into the database.

So my preference is:

rake db:create
rake db:schema:load

@sampritipanda sampritipanda mentioned this issue Sep 5, 2014
3 tasks
@PurityControl
Copy link
Contributor

@motasem-salem for the travils file I say drop bundle exec rake db:seed and have

bundle exec rake db:create:all
bundle exec rake db:schema:load

@NikitaAvvakumov
Copy link
Member

rake db:create # Travis doesn't need ':all', right?
rake db:schema:load

@motasem-salem
Copy link
Member Author

I think we have an agreement here. I'll use

rake db:create
rake db:schema:load

and I will close this question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants