Hi @Rakesh Yadav How are you doing?
Bamboo agent could be read as Directly on Bamboo agent. All of the tasks (like getting the source code, calling Maven etc.) will be done by your Bamboo Agent.
Docker would be read as In a Bamboo Agent that will create a container and run this Job inside it. An agent with the Docker capability will create a container based on the image you informed, run your tasks inside this container and destroy the container in the end.
Although the first option looks lighter, the second one solves a few issues you could have in a larger environment, for example:
- Isollation of resources; when we run many agents in the same machine and of them takes all CPU, the builds running in other agents will be affected. When you use docker, it takes only the CPU allocated to that container.
- Isollation of dependencies: when we run many agents in the same machine and build different applications on it, you will have to install all the dependencies for all the applications in the same machine (sometimes it is not even possible). Using docker, you could use different images for different applications, having only the necessary dependencies for each and, so, avoiding conflicts.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.