Bamboo OnDemand build + local deploy

[Vincent Kellers da Silveira]

Hello,

I would like to check whether Bamboo OnDemand supports the following scenario:

1. Build my application using maven in Amazon EC2

2. Deploy the built application in my servers, which are hosted locally in my company, not in the cloud

As per my research (https://answers.atlassian.com/questions/32813/jira-ondemand-with-standalone-download-local-bamboo and https://studio.atlassian.com/browse/JST-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#issue-tabs) step 2 is not possible, but I would like to double check anyway.

If the above scenario is not achievable using Bamboo OnDemand, I would like to check whether it is possible to provide a link to the artifacts resulting of the latest stable build. This link should not depend on version number, since (ideally) it would be used by scripts that would download the artifacts and then execute the deploy.

Thanks in advance.

[ReneR · Accepted solution]

This is certainly within the realm of possibility.

Bamboo-wise, you'll need a custom AMI.

http://confluence.atlassian.com/display/BAMBOO/Creating+a+Custom+Elastic+Image

Any EC2 instances you create from that AMI will have access to any of the functionality AWS provides. One of those features, for example, let's you create a hybrid VPN network between AWS and your datacentre:

http://aws.amazon.com/vpc/faqs/#C6

So you configure the custom Bamboo AMI with the security group for your VPN and in your build plan you just setup a Job to do the deployment (as if the Bamboo agent was in your own datacentre) via ssh, scp or whatever other means of automation you would use in your own datacentre.

Since you're using Maven, you can definitely use an artifact repository manager like Nexus that's setup in your datacentre and which you can provide a public access URL for or setup via the VPC. Setup a user for the bamboo builds and hide the encrypted settings.xml in your custom AMI. Any Jobs can then push artifacts into your repository via the normal maven-deploy methods.

You could also setup a Nexus repository manager inside EC2 on a dedicated instance that you can, again, reach from your custom AMI. Then setup a Nexus proxy in your data centre that can replicate artifacts back and forth from AWS.