如何按需运行容器化的Bamboo远程代理? [英] How do I run a containerized Bamboo remote agent on demand?

问题描述

我们目前将多个Linux系统配置为我们Bamboo项目的静态专用远程代理，并且希望转而使用按需启动的容器化远程代理.如何才能做到这一点?我看到了一个容器化的远程代理，但是它去哪里了?

We currently have multiple Linux systems configured as static dedicated remote agents for our Bamboo project and want to move to using containerized remote agents that are spun up on demand. How can this be done? I see a containerized remote agent but where does this go?

我们已将构建环境容器化，但是远程代理仍在专用硬件上运行.我们要删除所有专用的远程代理计算机，并在容器中运行所有内容.我是无法访问服务器的最终用户，所以不确定如何实现此目的.从我看过的内容中可能看不到云，所以猜测一个本地群集吗?这个概念的新手.

We have containerized our build environment but the remote agent is still running on the dedicated hardware. We want to remove all our dedicated remote agent machines and run everything in containers. I'm an end user with no access to the server so not sure how I can accomplish this. From what I've read probably not in the cloud so guessing an on-prem cluster? New to this concept.

推荐答案

Bamboo为此提供了一个per-build_container插件.将集群指定为配置的一部分，并且在构建作业中指定了容器化的远程代理(sidekick)，并在作业开始时启动.根据文档，这可以是AWS ECS，Docker集群或Kubernetes.

Bamboo provides a per-build_container plug-in for this. The cluster is specified as part of the configuration and the containerized remote agent (sidekick) is specified in the build job and spins up with the job starts. Based on documentations this can be AWS ECS, Docker cluster or Kubernetes.

这篇关于如何按需运行容器化的Bamboo远程代理?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！