AUTOMATED UPDATES TO CODE DEPLOYMENT PIPELINES

Number: 20230259356
Published: 2023-08-17
Filed: 2022-02-15
Assignee: Disney Enterprises, Inc.
Inventors: Wagner; Steven et al.
CPC: G06F8/65; G06F8/71; G06F8/61
Verdict: Set aside software deployment tooling, IT
Source: Google Patents · FreePatentsOnline

Abstract

Certain aspects of the present disclosure provide techniques for automated updates to code deployment pipelines. This includes identifying a proposed change to a plurality of source code repositories based on parsing a change template. It further includes determining one or more changes to one or more files in each respective source code repository, of the plurality of source code repositories, based on the proposed change. It further includes changing the one or more files in each respective source code repository, based on the determined one or more changes, and building a project in each respective source code repository using the changed one or more files.

Background

BACKGROUND

Many source code repositories include instructions, across repositories, that share certain similarities but that are not identical. For example, source code in different repositories can make analogous application programmer interface (API) calls to a particular third party API. These calls may be similar across the various repositories, but not identical. If this API changes, the calls must be modified across all source code repositories to ensure that all the repositories correctly call the API. Typically, this must be done manually, by requiring an engineer responsible for each repository to make the change in the repository, review the change, and commit the change to the repository. Making manual changes is extremely inefficient and time consuming, and prone to human error. Further, the process of implementing manual changes dis-incentivizes potential improvements across repositories because of the burden in making changes. SUMMARY

Embodiments include a method. The method includes identifying a proposed change to a plurality of source code repositories based on parsing a change template. The method further includes determining one or more changes to one or more files in each respective source code repository, of the plurality of source code repositories, based on the proposed change. The method further includes changing the one or more files in each respective source code repository, based on the determined one or more changes. The method furthe

Claims

1. A method, comprising: identifying a proposed change to a plurality of source code repositories by parsing a change template generated automatically based on previously committed changes; determining one or more changes to one or more files in each respective source code repository, of the plurality of source code repositories, based on the proposed change; changing the one or more files in each respective source code repository, based on the determined one or more changes; and building a project in each respective source code repository using the changed one or more files. || 11. A non-transitory computer-readable medium containing computer program code that, when executed by operation of one or more computer processors, performs operations comprising: identifying a proposed change to a plurality of source code repositories by parsing a change template generated automatically based on previously committed changes; determining one or more changes to one or more files in each respective source code repository, of the plurality of source code repositories, based on the proposed change; changing the one or more files in each respective source code repository, based on the determined one or more changes; and building a project in each respective source code repository using the changed one or more files. || 17. A system, comprising: a computer processor; and a memory having instructions stored thereon which, when executed on the computer processor, performs operations comprising: identifying a proposed change to a plurality of source code repositories by parsing a change template generated automatically based on previously committed changes; determining one or more changes to one or more files in each respective source code repository, of the plurality of source code repositories, based on the proposed change; changing the one or more files in each respective source code repository, based on the determined one or more changes; and building a project in each respective source code repository using the changed one or more files.