Abstract: Systems and methods for deploying dependent updates include mechanisms for requiring that dependency information be provided for each update so that dependent updates may be identified. Update dependencies are tracked so that dependent updates are not deployed until parent updates have been completed. Deployment sequencing is implemented on top of existing asynchronous deployment policies so that asynchronous workflow remains intact and unaltered. The asynchronous workflow is upgraded to a synchronous (i.e., sequential) workflow for updates having dependencies to ensure that updates having dependencies are applied in the correct order.

Abstract: A data processing system is implemented for detecting changes to infrastructure components, and extracting metadata associated with the changes. The data processing system also implements grouping the changes based on the metadata, ranking the groups of changes based on past incidents of service outages, and displaying the ranked groups of changes to a user.

Abstract: A data processing system implements scalable, secure, and reliable targeted release (TR) deployments of updates in cloud-based service. The TR deployment framework is provided that solves the technical problem of facilitating deployment of updates to targeted release customers. TR customers are associated with pre-deployment requirements (PDRs) associated with accreditation and/or validation tasks that must be completed before the update may be deployed to the customer base of the TR customers. A subset of the TR customer base is provided with segregated access to complete these accreditation tasks and/or validation tasks before the update is provided to the remainder of the userbase of the TR customer. This approach ensures that the industry standards and/or customer requirements are met before the update is deployed to the entire userbase of the TR customer.

Abstract: A data processing system implements managing the deployment of updates to a cloud-based service by deploying an update to one or more components of a cloud-based service according to a deployment plan. The deployment plan defines a plurality of stages in which the update is deployed to a subset of the components associated with a different subset of users of a userbase. The system implements receiving signal data that includes information regarding the performance of the update at each stage of the deployment plan; analyzing the signal data to determine whether one or more trigger conditions of halt and recovery rules associated with the update have been satisfied; and automatically halting deployment of the update to the one or more components of the cloud-based service responsive to at least one of the trigger conditions associated with the halt and recovery rules associated with the update having been satisfied.

Abstract: Technologies are disclosed for improving the deployment of a cloud-hosted service. Before being deployed to a particular environment, a cloud-hosted service must be configured for that environment. Configuring a deployment includes determining which components to deploy, determining how to connect with external components, identifying onboarding procedures, etc. A dependency data model defines a hierarchy of components utilized by the cloud-hosted service. For each component in the hierarchy, configuration parameters define how to deploy that component. A list of configuration parameters that do not yet have values for a target environment may be generated and provided to a user. Values for these parameters may then be received. A configuration for the target environment is then generated based on the dependency data model and the received values. The dependency data model may inherit dependencies and configuration properties from ancestors in a hierarchy of dependency data models.

Abstract: Systems and methods for creating and deploying jobs in a cloud-based service include receiving a job definition defining job attributes pertaining to a job to be deployed in a cloud-based service. The job definition is processed to determine whether the job definition complies with predefined rules for job creation in the cloud-based service. Based on the determination of whether the job definition complies with the predefined rules for job creation in the cloud-based server, the job may be validated or not validated in the cloud-based service. Deployment policies are determined for validated jobs based on the job definition for the validated job.

Abstract: A method of and system for customizing a rollout process of application features includes providing a list of one or more application features for display on a user interface screen, the software application features being application features that are scheduled for a staged rollout, enabling selection of one of the application features for enrolling in late-stage rollout or opting out of the staged rollout, receiving a request for enrolling a user entity in late-stage rollout or opting the user entity out of the staged rollout, storing a property associated with the user entity in a data store, the property indicative of the user entity enrolling in late-stage rollout or opting out of the staged rollout, accessing the stored property, when selecting a plurality of enterprises or users for the staged rollout of the application feature, and depending on the accessed property, selecting the user entity for late-stage rollout or not selecting the user entity for the staged rollout.

Abstract: Disclosed herein is a system for improving the user experience in the face of a regression by returning resources that offer a service to a “last known good” upgrade. In other words, the state of the resources is reconfigured to scale back from recent upgrade(s), the deployments of which likely caused the regression, to a previous upgrade that is known to have little or no effect on the user experience. To identify a problem, the system collects performance data from different resource units that make up a cloud-based platform. The performance data is collected for each upgrade event in a sequence of upgrade events that are currently deployed or being deployed. The system continually tracks and analyzes qualification data collected for each of the deployed upgrade events. The system can tag an upgrade event as the last known good upgrade event when the collected qualification data satisfies predefined qualifications.

Abstract: Please replace the Abstract of the Disclosure with the following Abstract showing all changes relative to the previous version of the Abstract (In the replacement Abstract, the header and footer have been marked out):

Abstract: A data processing system implements obtaining a set of first input parameters associated with a first update to be deployed to one or more components of a cloud-based service; providing the set of first input parameters to a machine learning model to obtain a first deployment policy for the first update; analyzing the set of first input parameters using the machine learning model to generate the first deployment policy, the machine learning model being trained to analyze input parameters associated with an update to be deployed to the cloud-based service and to generate a deployment policy for the update, the deployment policy identifying a set of rings for deploying the update and when the update is to be deployed to a subset of the userbase of the cloud-based service associated with that ring; and executing the first deployment policy to deploy the update to the one or more components.

Abstract: A system and method to allow an authorized searcher to conduct a search of a current primary version of a document being developed in an application as well as versions of the document which were used in the development of the current primary version. In an exemplary system, instructions cause a processor to grant a search request to search, via a search index in a cloud storage, stored selected versions of the document. The stored selected versions of the document are historical versions of the current primary version of the document which has been selected from among the stored selected versions to be accessible, via the search index, to other searchers having a lower access authorization than the predetermined access authorization. The authorized searcher is provided with a capability to toggle between searching only the primary version of the document and searching the stored selected versions of the document.

Abstract: A data processing system implements obtaining policy information for an update to be deployed to one or more components of a cloud-based service identifying a plurality of rings of the cloud-based service to which the update is to be deployed; analyzing the policy information to determine configuration information for a plurality of installer instances each associated with one or more rings or one or more stages of a ring to which the update is to be deployed; obtaining payload information for each respective installer instance, the payload information indicating one or more payloads associated with the update to be deployed to the respective one or more rings or one or more stages of the ring associated with the respective installer instance; and deploying the one or more payloads for each of the one or more rings or the one or more stages of the ring associated with each installer instance.

Abstract: A data processing system implements obtaining a set of input parameters associated with an update to be deployed to a plurality of server farms of a cloud-based service, wherein each server farm includes a primary replica configured to handle user traffic and a disaster recovery replica configured to handle user traffic responsive to a failure of the primary replica; determining temperature information for each of the server farms, ranking the server farms based on the temperature information to determine an order in which an update is to be deployed to the server farms; iteratively deploying the updates to the primary replicas of the server farms according to the ranking until an deployment threshold has been satisfied; and iteratively deploying the updates to the primary replicas of server farms for which the primary replicas have not yet been updated and to the disaster recovery replicas of the server farms.

Abstract: A data processing system implements obtaining a set of first input parameters associated with a first update to be deployed to one or more components of a cloud-based service; providing the set of first input parameters to a machine learning model to obtain a first deployment policy for the first update; analyzing the set of first input parameters using the machine learning model to generate the first deployment policy, the machine learning model being trained to analyze input parameters associated with an update to be deployed to the cloud-based service and to generate a deployment policy for the update, the deployment policy identifying a set of rings for deploying the update and when the update is to be deployed to a subset of the userbase of the cloud-based service associated with that ring; and executing the first deployment policy to deploy the update to the one or more components.

Abstract: Reliable feature deployment is provided. Features are evaluated for their readiness to be graduated and features that are ready to be graduated are added to a graduation list. When features are added to the graduation list, evaluation of the features is discontinued, thereby reducing the performance and runtime costs associated with deploying features. Furthermore, engineers can consult the graduation list to identify features that are ready for graduation, thereby reducing the risk of premature flight graduation. Data associated with features is analyzed to map the features to corresponding flights. In this way, when an engineer identifies a feature for graduation, the engineer is able to identify the corresponding flight (or flights) from the mapping. Even when a feature is selected for graduation, the present systems provide additional safeguards to ensure that corresponding flights are not improperly or prematurely graduated, thereby preventing a subpar customer experience.

Abstract: The techniques disclosed herein enable improved security as well as more scalable and reliable job execution by utilizing granular security boundaries and certificate-based authentication for all communication within cloud-based platforms. To manage a cloud-based platform, a system receives a plurality of jobs and associated certificates at a first security boundary that are to be executed at various resource units within a second security boundary. The system then authenticates each certificate before transmitting each job to its respective resource unit for execution. In addition, the system is further configured to monitor active certificates for compromise and accordingly isolate various security boundaries in the event of a security breach. By isolating portions of the cloud-based platform within security boundaries, the system can mitigate the impact of security breaches. Furthermore, certificate-based authentication addresses performance constraints to enable more efficient and scalable job execution.

Abstract: A method of and system for customizing a rollout process of application features includes providing a list of one or more application features for display on a user interface screen, the software application features being application features that are scheduled for a staged rollout, enabling selection of one of the application features for enrolling in late-stage rollout or opting out of the staged rollout, receiving a request for enrolling a user entity in late-stage rollout or opting the user entity out of the staged rollout, storing a property associated with the user entity in a data store, the property indicative of the user entity enrolling in late-stage rollout or opting out of the staged rollout, accessing the stored property, when selecting a plurality of enterprises or users for the staged rollout of the application feature, and depending on the accessed property, selecting the user entity for late-stage rollout or not selecting the user entity for the staged rollout.

Abstract: Traditionally, when a feature is updated or a new feature is released, the feature undergoes internal testing and validation before external distribution. However, some features may receive proportionately less internal usage than customer usage reflected externally. Low internal usage of features can lead to weak telemetry data, which can allow code regressions (e.g., bugs) to go undetected until the features are released to customers. Accordingly, accelerated internal feature usage is provided to mirror external customer usage. Highly used features are dynamically identified and, any deficiencies in internal feature usage are identified. Tenant sites estimated to generate at least a portion of the deficiency in feature usage are identified. These sites may be migrated or replicated to internal validation rings to generate additional internal feature usage.

Abstract: The techniques disclosed herein enable systems to safely deploy a plurality of upgrade variants to different resource units that provide a service by utilizing small-scale deployment and validation. To deploy upgrade variants, a system receives a selection of upgrade variants from a feature group and automatically selects an appropriate set of resource units at which to deploy the upgrade variants. The system is further configured to collect and analyze telemetry data from the set of resource units to determine if any problems have occurred as a result of the deployed upgrade variants. By analyzing the telemetry data, the system can also identify one or more upgrade variants that are causing the problems. In response, the system can remove the identified variants and proceed with deployment of the remaining upgrade variants.

Abstract: Technologies are disclosed for improving the deployment of a cloud-hosted service. Before being deployed to a particular environment, a cloud-hosted service must be configured for that environment. Configuring a deployment includes determining which components to deploy, determining how to connect with external components, identifying onboarding procedures, etc. A dependency data model defines a hierarchy of components utilized by the cloud-hosted service. For each component in the hierarchy, configuration parameters define how to deploy that component. A list of configuration parameters that do not yet have values for a target environment may be generated and provided to a user. Values for these parameters may then be received. A configuration for the target environment is then generated based on the dependency data model and the received values. The dependency data model may inherit dependencies and configuration properties from ancestors in a hierarchy of dependency data models.