-
Notifications
You must be signed in to change notification settings - Fork 7
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
Automate npm/yarn installation test of the CLI tool #274
Milestone
Comments
anuveyatsu
added a commit
that referenced
this issue
Feb 13, 2018
…allables + added shell script for it - refs #274
anuveyatsu
added a commit
that referenced
this issue
Feb 13, 2018
anuveyatsu
added a commit
that referenced
this issue
Feb 13, 2018
… versions weren't working - refs #274
anuveyatsu
added a commit
that referenced
this issue
Feb 13, 2018
… works (will be removed later) - refs #274
anuveyatsu
added a commit
that referenced
this issue
Feb 13, 2018
…eady to open a pull request - refs #274
anuveyatsu
added a commit
that referenced
this issue
Feb 13, 2018
* [travis][m]: refactored travis config for automation of npm/yarn installables + added shell script for it - refs #274 * [travis][xs]: fixed array syntax for yaml data - refs #274 * [travis][xs]: re-wrote travis config matrix otherwise listing node_js versions weren't working - refs #274 * [travis][xs]: added after_success script to test out how shell script works (will be removed later) - refs #274 * [travis][xs]: removed temporary 'after_success' script so now we're ready to open a pull request - refs #274
FIXED - you can see builds on Travis or take a look at |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As described in datopian/datahub-qa#91 we want to install data-cli using npm/yarn and test with basic commands after each deployment.
Acceptance criteria
Tasks
.travis.yml
to run script for installation of data-cli after each deploymentAnalysis
We want to run the CLI installation script only when a new release is issued so this should go somewhere in the
after_deploy
script in the travis configs. Also, we want to test it on Linux + MacOS and using Node versions 7, 8 and 9. Still, all tests should be run as before using only Linux and node8.The
test-script.sh
should look like:The text was updated successfully, but these errors were encountered: