Pragmatic Continuous Delivery with Jenkins, Nexus and LiveRebel
Despite the best attempts of Dev/Ops fan meetups and IT gurus keen to offer their view on Continuous Delivery/Deployment, a recent survey on Production Deployments shows that the vast majority of organizations’ deployment pipelines still rely heavily on manual processes – which, of course, tend to be prone to human error, inconsistencies and generally move things out the door a lot slower.
In this 22-page tutorial and accompanying video presentation, you’ll be guided step-by-step into building a Continuous Delivery pipeline for real uses case in a realistic environment – using tools like Jenkins, Nexus, LiveRebel and others readily available right now.
Why think about Continuous Delivery when we already have a working deployment pipeline now? It’s worthwhile to understand the philosophy of the Continuous Delivery (hereinafter “CD”) methodology, which we feel can be broken down into 4 simple parts:
- Automate. Humans suck at doing anything repetitive.
- Record. No action can happen without some kind of a trail.
- Test. Monitor & test from Development all the way to Production.
- Recover. Plan for failure and prepare for recovery.
This philosophy is incorporated in the central concept of CD: the automated pipeline leading from development all the way to production.
Register or Log in above to read the full report!