| 1 | # Heroku CI CLI
|
| 2 | [](https://dashboard.heroku.com/pipelines/420ca0bc-031b-479a-9335-1d51046daab2/tests)
|
| 3 |
|
| 4 | The CLI plugin for Heroku CI
|
| 5 |
|
| 6 | ## Installation
|
| 7 | ```sh
|
| 8 | heroku plugins:install heroku-ci
|
| 9 | ```
|
| 10 |
|
| 11 | ## Commands
|
| 12 |
|
| 13 | All commands accept a `-a` flag. This should be the name of an app in the pipeline you have connected to Heroku CI. The `-a` flag can be omitted if you are in the directory of an app already.
|
| 14 |
|
| 15 | `heroku ci:list`, aliased as `heroku ci`
|
| 16 |
|
| 17 | Show the statuses of the most recent test runs. Add the `-w` or `--watch` flag to keep the session running and listen for updates.
|
| 18 |
|
| 19 | `heroku ci:info NUMBER`
|
| 20 |
|
| 21 | Show the status of a specific test run. If no run number is provided the most recent will be shown.
|
| 22 |
|
| 23 | `heroku ci:last`
|
| 24 |
|
| 25 | Show the status of the most recent test run
|
| 26 |
|
| 27 | `heroku ci:run`
|
| 28 |
|
| 29 | Run this from within your repo directory to trigger a test agains the current branch and commit.
|
| 30 |
|
| 31 | `heroku ci:rerun NUMBER`
|
| 32 |
|
| 33 | Re-run a previous test run. If no test run number is provided, the most recent test run will be re-run.
|