Heroku - Features, integrations, alternatives & more
What it does
This action uploads your files from Buddy’s pipeline filesystem to Heroku Dyno, the building blocks that power any Heroku app.
How it works
The action uses Buddy’s OAuth integration with a Heroku account. Once it’s set up, it allows for selecting Heroku’s application to deploy to.
Heroku Dyno Action Features
- The action uses .gitignore from the repository by default, but it’s possible to set custom .gitignore in the action settings. The option could be used to push artifacts that we don’t want to store in the repository
- If Don't deploy changes made by previous actions is set, changes made by other actions in the pipeline filesystem will be ignored; like changed files or generated artifacts
- When Without force is selected, this action will fail on conflicts
- It’s possible to exclude paths and file types from transfer using patterns, specific directories and file names.
- The action can be configured in YAML mode. See Heroku YAML parameters and Heroku YAML config example
- Buddy's Heroku API is supported
- The action supports conditional execution: it can be run on each execution, only if there are changes in the repository or specific paths since last execution or if an environment variable has a specific value
- Error handling: you can either stop the execution, mark action and pipeline as failed or proceed the execution, mark action as warning and jump to the next action