I see the same thing - see this on CircleCI at the top of the build:
There are multiple applicable deployment sections! Using 'production'.
when I have both a ‘production’ and ‘staging’ off of branch:master
We are going to have multiple ‘production’ apps from the same codebase and we will need a way to deploy to both apps. Any workaround (have one deployment kick off another?) much appreciated!
have you tried deploying with version release tags, prefixed with an app-id vs trying to deploy from a branch … ?
going through the same process now, figured having multiple develop, stage, prod branches would be an inherent nightmare (to my already existing disgust of a reality…) , and that having one branch across all apps, but tagging releases for different commits per app-id to be a simpler solution, so far so good .
I would like to continue deploying my app to heroku when the master branch builds, but also start to publish a static site for the component library for this app to GitHub Pages, also limited to only the master branch.
The deployment section seems like the appropriate place to manage this, with the available multiple subsections. The only detail in the documentation that seems to suggest that my approach is not appropriate is the following:
In instances of multiple branches, the first one that matches the branch being built is the one that is run.
Since it seems like this is an intentional limitation, are there other options? I attempted to do the deploy to GitHub Pages as a post step under test, but I could not figure out how to limit it to only deploy when building the master branch.
For our project we need to build artifacts on every branch but want to push some package files to gemnasium only on pushes to master. How do we accomplish this?