Jenkins Build Flow与Workflow(Pipeline)插件 [英] Jenkins Build Flow versus Workflow (Pipeline) plugin
问题描述
我注意到Jenkins至少有两个编排选项
I notice there are (at least) two orchestration options for Jenkins
- Build Flow
- Workflow - Now known as Pipeline
我首先找到Build Flow，并围绕似乎可以满足我们需求的工作实施了编排工作.切换到管道有什么优势?我对切换到管道的想法是
I found Build Flow first and implemented an orchestration job around that which seems to work OK for our needs. Are there any advantages to switching to Pipeline? My thoughts for switching to Pipeline are
- Pro-该项目似乎比Build Flow更为活跃
- Con-DSL似乎要复杂得多
推荐答案
管道/工作流基于Build Flow插件中的概念.根据此处的Wiki注释: https://wiki.jenkins-ci. org/display/JENKINS/Build + Flow + Plugin 似乎管道是Build Flow的未来.我知道，事实上，管道被Cloudbees视为Jenkins 2.0的一项核心战略计划，并且将是向前发展的前沿和中心计划.
Pipeline / Workflow is based off concepts from the Build Flow plugin. Based on the wiki notes here: https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin it would seem like Pipeline is the future of Build Flow. I know for a fact that Pipeline is considered a a core strategic initiative for Jenkins 2.0 by Cloudbees and will be a front and center initiative going forward.
https://wiki.jenkins-ci.org/display/JENKINS/詹金斯+2.0
简而言之，我将移至管道"以位于曲线的前面.
In short, I would move to Pipeline to be ahead of the curve.
这篇关于Jenkins Build Flow与Workflow(Pipeline)插件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
