Computer-automated software release and deployment architecture
US-11093227-B1 · Aug 17, 2021 · US
US12468511B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12468511-B2 |
| Application number | US-202117149679-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 14, 2021 |
| Priority date | Jan 14, 2021 |
| Publication date | Nov 11, 2025 |
| Grant date | Nov 11, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Described herein is a computer implemented method and a computer system for processing a modification to a first repository, the first repository including components that are used in a second repository. The method comprises executing an integrator service that is communicatively coupled to the first repository and to the second repository; the integrator service detecting the modification to the first repository; the integrator service causing generation of an integrated repository by integration of the detected modification into the second repository; and the integrator service triggering processing of the integrated repository.
Opening claim text (preview).
The invention claimed is: 1 . A computer implemented method for processing components managed by a first repository and used by a product of a second repository, the method comprising: executing an integrator service that is communicatively coupled to the first repository and to the second repository, the first repository including a first set of source code hosted on a public network by a content delivery network (CDN), the second repository including a second set of source code hosted on an internal network, the second set of source code directed to software components different than the first set of source code; retrieving, by the integrator service, a continuous integration plan for the second repository, the continuous integration plan indicating one or more branches of the second repository; extracting, by the integrator service, a respective latest successful build number for each of the one or more branches of the second repository; detecting, by the integrator service, a modification to a particular component of the first set of source code stored by the first repository, the particular component built and tested by a first service operating the first repository, and the modification comprising creation of a new branch in the first repository, wherein the new branch created in the first repository encapsulates new or modified functionality of one or more of the first repository's components that are used in a branch of the second repository associated with at least one of the respective latest successful build numbers; downloading, by the integrator service, the detected modification from the first repository and communicating the modification to the second repository; causing generation of an integrated repository of integrated source code, by the integrator service, through integration of the detected modification into the second repository by causing a creation of a new branch in the second repository that corresponds to the new branch in the first repository, the new branch of the second repository named to indicate the integrator service; the integrator service triggering processing of the integrated repository; in response to a failed integration of the integrated repository, communicating, by the integrator service, a stop status to the CDN, the stop status corresponding to the new branch in the second repository; in response to a failed test of the integrated repository, communicating, by the integrator service, the stop status to the CDN; and in response to a successful integration and test of the integrated repository, causing generation of an artifact of the successful integration and publishing the modification to the particular component of the first set of source code on the CDN. 2 . The computer implemented method according to claim 1 , wherein the new branch created in the first repository has a deployment pipeline independent of a deployment pipeline of a main branch of the first repository. 3 . The computer implemented method according to claim 1 , wherein the processing of the integrated repository triggered by the integrator service comprises building a product from the integrated repository. 4 . The computer implemented method according to claim 3 , wherein the processing of the integrated repository triggered by the integrator service comprises testing the product built from the integrated repository. 5 . The computer implemented method according to claim 1 , wherein the integrator service detects the modification to the first repository by polling a registry to which a package built from the first repository has been uploaded. 6 . The computer implemented method according to claim 5 , wherein the integrator service retrieves commit information from the registry and causes the generation of the integrated repository by integration of the detected modification into the second repository by reference to the commit information. 7 . The computer implemented method according to claim 1 , further comprising the integrator service communicating to the first repository, modification-processing status information resulting from processing the integrated repository. 8 . The computer implemented method according to claim 7 , wherein the integrator service obtains the modification-processing status information by processing integrated repository information resulting from processing the integrated repository, to extract processing-status data pertaining to the detected modification. 9 . The computer implemented method according to claim 7 , wherein the integrator service communicates modification-processing status information to the first repository without impacting operation of the first repository. 10 . A computer system comprising: a processing unit; and non-transitory memory, the non-transitory memory comprising instructions, which when executed by the processing unit cause the computer system to: process components managed by a first repository and used by a product of a second repository; execute an integrator service that is communicatively coupled to the first repository and to the second repository, the first repository including a first set of source code hosted on a public network by a content delivery network (CDN), the second repository including a second set of source code hosted on an internal network, the second set of source code directed to software components different than the first set of source code; cause the integrator service to retrieve a continuous integration plan for the second repository, the continuous integration plan indicating one or more branches of the second repository; cause the integrator service to extract a respective latest successful build number for each of the one or more branches of the second repository; cause the integrator service to detect a modification to a particular component stored by the first repository, the particular component built and tested by a first service operating the first repository, and the modification comprising creation of a new branch in the first repository, wherein the new branch created in the first repository encapsulates new or modified functionality of one or more of the first repository's components that are used in a branch of the second repository associated with at least one of the respective latest successful build numbers; cause the integrator service to download the detected modification from the first repository and communicating the modification to the second repository; cause the integrator service to cause generation of an integrated repository of integrated source code by integration of the detected modification into the second repository by causing a creation of a new branch in the second repository that corresponds to the new branch in the first repository, the new branch of the second repository named to indicate the integrator service; cause the integrator service to trigger processing of the integrated repository; in response to a failed build of the integrated repository, cause the integrator service to communicate a stop status of the CDN, the stop status corresponding to the new branch in the second repository; in response to a failed test of the integrated repository, cause the integrator service to communicate the stop status of the CDN; and in response to a successful integration and test of the integrated repository, cause the integrator service to cause generation of an artifact of the successful integration and publishing the modification to the particular component of the first set of source code on the CDN. 11 . The computer system according to claim 10 , wherein the new branch created in the first repository has a deployment pipeline
Related publications grouped by family.
Answers are generated from the same data shown on this page.