kevin/asdf
1
Fork 0
mirror of https://github.com/asdf-vm/asdf.git synced 2024-11-15 01:28:17 -07:00
Code Issues Packages Projects Releases Wiki Activity

Add info about using the CI repo on plugin test

Browse Source
This commit is contained in:
Marcos Ferreira 2018-10-24 19:20:13 -03:00 committed by GitHub
parent 65ce0db5e1
commit 5a2e69ca86
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/creating-plugins.md
View File

@ -137,7 +137,7 @@ Here is a sample `.travis.yml` file, customize it to your needs
```yaml
language: c
script: asdf plugin-test nodejs https://github.com/asdf-vm/asdf-nodejs.git 'node --version'
script: asdf plugin-test nodejs $TRAVIS_BUILD_DIR 'node --version'
before_script:
- git clone https://github.com/asdf-vm/asdf.git asdf
- . asdf/asdf.sh
@ -146,6 +146,14 @@ os:
- osx
```
Note:
When using another CI, you will need to check what variable maps to the repo path.
You also have the option to pass a relative path to `plugin-test`.
For example, if the test script is ran in the repo directory: `asdf plugin-test nodejs . 'node --version'`.
## GitHub API Rate Limiting
If your plugin's `list-all` depends on accessing the GitHub API, make sure you provide