Why You Shouldn't Run Business Applications with a Build Tool

on YouTube ↗28m

" summary

Argument: don’t use a build tool (Jenkins/SBT) as your production orchestrator; use domain-specific orchestration that can be treated as jobs as code. Example platform Control-M validates JSON/Scala orchestration in an IDE, runs tests against a virtual appliance and EMR cluster via REST, and integrates into Jenkins pipelines with Robot tests. Results: PayPal moves from days/weeks to self‑service delivery, Amadeus runs workloads across mainframe, private and public clouds for seamless portability.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 1:59Business Service Orchestration
3. 16:18Run a Test
4. 17:33Ownership Conflict
5. 20:57The Benefits of a Ci Cd Approach

" related talks

• 45mBuilding Your Continuous Delivery ToolkitAndrew Phillips · Jenkins User Conference US West (JUC San Francisco) 2014
• 05mYou scream for microservices orchestration; I scream for batch...Joe Goldberg · O'Reilly Velocity Conference 2017 - New York, New York
• 08mLightning Talk: Thinking out of the CI/CD Toolbox: An Experiment with a Workflow En...Nele Lea Uhlemann · cdCon 2022
• 53mChange your tools, change your outcomeNic Williams · RubyConf 2012
• 34mWorkflow Orchestration Embedded in your DevOps Tool ChainAlon Lebenthal · DevOps Pro Europe 2019
• 45mBuilding Your Continuous Delivery ToolkitAndrew Phillips · Jenkins User Conference San Francisco 2014
• 30mQA in DevOps: Transformation thru Automation via JenkinsTanya Kravtsov · Jenkins User Conference U.S. East 2015
• 33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool ChainCurtis Yanko · Jenkins User Conference U.S. East 2015