Continuous Delivery with Jenkins and IBM UrbanCode Deploy
summary
Jenkins publishes build artifacts to an artifact repository or directly to IBM UrbanCode Deploy using a Jenkins post-build action plugin; UrbanCode then models applications as components, orchestrates deployments across environments, and captures snapshot versioning so exact component sets move together and rollbacks deploy known-good snapshots. The system uses an agent model for scalable parallel deploys, exposes 130+ plugins to wrap target APIs, and integrates with cloud provisioning via OpenStack patterns and UrbanCode Release for higher-level multi-application release orchestration.
AI-written summary · about
chapters (17)
- 0:00Intro
- 5:47What can go wrong will go wrong
- 9:35What if we had... Intuitive and scalable Model Driven Deploymen
- 11:07Introducing IBM UrbanCode Deploy
- 15:15Applications are made of Components
- 16:21Application Deployment orchestrate Component Deployments
- 19:00Snapshots promote tested versions
- 20:51Application Environment models
- 23:31Putting it all together
- 26:30A look at the integration in Jenkins
- 27:59Other approaches
- 28:20Getting Started with UCD and Jenkins
- 30:01What does UrbanCode Deploy with Patterns do?
- 33:23What is UrbanCode Release?
- 39:07IBM UrbanCode Deploy delivers real results
- 39:58What's next? IT Transformation enabled by automation and hybrid cloud
- 43:11UrbanCode can take us there
related talks
04mContinuous Delivery with Jenkins' New Declarative Pipeline & Artifactory
27mAutomation, Innovation and Continuous Delivery
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
31mSolving Day 2 DevOps Challenges
45mBuilding Your Continuous Delivery Toolkit
42mBuilding Your Continuous Delivery Toolkit
28mDOES14 - Bill Donaldson and Aimee Bechtle - The MITRE Corp- 45mBuilding Your Continuous Delivery Toolkit