Deploy to multiple environments
See original GitHub issueLet’s say we want to deploy a preview of one commit to two environments. In our build step we will provide different API base urls for each envirnoment, dev
and qa
.
Is there any way to achieve this?
I suspect we can do two deploy steps, but it’s not clear how we display in each message which environment the link is for.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Multi Environment Deployment with CI/CD | by Anuraag Jain
Automating your app deployment helps you to focus and eliminate the redundant steps. Sometimes your app has to have multiple environments for various...
Read more >How to use GitLab CI to deploy to multiple environments
If you deploy to multiple environments, GitLab will conserve the history of deployments, which allows you to rollback to any previous version.
Read more >How to Manage Multiple Environments with DevOps
In most DevOps settings you'll find that there are multiple environments in the pipeline. You might have conditions that change the ...
Read more >Using workflows to deploy an API to multiple environments
In this tutorial, we will deploy an API to both a staging and production environment. This process is also known as multi-deployment.
Read more >Using Multiple Environments to Improve Your Development ...
Using multiple environments keeps a team productive: Having multiple environments enables a team to work on parallel development efforts. If ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I found your comment while trying to fix a similar issue – I think the fix is described here https://github.com/FirebaseExtended/action-hosting-deploy/issues/143#issuecomment-921789605
It’s possible this is rolled into having multiple deploy domains and works automatically. I never got around to finding out if that was the case.