Skip to content

DeployHeroku

Bastien Abadie edited this page Jun 5, 2019 · 1 revision

The deploy-heroku command allows you to deploy on Heroku an image previously built on another taskboot task, and stored as a Taskcluster artifact.

You can either publish the application as a web or worker dyno.

Secret configuration

You need to setup the Heroku authentication tokens in your Taskcluster secret :

heroku:
  username: user@provider.com
  password: mystrongp4ssword

The password can be one of the following:

  • Recommended: an authentication token, like the one for heroku's cli application (you can retrieve yours with heroku auth:token for development, or heroku authorizations:create for production - official docs)
  • ⚠️ If your account use an SSO authentication scheme (such as Mozilla accounts), you'll need to create another dedicated account with SSO disabled to get a long lived token.

Arguments

Argument Type Description Sample values
--task-id Optional string, defaults to env variable TASK_ID set on Taskcluster The Taskcluster task id to use for dependent tasks lookups deadbeef1234
--artifact-filter Optional string, defaults to public/**.tar fnmatch glob expression filtering dependent tasks artifacts to upload public/my-project/image*.tar
--exclude-filter Optional string fnmatch glob expression filtering dependent tasks artifacts NOT to upload. Can be used in union with --artifact-filter public/my-project/image-old-*.tar
--heroku-app Required string The Heroku application name to update. web-app-production
--heroku-dyno-type Optional string, defaults to web The Heroku dyno type to update. worker
Clone this wiki locally