Import Continuous Delivery

on YouTube ↗37m

" summary

A concrete pipeline moves a Maven build through repositories and environments using Jenkins orchestrates to trigger jobs, Nexus to store snapshots and promote artifacts, and LiveRebel to deploy to two Tomcat nodes behind a load balancer so production shows exactly which revision runs. The final promotion is manual so this is continuous delivery not continuous deployment, tests and schema migrations are mostly omitted in the demo, and rollback comes via LiveRebel or by promoting a fixed release candidate.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 2:04JAVA EE
3. 2:18QUESTIONS?
4. 4:01SOFTWARE FAIL
5. 4:19KEY PROBLEMS
6. 7:23KEY FEATURES
7. 35:40CONCLUSIONS

" related talks

• 32mContinuous Delivery as a ServiceFolkert Schram de Jong · J-Fall 2015
• 24mWhy, What, and How of Continuous DeliveryKohsuke Kawaguchi · swampUP 2017
• 01h 29mBuilding a Continuous Delivery Pipeline with Gradle and JenkinsPeter Niederwieser · SpringOne2GX 2014
• 59mJenkins & continuous delivery pipelineJean-Philippe Briend · DevFest Nantes 2016
• 42mCONTINUOUS DELIVERY FOR RUBYISTSMichał Knapik · Grill.rb 2017
• 27mAutomation, Innovation and Continuous DeliveryMario Cruz · Jenkins User Conference US West (JUC San Francisco) 2014
• 38mContinuous Delivery, or the magic button for on‑demand releasesDenis Yakovlev · HighLoad++ 2014
• 38mContinuous Delivery with a Microservices ArchitectureMichael Pigg · Jenkins User Conference U.S. East 2015