Microsoft Technology Licensing, LLC

Jeremy Haubold

Claudio Ariel Pacciarini

Rahul Nigam

Parminder Pal Singh

Harry Phillip Ferguson, Iv

Derek Kiwamu Tsuchida

Shepherd Walker

Jessica Priscila De Sousa Santos

Shepherd Tate Walker

Claudio Pacciarini

Systems and methods are described for verifying functionality of software. A set of code that is to be validated is identified. A first configuration is determined for the set of code that configures the code as a first build for validation. The first build is released for a first validation process. Prior to completion of validation of the first build, a second configuration is determined for the set of code that configures the code as a second build for validation. The second build is released for a second validation process prior to completion of validation of the first build. The first and second validation process are staged so that the first and second builds can be reverted independently of one another in the event of a validation issue. The first and second validation process are independently completed in the absence of a validation issue.

Deployment of variants built from code

Techniques are disclosed for allocating computing resources. Historical verification test data for one or more workloads is accessed. The accessed data is updated by removing data for workloads that are mathematical outliers. Based on the updated data, for one or more workload groups, resource allocations for a range of test times are determined. Based on the allocations, costs for the one or more workload groups are predicted. One or more test configurations are updated based on the predicting.

Optimization of workloads based on constraints

Systems, methods, and software are disclosed herein for triaging test results of a failed code validation. Test results are received indicative of a failed code validation performed in a client device. Failure data is generated from the test results indicating one or more failure modes which occurred during the failed code validation. A follow-up action associated with each of the one or more failure modes is then determined by comparing each of the one or more failure modes to previously identified failure modes. Instructions are communicated to the client device based on the determined follow-up action associated with each of the one or more failure modes.

Test result triage for a failed code validation

A method of and system for incorporating a source code change made in a first branch of a source code configuration into a second branch of the source code configuration is carried out by detecting that the change was made to the first branch, identifying the second branch as a branch of the source code configuration that does not include the change, automatically incorporating the change into the second branch, determining if the automatic incorporation of the change was successful, and notifying an individual if the automatic incorporation was unsuccessful such that manual incorporation may be performed.

Mechanism for automatically incorporating software code changes into proper channels

Various technologies described herein pertain to performing a file operation on an inputted file on a computer system. File data retained at a first location in a data store and a first file name retained at a second location in the data store can be provided. The inputted file can include the file data. Moreover, the first file name is a hard link to the file data. Further, a file operation command related to the file data can be received during installation or removal of the inputted file. Accordingly, a second file name retained at a third location in the data store can be created in response to the file operation command. The second file name is created while the file data is immutably maintained at the first location in the data store. Further, the second file name is a hard link to the file data.

Techniques for efficient file operations

In one embodiment, an application updater may cleanly update a computer applicationwithout causing a fault or a reboot of either the system or the process. A processormay execute a predecessor versionof a computer application. The processormay install a successor versionof the computer applicationon a user account level. The processormay execute the successor versionof the computer application

Growing community of inventors

Portage, IN, United States of America

Jeremy Haubold