How does DROPS work?

DROPS makes it easy to prepare and deploy your applications and data safely. For this, DROPS uses dedicated repositories secured in the DROPS Server to organize your artifacts and shape and store your releases.

Your company’s processes, roles and access rights, approval and validation requirements, scheduling, and reporting are all managed inside DROPS. Up front, you will define each user’s role(s) in the approval process.

Then deploying an application in DROPS is a 2-step process: configuration (done just once), and execution (recurring tasks).

Step 1. How to CONFIGURE a deployment in DROPS?

To configure a deployment, you’ll need to define what to deploy, where, and how.

Illustration DROPS Importation Artefacts

Releases to deploy to target environments contain artifacts from the artifact repository. A release is created each time a pre-defined import strategy is launched and artifacts from your source location are copied to the artifact repository.

For continuous security in a DevSecOps process, DROPS integrates with Sonatype Nexus IQ to guard against security vulnerabilities in open-source components.

Illustration defining infrastructure items

Once the import is complete, the release is available to be deployed. You can then define infrastructure items to structure your deployment environment and connect to your target machine(s). To deploy to multiple machines, simply group infrastructure items in environments and organize your environments by client.

For the provisioning and instantiation of environments in the cloud, DROPS leverages tools from the major cloud services such as AWS , GCP and Azure.

Illustration Drawing your deployment process

To organize your deployment process, you can draw a fully customizable deployment process diagram together with the actions necessary for your deployment, all driven by ANT scripts. Applications and their components are associated with environments and their individual infrastructure items to make sure the correct artifacts always arrive at their intended destination(s).

Illustration DROPS Planning deployment

Use DROPS pipelines to automate the deployment of an application to multiple environments, either in parallel, or in sequence.

For example, for a given application or application group, you can plan the deployment of a given release across a predefined set of environments (e.g. test, QA, pre-prod, production). The deployment to the ‘next’ environment in the sequence can be either automatic, or conditional on successful execution or on validation by an authorized user.

Checks and balances are taken care of in DROPS using validation requests and suspended actions which automatically pause processes if authorization is required or an error occurs.

DROPS Deployment Process

Step 2. How to EXECUTE a deployment in DROPS?

Once configured, all day-to-day operational tasks such as launching, validating and monitoring deployments are performed from the DROPS Web console.

To create your release, launch a pre-defined import strategy to consolidate release artifacts from various sources in the DROPS repository.

Once a new release has been imported, executing a unitary deployment is simple. From the deployment board, choose an application to deploy, select the target environment and click deploy.

Like many organizations you may deploy across multiple environments, destined for specific purposes, such as test, training, QA and production. Using DROPS pipelines you can configure precisely how your application will be deployed across these environments, in parallel or in sequence, and the conditions for deploying to the next environment in the sequence.

At deployment execution time, for maximal automation, use DROPS “one-click” deploy to combine release creation and deployment across one or more pipelines into one single step.

DROPS enables you to track deployment stages in real time. In addition to providing full deployment logs, it keeps a history of all actions, executions, and transition times.

The option to roll back is always available. Before deployment, actions automatically register a copy of the existing release on your target machine(s) and the infrastructure item backs it up to a rollback directory.

Illustration Request DROPS

Request your demo

Let’s talk about your project!

Release Management Expert

Try it now!

Request a trial version
Release Management Expert

Personalized demo

Ask our Release Management experts