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

Added support for running tests on Travis-CI #8

Closed
wants to merge 58 commits into from

Conversation

OriHoch
Copy link
Contributor

@OriHoch OriHoch commented Jan 10, 2017

Travis-CI is free for open source projects

https://travis-ci.org/OriHoch/Spark/builds/190556286

tests are failing but not because of Travis-CI..

@OriHoch
Copy link
Contributor Author

OriHoch commented Jan 10, 2017

follow-up issue: #9

@OriHoch OriHoch changed the title Added support for running tests on Travis-CI [WIP] Added support for running tests on Travis-CI Jan 10, 2017
@OriHoch OriHoch changed the title [WIP] Added support for running tests on Travis-CI Added support for running tests on Travis-CI Jan 10, 2017
@netanelben
Copy link
Contributor

great contribution, CI is needed from day-1.
need all to review

@amotenko
Copy link
Member

This should hopefully work with our docker image. Once we have a staging server with a working docker image this should be tested against it and merged.

Copy link
Contributor

@ripper234 ripper234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK, Great work.

  1. Knex should be used for migrations instead of plain SQL as per standardize the migration and DB setup process #4. (current .sh calls them). The /sql folder is deleted in another standardize the db migration process (switch to knex) and use sqlite for dev environment #18 I believe, let's update this PR to reflect that.

  2. Please no .sh files, I think it's better to put the logic there into the package.json file directly (let's use that as a build system). See Introduction to Using NPM as a Build Tool.

(Item 2 above is not a blocker, I ACK this PR, if you don't do Item 2 please copy-paste the text above into a new issue)

…sqlite-for-local-development

# Conflicts:
#	README.md
#	config/default.js
#	opsworks.js
#	sql/camps.sql
#	sql/schema.sql
…om:OriHoch/Spark into 17-should-use-sqlite-for-local-development
…ocal-development

standardize the db migration process (switch to knex) and use sqlite for dev environment
@OriHoch
Copy link
Contributor Author

OriHoch commented Jan 17, 2017

thanks @ripper234 - I will update according to your comments and merge

@OriHoch
Copy link
Contributor Author

OriHoch commented Jan 17, 2017

There are some conflicts, I'll open a new PR

@OriHoch OriHoch closed this Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants