Please welcome JRebel 6.1.3. Our newest release is filled with multiple improvements and updates, both within the plugins as well as on the agent side.
The latest expert opinions, articles, and guides for the Java professional.
It’s an exciting time for the LiveRebel team–we released LiveRebel 3.1 a few days ago and so far nothing has broken! Kidding aside, releasing software is a difficult task, and that why we built LiveRebel: so that any size software shop could afford out-of-the-box continuous delivery with multi-platform deploys, release orchestration, zero downtime rollouts and automated rollbacks.
5 reasons it’s silly to use awesome provisioning tools like Chef, Puppet and Ansible to release applications
We love the concept of “infrastructure as code” and the tools that go with it. Chef, Puppet, Ansible, CFEngine and others have transformed the way we manage tens, hundreds or even thousands of nodes today. Provisioning tools have really been a great value-add to the world of software, and this widespread adoption of the paradigm illustrates the key strength of those tools: simplicity.
Unfortunately, when we have a tool close at hand that we love, we tend to overuse it for problems it wasn’t really designed to solve. Releasing your applications using Provisioning tools (instead of Release Management tools) is like moisturizing your face with bacon drippings instead of fancy lotion; you might love bacon nectar, but it’s simply not appropriate for use in all situations.
As developers, we should be shaping the world, not waste time on process issues that automation, provisioning and release management tools can solve easily.
So, you’ve been coding away for months on a big project, and you can’t wait to share what you’ve created with the world. All the functionality is there, your test coverage is great and every demo you’ve shown ends in a complete success with love at first sight….
But wait–what if it totally breaks in production? That would suck, obviously. But what are we as developers supposed to do about what happens in production? Isn’t that the job of the sysadmin or release engineer or whatever that person is called who….well…does all that stuff with apps in production? (Hmmm, what DOES that dude do? Maybe you should figure that out!)
We’re incredibly relieved to announce an uneventful release of a major upgrade–LiveRebel 3.0 ;-) This release brings a number of enhancements that we’re freakin’ excited to tell you about–which we will do during a live webinar on Jan 30th. For those of you who aren’t familiar with LiveRebel…
LiveRebel is our deployment automation suite that releases Java, .Net, PHP, Python, Ruby and Perl applications with zero downtime, complete with your database and configuration changes. If anything goes wrong, the failed rollout is automatically reversed before users can be impacted.
Existing customers can easily upgrade using this migration guide to make the transition from previous versions as smooth as possible.
Ah, DevOps, the biggest WTF buzzword among the innovators in software development and deployment today. It’s as hot a topic as agile was a decade ago, but just like agile, no one was able to really lock down a good enough definition, or figure out the context in which the definition of Agile actually existed (at first).
State of the art in deployment automation doesn’t look very artsy. Popular tools, like Fabric or Capistrano, just let you execute scripts in a fancy way. But LiveRebel is different: instead of scripts, it talks in terms of applications, servers and the deployment process in general. And with the addition of general file-based deployments in LiveRebel 2.6, applications on any platform can enjoy the domain-driven mindset…
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?