A cli tool for http://wercker.com/ - a continuous delivery platform.
Usage:
$ wercker
-----------------------
welcome to wercker-cli
-----------------------
Usage:
wercker create
wercker status
wercker deploy
wercker builds
wercker open targets
wercker open
wercker queue
wercker apps
wercker link
wercker login
wercker logout
wercker targets add
wercker targets list
wercker targets details
wercker --version
You can install official releases of the wercker-cli by eather running pip install wercker
or clone this repository or install it manually by cloning this
repository and run python setup.py install
note: you may need to run the commands with sudo
permissions
Starts a wizard like setup, to get your application fully working on wercker. In detail it:
- adds a new application based on your current git repository
- checks for permissions on github or bitbucket
- triggers a build
- tries to find and add a heroku deploy target.
The newly created application information is stored in a .wercker file in the root of your repository. You don't need to add this file to your git repository, if a user has access to the project, a user can run wercker link
to rebuild the .wercker file
Shows the status of the latest build.
Starts a simple wizard like setup for deploying your latest build to a deploy target.
Retrieves a login token for wercker and stores it in the .netrc in the users' home folder.
Removes the login token from the .netrc file
Opens a webpage showing the current app
Opens a webpage showing a deploy target's details
Shows a list of all applications available to the user
Shows a list of all builds and deploys that are still scheduled.
Retrieve application information for storing in the .wercker file.
Shows a list of the most recent builds
Add a new deploy target to your application. Currently only supports heroku targets.
Lists all deploy targets
This is an alias for wercker open targets
Checks pypi if there's a newer version available.
- wercker link can now be run from subfolders
- update to support wercker API changes
- fix: opening the deploy target without deploy targets resulted in url with
None