Continuous Delivery is a frequent topic here on the ZeroTurnaround blog. No surprise, right? Many of you are already sold on the idea, and lots of you are putting it into practice already. But others may be reading these posts thinking “Continuous delivery sounds wonderful, but my hurdles are so many and so high, I wouldn’t even know how to start! Lemme go kick off a rolling-restart-fueled hot-patch just to bring me out of my dispair and back into my happy place.”
Sound familiar? If so, then read on.
Software plays an increasing part in helping us get things done. We not only expect it to satisfy our rapidly changing needs, work 24/7 and perform well, but also evolve and improve in advance of our expectations. These days, the best software teams release products and features faster and more frequently, while striving to raise the bar on quality. But managing consumer demands with the increasing complexity in how software is released and delivered is not easy.
Update Java Apps and dependencies without hassles
LiveRebel is a Continuous Delivery tool that helps you take Java apps to users faster. It instantly deploys apps across the QA and production environments in cloud, virtual or physical servers, and it does it all with zero downtime and no session loss, making LiveRebel unique in the market.
A Java application rarely consists of just Java code. It includes multiple interdependent components – a database, JMS, other dependent applications, native libraries, resources in a CDN and so on. The point is, regularly deploying these apps manually can be cumbersome for operations teams – why not automate the process, recording each step along the way with an audit trail?
For this reason, the LiveRebel team at ZeroTurnaround wanted to introduce Configuration Scripts (aka “Config Scripts”), an intelligent feature that helps you automate the deployment of your Java app and its dependencies using any of your existing deployment scripts from a single viewpoint.
I was brainstorming in the shower the other day, and I thought “Eureka!” – I need to bootstrap and test my Java app on a dynamic cluster with 800 Tomcat servers right now! Then, breakfast.
Obviously, every now and then you need to build a dynamic cluster of 800 Tomcat machines and then run some tests. Oh, wait, you don’t? Well, lets say you do. Provisioning your machines on the cloud for testing is a great way to “exercise” your app and work on:
- Warming up: Bootstrap a clean slate, install the software, run your tests
- Checking your Processes: Smoke testing for deploying the app to production
- Ensuring success: Checking load handling before launching the application to real clientelle
- Leaving nothing behind: After you’ve got all green lights, shut it all down and watch it disappear
It’s time for another issue of ZeroTurnaround GeekNews. This update covers all the cookies and cream from April to June of 2012. See what you missed!Read more
I wanted to post this inquiry from our ZeroTurnaround Support Forum because it brings up a great feature of LiveRebel that we often show during LiveRebel demos – the compatibility check feature you can use to ensure your live app hotpatch will do what is intended.Read more
Jenkins is a continuous integration tool that is very often used as a orchestration tool for continuous deployment and delivery. Today, we will look how to do artifact propagation in a Jenkins pipeline for Continuous Delivery. Some of questions I’m thinking about are:
So what’s the Problem with Application Configuration Management anyway?
You know how when you are trying to deploy an application to another environment, and then it starts to suck because somehow you end up with the wrong version of the configuration or the configuration values are for a different environment altogether?Read more