-
Notifications
You must be signed in to change notification settings - Fork 50
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
Adding .travis.yml for Travis CI integration. #3
Conversation
38084fa
to
d6c26a8
Compare
install: | ||
- npm install | ||
- mkdir node_modules_new | ||
- mkdir node_modules_new/grunt-drupal-tasks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mkdir -p?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, updated.
I haven't done much with Travis, but not quite following the point of the shenanigans with node_modules_new? |
f58c92a
to
5116cd6
Compare
…ain package.json.
…, remove composer.json to remove dependency on Composer and PHP.
496152c
to
63af775
Compare
@grayside Travis gives you a specific checkout of grunt-drupal-tasks that corresponds to the pull request or branch code. Ideally the test will use the plugin and example code from this checkout. To set this up from the single checkout, this manual restructuring of the directories is needed. It moves the example dir contents into the Travis root dir and what was in the root into a node_modules/grunt-drupal-tasks dir. |
👍 |
"name": "drupal-grunt-starter", | ||
"description": "Build and testing tools for a Drupal project built based on Grunt.", | ||
"name": "grunt-drupal-tasks", | ||
"description": "Grunt-based build and testing tasks for Drupal projects.", | ||
"version": "0.2.0", | ||
"private": true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it's technically not "private" anymore, but that can wait for npm listing. Looking good to me! Yay green lights!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@grayside Good catch. I pushed a few updates to the develop branch, including the removal of the private flag.
a123517
to
7255c67
Compare
Adding Travis CI integration.
No description provided.