Once you have your stages/environments configured, you might find yourself needing to change the branch that is tied to it.
This can happen when you are trying to test an update on staging that might not be on
master (assuming you have staging connected to
Update the Source Branch
To change the branch that is tied to a stage, go in to the stage settings and select Update Source.
And select the branch that you’d like to auto-deploy to this stage.
This will automatically start creating a build in the stage with the selected branch.
By default, auto-deploying for the
production stage is turned off and is turned on for all other stages. This is a good practice since it is better to review your code and infrastructure changes before deploying to production.
However, you might run in to cases where you’d like to configure the auto-deploy setting. To do so, go to the stage settings and select Enable Auto-Deploy.
Just as the case above, this allows you to select the branch you’d like to auto-deploy. You can also disable auto-deploying at any time in the future by hitting the Disable Auto-Deploy button.
Finally, you can trigger one-off deployments to a stage from any branch. This can be useful when you want to test a hotfix branch in your staging environment.
To do so, hit the Trigger Deploy button from the stage settings.
You’ll be asked to pick a branch to deploy.
And hitting Deploy Branch triggers a one-off deployment to the current stage.
By updating the stage source, the auto-deploy options, and the ability to manually deploy; Seed gives you the flexibility to maintain consistent endpoints for your environments while deploying the branch you need.
If you have any questions or feedback feel free to contact us via email.