TOP!!! When will you provide this feature?
This feature is live now for anyone who signs up for early access: https://confluence.atlassian.com/bitbucket/pipelines-alpha-8...
Atlassian announces Bitbucket Deployments: Confidence to release early and often
11–20 of 29 posts
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#12Will there be support for deployments to a (test) environment per branch?
In the early release, it's not possible: the 3 default environments are at the moment just for the repository, not per branch. You can deploy from multiple branches to the same environment though. Can you elaborate on why this would be helpful for you?
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#13When will you provide this awesome feature?
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#14Will there be support for deployments to a (test) environment per branch?
In the early release, it's not possible: the 3 default environments are at the moment just for the repository, not per branch. You can deploy from multiple branches to the same environment though. Can you elaborate on why this would be helpful for you?
Branch-specific test environments would allow regression testing to happen _before_ changes get merged (I've used Travis to do this). I would love to have this kind of test isolation in our CI environment.
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#15Will there be support for deployments to a (test) environment per branch?
You can do this already in Bitbucket Pipelines and your preferred PaaS provider -- just set up a manual step on your branch pipeline to deploy it. We built Deployments to help teams track changes in their _shared_ environments, which is where most of the value for tracking is.
Who would want to see a history of deployments for a branch-specific environment? What information would they be looking for?
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#16My main pain point with deployment is with servers that are not directly accessible from the Internet. For example, an EC2 instance that sits in a private section of an AWS VPC. Accessing the server is done through a Bastion server/Jumpbox. AWS CodeDeploy is the only solution I've found in this environment and it sucks. Can the new system ssh proxy through a Bastion server?
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#17I'd like to see a mechanism to coordinate deployment dependencies - if the front-end and back-end(s) are stored in separate repos it may be necessary for the back-end to be upgraded before deploying the new front-end.
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#18How are roll-backs performed? Can a roll-back be executed automatically if smoke tests fail?
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#19Nice move, Atlassian, linking directly to this post from the promo email.
That's why im here :)
Re: Atlassian announces Bitbucket Deployments: Confidence to release early and often
#20Cool feature! I will be pushing this into our pipline scripts this week.
I'm pleasently surprised that bitbucket-pipelines has actually worked this well. So well that we have turned off our Jenkins server.
Nice work, atlassian!