Developers use awesome processes, project management tools and CI servers (such as Jenkins) to coordinate tasks and quickly integrate changes into app feature branches or the trunk. But building applications is only half the job to be done.

Releasing apps through QA, production and to your users can be repetitive, but it takes care and finesse. Often, this means running scripts to provision and configure servers, deploy artifacts, copy files over, update databases, and run tests in a specific order. The problem is that this is often done manually, which is error-prone; and if you make a mistake, your app and users are dead in the water. No fun!

Just Released: All-New LiveRebel Plugin for Jenkins

Automatically deploy apps straight from Jenkins with zero downtime. Failed deployments are fully reversed. Your users won’t feel a thing. The LiveRebel plugin for Jenkins integrates Jenkins with your LiveRebel installation. It helps you automate safely and take control of release processes that can otherwise be tediously repetitive and error-prone. Since users are not disrupted, you can push app updates frequently and during business hours a.k.a. practice continuous delivery. LiveRebel’s plugin for Jenkins can:

Get staged, zero-downtime app updates. LiveRebel updates servers in stages using a rolling restart approach, so that users are not interrupted. Let LiveRebel run test scripts that you provide, at the end of each stage.

Achieve failsafe deployments with rollback. If deployments or tests fail, LiveRebel automatically rolls back changes to the app, database and configuration. Users are fully shielded from deployment failures.

Fully automate the release pipeline! By integrating Jenkins and LiveRebel using the latest plugin version, engineers can fully automate releases with all the necessary tests and processes in place.

How can you revert database changes, if smoke test fails? Data is commited, DDL operations finished.

Krishnan Badrinarayanan

Hey Leos – LiveRebel has built-in version control for databases and can rollback changes if a deployment were to fail. But, if the changes were destructive (such as dropping tables, etc.) LiveRebel will not be able to restore them. If this were the case, LiveRebel will warn you before you initiate the deployment.