@alrra/travis-scripts
Advanced tools
Comparing version
@@ -0,1 +1,8 @@ | ||
### 2.0.0 (February 9, 2016) | ||
* [[`9e81ebdb77`](https://github.com/alrra/travis-scripts/commit/9e81ebdb773f720023f124e5b8b5ae750708f8ec)] - | ||
Discontinue executing `travis-after-all` internally. | ||
* [[`b52ca7552b`](https://github.com/alrra/travis-scripts/commit/b52ca7552bfc6bee8b713fb9a6ae79f94b87068d)] - | ||
Make scripts also work with `Deploy Keys`. | ||
### 1.2.2 (January 19, 2016) | ||
@@ -2,0 +9,0 @@ |
@@ -21,5 +21,2 @@ { | ||
}, | ||
"dependencies": { | ||
"travis-after-all": "1.4.4" | ||
}, | ||
"description": "Scripts that can help automate certain things using Travis CI", | ||
@@ -35,3 +32,4 @@ "devDependencies": { | ||
"tap": "^5.0.0", | ||
"tap-mocha-reporter": "0.0.22" | ||
"tap-mocha-reporter": "0.0.22", | ||
"travis-after-all": "^1.4.4" | ||
}, | ||
@@ -49,6 +47,6 @@ "homepage": "https://github.com/alrra/travis-scripts#readme", | ||
"print-test-text": "printf \"%s\" \"$npm_package_config_test_text\"", | ||
"pretest": "rm -rf dist_test && babel test --out-dir dist_test", | ||
"pretest": "[ -z $GH_TOKEN ] && ./scripts/travis/enable_ssh_authentication.sh; rm -rf dist_test && babel test --out-dir dist_test", | ||
"test": "node dist_test/main.js | tap-mocha-reporter spec" | ||
}, | ||
"version": "1.2.2" | ||
"version": "2.0.0" | ||
} |
@@ -9,56 +9,7 @@ # travis-scripts | ||
1. Install `travis-scripts` as a `devDependency`: | ||
See [documentation](doc/usage.md). | ||
```bash | ||
$ npm install --save-dev @alrra/travis-scripts | ||
``` | ||
2. If you haven't, [enable Travis CI for your | ||
repository](https://docs.travis-ci.com/user/getting-started/#To-get-started-with-Travis-CI%3A) | ||
by going to your Travis CI profile page (`https://travis-ci.org/profile/<username>`) | ||
and flicking the repository switch on. | ||
## License | ||
3. [Install the Travis CLI](https://docs.travis-ci.com/user/encryption-keys/#Usage). | ||
4. [Generate a GitHub access token](https://github.com/settings/tokens). | ||
For more information, see [GitHub’s documentation](https://help.github.com/articles/creating-an-access-token-for-command-line-use/). | ||
5. Generate a secure key using the Travis CLI by running: | ||
```bash | ||
$ travis encrypt -r "<username>/<repository>" \ | ||
GH_TOKEN="<your_github_access_token>" \ | ||
GH_USER_EMAIL="<your_email>" \ | ||
GH_USER_NAME="<your_name>" \ | ||
--add env.global | ||
``` | ||
This adds an entry to your `.travis.yml` file: | ||
```yaml | ||
env: | ||
global: | ||
- secure: "<secure_key>" | ||
``` | ||
6. Specify the commands to be run in `.travis.yml`. | ||
Here’s an example that runs `npm install && npm run build` | ||
against the `master` branch whenever Travis CI completes a run, | ||
after which the resulting `build` directory gets deployed to | ||
the `gh-pages` branch: | ||
```yml | ||
after_success: | ||
- $(npm bin)/update-branch --commands "npm install && npm run build" | ||
--commit-message "Hey GitHub, this content is for you! [skip ci]" | ||
--directory "build" | ||
--distribution-branch "gh-pages" | ||
--source-branch "master" | ||
``` | ||
Note that these scripts use [`travis-after-all`](https://github.com/alrra/travis-after-all#readme) | ||
to ensure this is only executed once, even when there are multiple jobs | ||
in the build matrix. | ||
The code is available under the [MIT license](LICENSE.txt). |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
34446
49.82%0
-100%11
83.33%10
11.11%15
-76.56%- Removed
- Removed