We use heroku-orb in circleci for our heroku deployments and our heroku deployments are triggered when a new semantic version is created, the semantic version can be created from couple of branches. In this case we want to have a control on the heroku deployment on a each environment based on the semantic version branch.
As we do not have a conditional steps allowed in circleci on orbs , adding the provision in heroku orb by adding a new param
skip-deploy
If it is set to true , the heroku-deploy-via-git will not perform any deployment
ppentakota1
commented
3 years ago
We use heroku-orb in circleci for our heroku deployments and our heroku deployments are triggered when a new semantic version is created, the semantic version can be created from couple of branches. In this case we want to have a control on the heroku deployment on a each environment based on the semantic version branch.
As we do not have a conditional steps allowed in circleci on orbs , adding the provision in heroku orb by adding a new param skip-deploy
If it is set to true , the heroku-deploy-via-git will not perform any deployment