59 lines
1.8 KiB
Markdown
59 lines
1.8 KiB
Markdown
---
|
||
title: "Jenkins"
|
||
type: entity
|
||
tags:
|
||
- CI/CD
|
||
- Automation
|
||
- DevOps
|
||
sources:
|
||
- ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments
|
||
last_updated: 2026-04-29
|
||
---
|
||
|
||
# Jenkins
|
||
|
||
## Overview
|
||
|
||
Jenkins 是最广泛使用的开源自动化服务器之一，在 IaC 场景中曾被用于执行 Terraform 部署流水线。然而在 Atlantis 的对比中，Jenkins 流水线暴露出多个运维痛点。
|
||
|
||
## In This Context
|
||
|
||
**[[ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments]]** 指出原 Jenkins 流水线存在以下问题：
|
||
|
||
### Speed Issues
|
||
- 显著的初始化时间（每次构建需重新初始化环境）
|
||
- 多次代码克隆（每个 stage 重复克隆仓库）
|
||
- 顺序测试（无法并行化，瓶颈明显）
|
||
- ECS Deployer 预配置耗时
|
||
|
||
### Complexity Issues
|
||
- 持续叠加功能以覆盖更多场景和边缘情况
|
||
- 架构脆弱，易产生配置漂移（drift）
|
||
- 维护成本高，改动风险大
|
||
|
||
## Contrast with Atlantis
|
||
|
||
| Aspect | Jenkins | Atlantis |
|
||
|--------|---------|----------|
|
||
| Trigger Method | Push (pipeline job) | Pull (PR comment) |
|
||
| Plan Timing | Pre-merge testing | Pre-merge apply |
|
||
| Module Locking | Requires plugin/config | Built-in automatic |
|
||
| Parallel Builds | Configurable, complex | Native support |
|
||
| Setup Complexity | High (many integrations) | Low (single EC2) |
|
||
| Cost (VPC Endpoints) | High | Low (removes many endpoints) |
|
||
|
||
## Aliases
|
||
- Jenkins CI
|
||
- Jenkins Server
|
||
|
||
## Related Concepts
|
||
- [[CI/CD Pipeline]]：Jenkins 和 Atlantis 都属于 CI/CD 工具范畴
|
||
- [[GitOps]]：Atlantis 更贴近 GitOps 理念，Jenkins 为传统 Push 模型
|
||
- [[Infrastructure as Code (IaC)]]：两者均可用于 IaC 部署
|
||
|
||
## Related Entities
|
||
- [[Atlantis]]：在 IaC 部署场景下替代 Jenkins 的方案
|
||
|
||
## References
|
||
- [[ctp-topic-32-using-atlantis-cicd-for-infrastructure-deployments]]
|