Browse Prior Art Database

Automated Cleaning and Preservation of Devops Pipeline Test Environments

IP.com Disclosure Number: IPCOM000241277D
Publication Date: 2015-Apr-13
Document File: 1 page(s) / 39K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a solution for automated cleaning and preservation of devops pipeline test environments. The method performs cleaning in two stages, immediately deleting resources that are no longer needed, but providing a grace period for potentially needed environments before cleaning.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 01 of 1

Automated Cleaning and Preservation of Devops Pipeline Test Environments

Every time the pipeline runs (e.g., twice a day), dozens of resources are requested from the cloud to use for testing. Managing the life of these resources is a difficult balance. It is costly to keep all the environments online for very long, but removing the environments too soon prevents debugging of test or infrastructure failures. Because of the scope, manually cleaning unneeded environments is not feasible.

Most cloud platforms provide mechanisms to automatically clean resources. A typical method is to automatically delete resources that have been online longer than a certain threshold unless explicitly preserved. This approach can contain overall resource usage, but keeps many unneeded environments online.

Some virtual machine (VM) software has automation that reclaims inactive resources. This provides effective and proactive cleaning, but it does not solve the overall problem because when an issue needs to be analyzed, the system needs to sit inactive until a developer can connect and debug.

The proposed solution is to perform cleaning in two stages immediately deleting resources that are no longer needed , but providing a grace period for potentially needed environments before cleaning.

The basic steps are:


1. Create environment


2. Set expiration date on the environment


3. Run tests


4. If tests pass, delete environment immediately


5. Delete expired environments

1