Atlassian announces Bitbucket Deployments: Confidence to release early and often

Re:Atlassian announces Bitbucket Deployments: Confidence to ... by geoandrew on Tuesday December 05, 2017 @05:13PM (#15856535)

My 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?

[ Parent | on HN ]

Re:Atlassian announces Bitbucket Deployments: Confidence to ... by mryall on Tuesday December 05, 2017 @09:41PM (#15858081)

Yes, you can set up SSH keys to connect to your jumpbox from Bitbucket Pipelines: https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-b...

At the moment, direct access to your Amazon resources requires an access key configured via secure variables in Pipelines. We'd consider adding support for IAM roles/key rotation if a lot of people would find it useful.

[ Parent | on HN ]

Re:Atlassian announces Bitbucket Deployments: Confidence to ... by natbobc on Wednesday December 06, 2017 @10:39AM (#15861876)

Would be useful for stuff like;

- kubernetes - elastic beanstalk

I'm currently using the "custom" section with a plugin I developed to deploy to environments. In the default build it pushes the build to Elastic Beanstalk and then deploys to test. The custom builds merely promote the build for other environments.

[ Parent | on HN ]