Radha Kiwalkar

August 11, 2021

Chances are, you have a rapidly iterating application, and it’s updated frequently as your team builds new features for your customers. To scale constant, agile innovation, ​​you need a defined static method for rolling out new application versions to your large and potentially varied device fleet. 

With Esper Pipelines, you can easily configure your device fleet workflow. You can configure your deployment flow once. Then, each time you can define a job that’s specific for each app update. This DevOps process enables the completion of actions (such as sending updates and security patches) by providing a way to automate them. 

Using CI/CD Pipelines, you will define the stages through which the actions must be completed and the events that trigger each of those stages. For example, Pipelines can push application updates to the targeted devices after first testing with a small set of devices, reducing the potential for failure.

Advantages of Building Pipelines on the Esper Console

  • Esper Pipelines allows version control. You can also choose the application version to install on the fleet of devices, providing you flexibility over your deployment process. On the Console, navigate to Pipelines > New Pipeline. Click Add Operation to specify the application and version to deploy to the device or group.

  • CI/CD Pipelines orchestrate secure and automated deployments of your application using configurable stages, allowing the execution even without a dedicated technical team. On the Console, once you’ve created a Pipeline, click Add stages to create a new stage. You can create up to 5 stages from the Console.

  • Esper Pipelines allow a phased approach — meaning you can control how an application update or new application is installed onto your fleet, which minimizes the risk of job execution. You’ll have the same application and the version selected for each stage but an incremental set of devices chosen for targets. For each stage, you can add devices under Targets on the Console.  

    For example, ‘Test lab’ devices will be your targets for the first stage. A batch of devices at a smaller location managed by headquarters, the locations in the area next to headquarters can be the targets for the following 2 stages. You can pick a local region for stage 4, and the final stage will be nationwide.
  • DevOps Pipelines ensure an enterprise-ready deployment. Pipelines guarantee the speed and reliability you need when building, testing, and deploying code. With incremental stage deployments, you can monitor failure early, resulting in a confident release. 

    Esper Pipelines give you a comprehensive status update in real-time. Once a Pipeline is running, click View Run to get a clear picture of the deployments. This report helps to quickly identify successful deployments, promote them to the next stage, identify failures, and terminate the execution.

You can find the documentation on Pipeline here. Watch out for the following blog on the execution of Pipelines via API. In the meantime, please reach out to the Esper team if you have any questions.