{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 劫难 的问题《Jenkins Build Flow versus Workflow (Pipeline) plug》','https://www.manongdao.com/q-768188.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I notice there are (at least) two orchestration options for Jenkins
- Build Flow
- Workflow - Now known as Pipeline
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 - The project seems more active than Build Flow
- Con - The DSL seems much more complex
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/Jenkins+2.0
In short, I would move to Pipeline to be ahead of the curve.
Build Flow is the predecessor of Pipeline. Pipeline is more complex and more powerful (flexibility, features, integrations, etc).