Use docker containers as/instead-of elastic instances for bamboo

[s2zaman]

Bamboo launches an elastic-docker-container, instead of launching an elastic-instance

It would be great to have this idea implemented in future. Because the containers launch too fast as compared to an instance.

and i think this would be a great good solution for issues like
https://jira.atlassian.com/browse/BAM-12459 and https://jira.atlassian.com/browse/BAM-13111 

[Dana Cleveland]

Have you seen this? Is this what your looking for?

Per-build Container (PBC) Bamboo Agents

Set of plugins for Atlassian Bamboo. Allows running builds and deployments on Bamboo agents in Docker clusters like Docker Swarm, Kubernetes and AWS ECS. Tools and services for the build defined as Docker images.

Each execution of a Bamboo job or deployment environment will run on a newly created remote agent that will contain exactly the tools needed for the job, run it and then destroy itself. Services as Selenium, databases or Docker can be defined as extra containers that the build can interact with.

https://bitbucket.org/atlassian/per-build-container

[s2zaman]

@Dana Cleveland Let me have a look at the resources you provided.

[s2zaman]

@Dana Cleveland , it seems great to me.

Thanks for sharing the useful source.

[ranjitrajan]

You can have a bamboo agent running on the Orchestrator which can use your docker image and based on placement constraints deploy the image on the node where the cluster manager schedules and run the build. There is no need of any additional plugin in such a case.