# US 10,372,441 B2 · Build isolation system in a multi-system environment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,372,441 B2
- Document ID: US10372441B2
- Status: Granted
- Kind: B2
- Application number: 15/425,775
- Filed: 2017-02-06
- Published: 2018-05-31
- Granted: 2019-08-06
- Earliest claimed: 2016-11-28
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Matthew Ross Peterson; Carlo Rivera; David Speirs; Max David Bressler
- Web page: https://patentgrep.com/patent/US10372441B2

## CPC

- G06F 8/70: Software maintenance or management
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 11/1446: Point-in-time backing up or restoration of persistent data
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Software build isolation is provided. Systems, methods and computer-readable devices provide for receiving a request from a user who is a member of a team or group for allocation of a machine from a pool of machines. A determination is made as to whether a limit has been reached on the number of machines available to the team or group. If the limit has not been reached, the machine is provisioned and the user is notified that the machine has been provisioned and allocated to the user. In addition, in response to receiving a notification that an asset is ready for backup, an asset is replicated on an archive server. Dependencies of the asset on dependent assets are determined and the dependent assets are replicated on the archive server.

## Claims

### Claim 1

A method, comprising:
receiving, by a processing device, a first notification that an asset is ready for backup, wherein the asset is a tenant code of a monolithic code, wherein the first notification is generated after a successful build of the tenant code of the monolithic code, and wherein the successful build of the tenant code of the monolithic code occurs when the tenant code of the monolithic code is checked in;
in response to the successful build of the tenant code of the monolithic code and receipt of the first notification, replicating, by the processing device, the asset on an archive server;
determining, by the processing device, dependencies of the asset on dependent assets; and
replicating, by the processing device, the dependent assets on the archive server, wherein the dependent assets are part of the monolithic code but not part of the tenant code of the monolithic code.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving a second notification that the asset is ready for backup, wherein receiving the second notification comprises receiving the second notification from a user;
in response to the receipt of the second notification, repeating the replication of the asset on the archive server;
repeating the determination of the dependencies of the asset on the dependent assets; and
repeating the replication of the dependent assets on the archive server.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving a second notification that the asset is ready for backup, wherein receiving the second notification comprises receiving the second notification from a scheduler;
in response to the receipt of the second notification, repeating the replication of the asset on the archive server;
repeating the determination of the dependencies of the asset on the dependent assets; and
repeating the replication of the dependent assets on the archive server.

### Claim 4 (depends on 1)

The method of claim 1, further comprising determining if the asset has been electronically delivered to a customer.

### Claim 5 (depends on 4)

The method of claim 4, further comprising maintaining the asset on the archive server if the asset has been electronically delivered to the customer.

### Claim 6 (depends on 4)

The method of claim 4, further comprising determining if a time limit has expired if the asset has not been electronically delivered to the customer.

### Claim 7 (depends on 6)

The method of claim 6, further comprising removing the asset from the archive server if the time limit has expired.

### Claim 8 (depends on 6)

The method of claim 6, further comprising removing the asset from an original location of the asset if the time limit has expired.

### Claim 9 (depends on 4)

The method of claim 4, further comprising maintaining the dependent assets on the archive server if the asset has been electronically delivered to the customer.