The latest expert opinions, articles, and guides for the Java professional.

LiveRebel 2.5 released – Continuous Delivery adherents rejoice

Live from JavaOne 2012 in San Francisco, it is our pleasure to announce the release of LiveRebel 2.5!

LiveRebel 2.5 extends version 2.0, the Java industry’s only solution that can instantly  hot-patch apps in production without session loss, and lets operations teams implement Continuous Delivery principles with automated rolling restarts and offline updates.

LiveRebel lets you deploy, update and rollback application versions with dependencies on complex server environments quickly and easily. Everything is automated. Everything is recorded. Everything is tested, and it’s all recoverable with the press of a button. Seriously.

Master your environment with Configuration Scripts

You already know that, more often than not, deploying Java applications require updates to the environment or database tables at certain stages of the update process. LiveRebel 2.5 introduces “Config Scripts” to help you do just that. Consider a simple example:

You’d like to update your relational database schema during an application update. To do so, you simply specify shell scripts to be executed at several stages during the update. You can even package shell scripts inside the application archive (self-contained updates)!

LiveRebel automatically executes scripts based on events that occur during the update process to fulfill dependencies and ensure successful application updates. Use this capability to:

  • Perform smoke tests after the update
  • Update database schema
  • Update static content on proxy
  • Install and configure new services required by the application
  • Trigger other deployments and/or updates

To get started, add the scripts to the application archive, in the “liverebel/scripts” directory. Make sure you put them in subdirectories named as below, based on when you’d like them to execute:

  • init
  • appDown
  • appUp
  • appVisible

For more events, check out the reference. Remember that:

  • Only scripts associated with the version being deployed are executed, so you never need to delete scripts.
  • Scripts can be executed on all machines participating in the update and have access to all information about the update via environment variables, the archive, and the LiveRebel command line.
  • You can roll back updates and the changes made by their associated scripts.
  • As always, you may update to any version of the app.

Keep those patches rolling through the pipeline, without having to manage configuration, database and environment manually. There is more coming soon!

Take on massive production environments

Use LiveRebel 2.5 to confidently update a large number of deployments. It successfully updated 800 Tomcat instances running on one EC2 instance. Further, whenever possible, LiveRebel 2.5 runs actions in parallel. Translation – you can update large artifacts across very large deployments in seconds.

We put time into this owing to significant interest from companies with some of the largest production environments.

More goodies with LiveRebel 2.5

Improved server management – organize application server instances into groups for better overview and easier management. For example, you might want to separate your QA servers from staging servers.

Single Sign-on – LiveRebel authenticates you against your in-house LDAP directory service (including Microsoft Active Directory). Simply put, you no longer need to log into the LiveRebel Command Center with a separate password.

Support for virtual hosts – deploy applications to hosts, virtual or otherwise, spun up by application servers. Update and undeploy applications as well. Support for Weblogic and Websphere to come.

LiveRebel automatic self updates – see new versions in LiveRebel’s Update Center as soon as they are available, and install them with a single click.

Complete visibility into running tasks while you work – Keep tabs on tasks running in the background via the “running tasks” widget while you continue working with LiveRebel, uninterrupted.

Modify application version info – override “application name” and “version” parameters for easier integration with your continuous delivery pipeline, while uploading the archive. Available with LiveRebel GUI, command line, Jenkins, Hudson and Bamboo plugins.

Maintain build audit trails – attach a plain text file to create an audit trail for each application archive you upload to the LiveRebel Command Center. Check out ZT Labs Tutorial: Pragmatic Continuous Delivery with Jenkins, Nexus and LiveRebel to see how you can maintain app version info and audit trails.

Automatically clean up old versions of apps – remove old versions of applications by configuring a cleanup policy, and reclaim disk space.

Finer control with Jenkins/Hudson and Bamboo plugins

In addition to the “deploy” and “update” actions, version 2.5 gives you more control on managing archives. You can now “upload” archives without deploying them, and “undeploy” previously deployed archives, all from Jenkins/Hudson or Bamboo.

Are you waiting for something else?

Download LiveRebel 2.5 now, see the full changelog or request a live demo now! Questions? Write to

Responses (3)

  1. Avatar  


    October 2, 2012 @ 2:09 pm

    Link to event reference seems to be broken?

  2. Avatar  

    Toomas Römer

    October 2, 2012 @ 4:20 pm

    Thanks, fixed now. Was not supposed to link to any specific document.

  3. Avatar  

    Toomas Römer

    October 3, 2012 @ 9:36 pm

    Link fixed now. There was some confusion on our side. I’m deleting my other comment :)

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.