Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
Currently the deployment enviroments are static. You have to setup them and name them. Only then you can use deployment functionality in Bitbucket Pipelines.
That does not scale very much when using automatic testing enviroment per branch or pull request. For example we have containerized testing enviroment for each branch (eg. http://internal.company.com/feature/JIRA-1234-introduced-dynamic-deploy-env). Each branch has its own testing enviroment so it can be easilly tested before the pull request gets merged. I believe this is a pretty common work flow and it should be supported by Bitbucket.
I would like to have dynamic deployment enviroments, so I dont need to setup them ahead. So I could do something like following:
- step:
name: Deploy branch
deployment: ${BITBUCKET_BRANCH}
script:
- echo "Deploying...";