Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@heroku-cli/plugin-ci

Package Overview
Dependencies
Maintainers
29
Versions
79
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@heroku-cli/plugin-ci

Heroku CLI plugin for Heroku CI

  • 7.62.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
154
decreased by-82.96%
Maintainers
29
Weekly downloads
 
Created
Source

@heroku-cli/plugin-ci

Heroku CLI plugin for Heroku CI

oclif Version

CircleCI

Appveyor CI Downloads/week License

Usage

$ npm install -g @heroku-cli/plugin-ci
$ heroku COMMAND
running command...
$ heroku (-v|--version|version)
@heroku-cli/plugin-ci/7.62.0 darwin-x64 node-v16.14.0
$ heroku --help [COMMAND]
USAGE
  $ heroku COMMAND
...

Commands

heroku ci

display the most recent CI runs for the given pipeline

USAGE
  $ heroku ci

OPTIONS
  -a, --app=app            app name
  -p, --pipeline=pipeline  name of pipeline
  --json                   output in json format
  --watch                  keep running and watch for new and update tests

EXAMPLE
  $ 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

OPTIONS
  -a, --app=app            app name
  -p, --pipeline=pipeline  name of pipeline
  --node=node              the node number to show its setup and output

EXAMPLE
  $ 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

OPTIONS
  -a, --app=app            app name
  -p, --pipeline=pipeline  name of pipeline
  --node=node              the node number to show its setup and output

EXAMPLE
  $ 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]

OPTIONS
  -a, --app=app            app name
  -p, --pipeline=pipeline  name of pipeline

EXAMPLE
  $ 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

OPTIONS
  -a, --app=app            app name
  -p, --pipeline=pipeline  name of pipeline

EXAMPLE
  $ 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

Keywords

FAQs

Package last updated on 04 Aug 2022

Did you know?

Socket

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.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc