Method and system for implementing safe deployment of features

Patent metadata

Field	Value
Publication number	US-12175234-B2
Application number	US-202218072450-A
Country	US
Kind code	B2
Filing date	Nov 30, 2022
Priority date	Nov 30, 2022
Publication date	Dec 24, 2024
Grant date	Dec 24, 2024

Abstract

A method of and system for implementing a safe deployment of a first feature in a computing environment is carried out by receiving registration information for the first feature, the registration information including a second feature on which the first feature depends or a feature type on which the first feature depends. Based on the second feature or the feature type, a target build version that meets dependency requirements of the second feature or the feature type is then identified before obtaining a list of build versions for a plurality of computing devices in the computing environment. From among the plurality of computing devices, one or more computing devices that have build versions that meet the target build version are then identified before marking the identified computing devices as being available for deployment of the feature and advancing deployment of the feature to those computing devices.

First claim

What is claimed is:

1. A data processing system comprising:
a processor; and
a memory in communication with the processor, the memory comprising executable instructions that, when executed by the processor, cause the data processing system to perform functions of:
receiving information about a first feature of a software application, comprised of a code change and/or a configuration update to the software application, the first feature being a feature that has become available for being deployed as a feature of the software application in a computing environment, the information received including feature dependency information, wherein the dependency information indicates a dependency requirement for the first feature upon a second feature of the software application in order for the first feature to operate in the software application;
identifying, based on the dependency information, a target build version of the software application that meets the dependency requirement for the first feature;
determining, using a machine learning model, that a computing device meets the dependency requirement for the first feature in the target build version;
upon determining that the computing device, in which the software application is stored, meets the dependency requirement for the first feature in the target build version, attributing a tag to the computing device, the tag identifying the computing device as being available for deployment of the first feature to the computing device; and
advancing deployment of the first feature to the software application in the computing device to provide the code change and/or the configuration update to the software application in the computing device based upon the tag identifying the computing device as being available for deployment of the first feature to the computing device.

2. The data processing system of claim 1 , wherein the dependency information includes a feature type on which the first feature depends.

3. The data processing system of claim 2 , wherein the feature type is a base feature type.

4. The data processing system of claim 2 , wherein identifying, based on the dependency information, the target build version that meets the dependency requirement includes identifying an earliest build version that includes the feature type on which the first feature depends.

5. The data processing system of claim 1 , wherein identifying, based on the dependency information, the target build version that meets the dependency requirement includes accessing a deployment management database and determining based on information in the deployment management database that the target build version meets the dependency requirement.

6. The data processing system of claim 1 , wherein determining that the computing device meets the target build version includes checking a deployment state machine to determine a deployment status for the target build version.

7. The data processing system of claim 1 , wherein the dependency information includes the target build version.

8. A method for implementing a safe deployment of a first feature of a software application, comprised of a code change and/or a configuration update to the software application in a computing environment, comprising:
receiving registration information for the first feature, the registration information including at least one of a second feature of the software application on which the first feature depends and a feature type on which the first feature depends;
identifying, based on the second feature or the feature type, a target build version of the software application that meets dependency requirements of the second feature or the feature type;
obtaining a list of build versions for a plurality of computing devices in the computing environment;
identifying, using a machine learning model, from among the plurality of computing devices, one or more computing devices that have build versions that meet the target build version;
marking one or more computing devices as being available for deployment of the first feature; and
advancing deployment of the first feature to the one or more computing devices to provide the code change and/or the configuration update to the software application in the one or more computing devices based upon the one or more computing devices being marked as being available for deployment of the first feature to the computing device.

9. The method of claim 8 , further comprising:
utilizing an intelligent data driven deployment plan to obtain capacity unit condition information about the plurality of computing devices in the computing environment; and
utilizing the capacity unit condition information and the list of build versions to identify a capacity unit for deploying the feature to in a next stage of a deployment process.

10. The method of claim 8 , wherein identifying, based on the second feature or the feature type, the target build version that meets dependency requirements of the second feature or the feature type includes identifying an earliest build version that includes at least one of the second feature or a feature type on which the first feature depends.

11. The method of claim 8 , wherein identifying, based on the second feature or the feature type, the target build version that meets dependency requirements of the second feature or the feature type includes accessing a deployment management database and determining based on information in the deployment management database that the target build version includes the second feature or the feature type.

12. The method of claim 11 , wherein identifying, from among the plurality of computing devices, one or more computing devices that have build versions that meet the target build version includes checking a deployment state machine to determine a deployment status for the target build versions.

13. A non-transitory computer readable medium on which are stored instructions that when executed cause a programmable device to perform functions of:
receiving information about a first feature of a software application, comprised of a code change and/or a configuration update to the software application, the first feature being a feature that has become available for being deployed as a feature of the software application in a computing environment, the information received including feature dependency information, wherein the dependency information indicates a dependency requirement for the first feature upon a second feature of the software application in order for the first feature to operate in the software application;
identifying, based on the dependency information, a target build version of the software application that meets the dependency requirement for the first feature;
determining, using a machine learning model, that a computing device meets the dependency requirement for the first feature in the target build version;
upon determining that the computing device, in which the software application is stored, meets the dependency requirement for the first feature in the target build version, attributing a tag to the computing device, the tag identifying the computing device as being available for deployment of the first feature to the computing device; and
advancing deployment of the first feature to the software application in the computing device to provide the code change and/or the configuration update to the software application in the computing device based upon the tag identifying the computing device as being available for deployment of the first feature to the computing device.

14. The non-transitory computer readable medium of claim 13 ,

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Verma Nidhi
• Chen Henry
• Nigam Rahul

Classifications

• G06F8/71 Primary

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/61

  Installation · CPC title

• G06F8/60

  Software deployment · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title