blocks|key|3487656|text|最好的方法是在EC2上运行。我建议你使用terraform来构建你的环境，因为你可以编写代码，也可以控制它的版本。https://www.terraform.io/downloads.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3487657|entityMap|0|LINK|mutability|MUTABLE|url|https://www.terraform.io/downloads.html^0|1L|13|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Best way would be running on EC2. Make sure you have granular control over your instance Security Group and Network ACL's. I would recommend using terraform to build your environment as you can write code and also version control it. <a href="https://www.terraform.io/downloads.html" rel="nofollow noreferrer">https://www.terraform.io/downloads.html</a>

blocks|key|1171796|text|你以前有没有把你的Jenkins装在集装箱里？在VMWare本身？如果没有，如果你没有使用容器的经验，那就去找EC2吧。它将与在任何其他虚拟机上运行一样简单。要再现基础设施，请使用Terraform或CloudFormartion。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1171797|我建议您首先对接您的本地Jenkins。了解在实现和管理/扩展它方面需要多大的努力。那就去ECS吧。|1171798|否则，转到EC2，看看有多少管理费用%2B您的账单。然后，如果需要，转到ECS。|1171799|您必须考虑的另一点是您的Jenkins是如何架构的。你用的是主从模式吗？您是否在争议性地运行构建，以便VM永远不会空闲？您是否希望轻松扩展，以便在每次构建执行时创建和销毁构建环境？|1171800|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Have you previously containerized your Jenkins? On VMWare itself? If not, and if you are not having experience with containers, go for EC2. It will be as easy as running on any other VM. For reproducing the infrastructure, use Terraform or CloudFormartion.

I would recommend dockerize your on-premise Jenkins first. See how much efforts are required in implementation and administrating/scaling it. Then go for ECS.

Else, shift to EC2 and see how much admin overhead + costs you are billed. Then if required, go for ECS.

Another point you have to consider is how your Jenkins is architected. Are you using master-slave? Are you running builds contentiously so that VMs are never idle? Do you want easy scaling such that build environment is created and destroyed per build execution?

blocks|key|1187976|text|如果您没有运行容器的经验，那么可以在EC2上创建它。在ECS上运行之前，请确保您真正了解容器和容器编排。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1187977|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have no experience with running containers then create it on EC2. Before running on ECS make sure you really understand containers and container orchestration.

blocks|key|4956955|text|我只想通过提供官方AWS白皮书的链接来补充其他答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4956956|4956957|Jenkins+on+AWS|unordered-list-item|offset|length|4956958|4956959|它可能会特别有趣，因为它详细讨论了这两个选项:+EC2和ECS：|4956960|4956961|在本节中，我们将讨论部署Jenkinson+AWS的两种方法。首先，您可以使用亚马逊弹性计算云(Amazon+EC2)上的传统部署。其次，您可以使用利用Amazon容器服务(Amazon+)的容器化部署.Both方法是企业环境的生产就绪。|blockquote|style|BOLD|4956962|4956963|4956964|AWS+for+ECS上还有针对Jenkins的AWS示例解决方案：|4956965|4956966|https://github.com/aws-samples/jenkins-on-aws：|4956967|4956968|4956969|此项目将使用在亚马逊网络服务中构建和部署一个不可变的、容错的、经济高效的Jenkins环境。所有Jenkins镜像都在存储库中进行管理(从上游提取)，并且完全可以配置为代码。插件安装是自动化的，包括版本控制，以及通过配置为代码插件进行配置。|4956970|4956971|entityMap|0|LINK|mutability|MUTABLE|url|https://d1.awsstatic.com/whitepapers/DevOps/Jenkins_on_AWS.pdf|1|https://github.com/aws-samples/jenkins-on-aws^0|0|0|0|E|0|0|0|0|0|1J|3|36|5|0|0|0|0|Y|0|0|0|1A|0|19|1|0|0|0|0|3C|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|1E|8|@]|9|@$F|1F|G|1G|1|1H]]|A|$]]|$1|H|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1J|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1L|8|@$F|1M|G|1N|O|P]|$F|1O|G|1P|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1S|8|@$F|1T|G|1U|O|P]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|V|3|W|5|E|7|1W|8|@$F|1X|G|1Y|O|P]]|9|@$F|1Z|G|20|1|21]]|A|$]]|$1|X|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|Z|3|10|5|N|7|24|8|@$F|25|G|26|O|P]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|28|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]]]

Just want to complement the other answers by providing link to official AWS white paper:

<ul>
<li><a href="https://d1.awsstatic.com/whitepapers/DevOps/Jenkins_on_AWS.pdf" rel="nofollow noreferrer">Jenkins on AWS</a></li>
</ul>

It might be of special interest as it discusses both options in detail: EC2 and ECS:

<blockquote>
 In this section we discuss two approaches to deploying Jenkinson AWS. First, you could use the traditional deployment on top of Amazon Elastic Compute Cloud (Amazon EC2). Second, you could use the containerized deployment that leverages Amazon EC2 Container Service (Amazon ECS).Both approaches are production-ready for an enterprise environment. 
</blockquote>

There is also AWS sample solution for Jenkins on AWS for ECS:

<ul>
<li><a href="https://github.com/aws-samples/jenkins-on-aws" rel="nofollow noreferrer">https://github.com/aws-samples/jenkins-on-aws</a>: </li>
</ul>

<blockquote>
 This project will build and deploy an immutable, fault tolerant, and cost effective Jenkins environment in AWS using ECS. All Jenkins images are managed within the repository (pulled from upstream) and fully configurable as code. Plugin installation is automated, including versioning, as well as configured through the Configuration as Code plugin.
</blockquote>

Currently we have Jenkins that is running on-premise(VMware), planning to move into the cloud(aws). What would be the best approach to install Jenkins whether on ec2 or ECS?

Jenkins setup on EC2 vs ECS

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

目前，我们有Jenkins正在运行内部部署(VMware)，计划迁移到云(Aws)。无论是在ec2上还是在ECS上，安装Jenkins的最佳方法是什么？

问EC2与ECS上的Jenkins设置
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问EC2与ECS上的Jenkins设置EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问EC2与ECS上的Jenkins设置
EN