Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@heroku-cli/plugin-ci
Advanced tools
Heroku CLI plugin for Heroku CI
$ npm install -g @heroku-cli/plugin-ci
$ heroku COMMAND
running command...
$ heroku (--version|-v)
@heroku-cli/plugin-ci/8.1.7 darwin-x64 node-v16.19.0
$ heroku --help [COMMAND]
USAGE
$ heroku COMMAND
...
heroku ci
display the most recent CI runs for the given pipeline
USAGE
$ heroku ci [-a <value>] [--watch] [-p <value>] [--json]
FLAGS
-a, --app=<value> app name
-p, --pipeline=<value> name of pipeline
--json output in json format
--watch keep running and watch for new and update tests
DESCRIPTION
display the most recent CI runs for the given pipeline
EXAMPLES
$ heroku ci --app murmuring-headland-14719
See code: src/commands/ci/index.ts
heroku ci:info TEST-RUN
show the status of a specific test run
USAGE
$ heroku ci:info TEST-RUN [-a <value>] [--node <value>] [-p <value>]
FLAGS
-a, --app=<value> app name
-p, --pipeline=<value> name of pipeline
--node=<value> the node number to show its setup and output
DESCRIPTION
show the status of a specific test run
EXAMPLES
$ heroku ci:info 1288 --app murmuring-headland-14719
See code: src/commands/ci/info.ts
heroku ci:last
looks for the most recent run and returns the output of that run
USAGE
$ heroku ci:last [-a <value>] [--node <value>] [-p <value>]
FLAGS
-a, --app=<value> app name
-p, --pipeline=<value> name of pipeline
--node=<value> the node number to show its setup and output
DESCRIPTION
looks for the most recent run and returns the output of that run
EXAMPLES
$ heroku ci:last --pipeline=my-pipeline --node 100
See code: src/commands/ci/last.ts
heroku ci:rerun [NUMBER]
rerun tests against current directory
USAGE
$ heroku ci:rerun [NUMBER] [-a <value>] [-p <value>]
FLAGS
-a, --app=<value> app name
-p, --pipeline=<value> name of pipeline
DESCRIPTION
rerun tests against current directory
EXAMPLES
$ heroku ci:rerun 985 --app murmuring-headland-14719
See code: src/commands/ci/rerun.ts
heroku ci:run
run tests against current directory
USAGE
$ heroku ci:run [-a <value>] [-p <value>]
FLAGS
-a, --app=<value> app name
-p, --pipeline=<value> name of pipeline
DESCRIPTION
run tests against current directory
EXAMPLES
$ heroku ci:run --app murmuring-headland-14719
See code: src/commands/ci/run.ts
heroku ci:info
Shows the information for a particular ci run on a pipeline.
USAGE
$ heroku ci:info 555 --pipeline=my-pipeline # 555 is the test number
heroku ci:last
Shows the information for the last run for a given pipeline.
USAGE
$ heroku ci:last --pipeline=my-pipeline
heroku ci:run
Run this from within your repo directory to trigger a test agains the current branch and commit.
USAGE
$ heroku ci:run --pipeline=my-pipeline
heroku ci:rerun
Re-run a previous test run. If no test run number is provided, the most recent test run will be re-run.
USAGE
$ heroku ci:rerun 555 --pipeline=my-pipeline # 555 is the test number
8.1.7 (2023-06-01)
Note: Version bump only for package heroku
FAQs
Heroku CLI plugin for Heroku CI
The npm package @heroku-cli/plugin-ci receives a total of 2,151 weekly downloads. As such, @heroku-cli/plugin-ci popularity was classified as popular.
We found that @heroku-cli/plugin-ci demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 27 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.