Using virtual machines to manage software builds

• US 9,038,055 B2
• Filed: 08/05/2011
• Issued: 05/19/2015
• Est. Priority Date: 08/05/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Mutisya, Hillary Mucheru, Goldsmith, Benjamin W., Sheppard, Edward Griffin III
• Primary Examiner(s): Kendall, Chuck
• Application Number:
  US13/198,728
• Publication Number:
  US 20130036402A1
• Time in Patent Office: 1,383 Days
• Field of Search: 717168-178
• US Class Current: 717/172
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3692 for test results analysis
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

Concepts and technologies are described herein for using virtual machines to manage software builds. A deployment controller manages deployment of a new software build. The deployment controller installs the new software build on test device and tests the new software build. If the new software build functions without errors, the new software build is deployed to hosts of a data center and monitored for errors. If errors are detected, the errors are reported to a developer associated with the new software build. In some embodiments, the deployment controller creates a differencing disk storing differences between the updated software build and an existing software build and uses the differencing disk for installing the new software build for testing and/or for deploying the new software build.

Claims

1. A computer-implemented method for managing software builds, the computer-implemented method comprising performing computer-implemented operations for:

receiving code corresponding to an update for an existing software build hosted by a data center;

creating a new software build based upon the code, the new software build comprising a new version of the existing software build;

creating a virtual hard drive to host the new software build and creating a differencing disk comprising the virtual hard drive storing data indicating a difference between the existing software build and the new software build;

installing the new software build on the virtual hard drive;

distributing the new software build to a data center for hosting at the data center; and

monitoring performance of the new software build hosted by the data center.

2. The method of claim 1, further comprising testing the new software build installed on the virtual hard drive.

3. The method of claim 2, further comprising:

determining if an error is detected during execution of the new software build during the testing;

in response to determining that the error is not detected, determining that the new software build is ready for distribution to the data center; and

in response to determining that the error is detected, reporting the error.

4. The method of claim 3, wherein reporting the error comprises:

generating an error report that identifies the new software build and the error detected; and

transmitting the error report to a developer associated with the new software build.

5. The method of claim 1, wherein creating the virtual hard drive further comprises:

linking the differencing disk to the virtual hard drive hosting the existing software build.

6. The method of claim 5, wherein distributing the new software build comprises:

copying the differencing disk to the data center; and

linking the copied differencing disk to the virtual hard drive hosting the software build.

7. The method of claim 1, wherein distributing the new software build comprises:

installing the new software build at the data center;

monitoring performance of the new software build; and

determining if an error is detected in the new software build hosted by the data center.

8. The method of claim 7, further comprising:

determining if the error is detected during execution of new software build; and

in response to determining that the error is detected, rolling back deployment of the new software build and reporting the error.

9. The method of claim 7, further comprising copying the differencing disk to the data center, and linking the copied differencing disk to a virtual hard drive hosting the existing software build, and

wherein rolling back deployment of the new software build comprises delinking the differencing disk from the virtual hard drive hosting the existing software build.

10. The method of claim 1, wherein creating the new software build comprises executing a virtual installation package to install the new software build on a virtual hard drive.

11. The method of claim 10, wherein the virtual installation package is stored on and executed on a virtual external storage device.

12. A computer-implemented method for managing software builds, the computer-implemented method comprising performing computer-implemented operations for:

receiving code at a deployment controller, the code corresponding to an update for an existing software build hosted by a data center;

creating a new software build based upon the code, the new software build comprising a new version of the existing software build hosted by the data center;

creating a differencing disk storing data indicating differences between the existing software build and the new software build;

distributing the new software build to the data center for hosting by copying the differencing disk to the data center and linking the differencing disk to a virtual hard drive hosting the existing software build at the data center; and

monitoring performance of the new software build hosted by the data center.

13. The method of claim 12, further comprising testing the new software build before creating the differencing disk, wherein testing the new software build comprises:

creating a virtual hard drive to host the new software build;

installing the new software build on the virtual hard drive; and

testing the new software build installed on the virtual hard drive.

14. The method of claim 13, further comprising:

determining if any errors are detected during execution of the new software build during testing;

in response to determining that no errors are detected, determining that the new software build is ready for rollout to the data center; and

in response to determining that errors are detected, reporting the errors to a developer associated with the code.

15. The method of claim 14, wherein reporting the errors comprises:

generating an error report that identifies the new software build and the error detected; and

transmitting the error report to a developer associated with the new software build.

16. The method of claim 12, wherein creating the new software build comprises executing a virtual installation package to install the new software build on the virtual hard drive, and wherein the virtual installation package is stored on and executed on a virtual external storage device.

17. A computer storage medium having computer readable instructions stored thereupon that, when executed by a computer, cause the computer to:

receive code at a deployment controller, the code corresponding to an update for an existing software build hosted by a data center;

create a new software build based upon the code, the new software build comprising a new version of the existing software build hosted by the data center;

creating a differencing disk storing data indicating differences between the existing software build and the new software build;

install the new software build on a test device;

monitor performance of the new software build on the test device to determine if the new software build is to be deployed; and

in response to determining that no errors are detected during execution of the new software build on the test device, distribute the new software build to the data center for hosting by copying the differencing disk to the data center and linking the differencing disk to a virtual hard drive hosting the existing software build at the data center; and

monitor performance of the new software build hosted by the data center.

18. The computer storage medium of claim 17, further comprising computer-executable instructions that, when executed by the computer, cause the computer to:

determine if an error is detected during execution of the new software build hosted by the data center;

in response to determining that the error is detected, report the error.

19. The computer storage medium of claim 18, wherein reporting the error comprises:

generating an error report that identifies the new software build and the error detected; and

transmitting the error report to a developer associated with code.