Dynamic multiple repository package management through continuous integration
US-2022334830-A1 · Oct 20, 2022 · US
US11915007B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11915007-B2 |
| Application number | US-202117341585-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 8, 2021 |
| Priority date | Jun 8, 2021 |
| Publication date | Feb 27, 2024 |
| Grant date | Feb 27, 2024 |
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.
A method includes receiving, by a processing device, a definition of a CI/CD pipeline for executing a set of stages of the CI/CD pipeline. The CI/CD pipeline is associated with a first computer system. The method further includes converting, by the processing device, the definition into a container image file, and causing, by the processing device using the container image file, a second computer system to implement a container executing the CI/CD pipeline.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, by a processing device, a definition of a continuous integration and continuous delivery/deployment (CI/CD) pipeline for executing a set of stages of the CI/CD pipeline, wherein the CI/CD pipeline is associated with a first computer system; converting, by the processing device, the definition into a container image file, wherein converting the definition into the container image file comprises removing implementation-specific code associated with the definition; and causing, by the processing device using the container image file, a second computer system, different from the first computer system, to implement a container executing the CI/CD pipeline. 2. The method of claim 1 , wherein converting the definition into the container image file further comprises expanding code of the definition to obtain expanded pipeline code, and wherein the implementation-specific code is removed from the expanded pipeline code. 3. The method of claim 1 , wherein the implementation-specific code comprises code related to logical separations associated with the set of stages. 4. The method of claim 1 , wherein the implementation-specific code comprises CI/CD pipeline scheduling code. 5. The method of claim 1 , wherein converting the definition into the container image file further comprises identifying an operating system for executing the container. 6. The method of claim 1 , wherein converting the definition into the container image file further comprises: defining a set of variables within the container image file for handling inputs for executing the CI/CD pipeline; and receiving storage location information defining a storage location for handling outputs during container execution of the CI/CD pipeline. 7. The method of claim 1 , wherein the first computer system is a CI/CD system, and wherein the second computer system is a host. 8. A computing system comprising: a memory; and a processing device, operatively coupled to the memory, to: receive a definition of a continuous integration and continuous delivery/deployment (CI/CD) pipeline for executing a set of stages of the CI/CD pipeline, wherein the CI/CD pipeline is associated with a first computer system; convert the definition into a container image file, wherein, to convert the definition into the container image file, the processing device is to remove implementation-specific code associated with the definition; and cause, using the container image file, a second computer system, different from the first computer system, to implement a container for executing the CI/CD pipeline. 9. The computing system of claim 8 , wherein, to convert the definition into the container image file, the processing device is further to expand code of the definition to obtain expanded pipeline code, and wherein the implementation-specific code is removed from the expanded pipeline code. 10. The computing system of claim 8 , wherein the implementation-specific code comprises code related to logical separations associated with the set of stages. 11. The computing system of claim 8 , wherein the implementation-specific code comprises CI/CD pipeline scheduling code. 12. The computing system of claim 8 , wherein, to convert the definition into the container image file, the processing device is further to identify an operating system for executing the container. 13. The computing system of claim 8 , wherein, to convert the definition into the container image file, the processing device is further to: define a set of variables within the container image file for handling inputs for executing the CI/CD pipeline; and receive storage location information defining a storage location for handling outputs during container execution of the CI/CD pipeline. 14. The computing system of claim 8 , wherein the first computer system is a CI/CD system, and wherein the second computer system is a host. 15. A computing system comprising: a memory; and a processing device, operatively coupled to the memory, to: receive a definition of a continuous integration and continuous delivery/deployment (CI/CD) pipeline for executing a set of stages of the CI/CD pipeline, wherein the CI/CD pipeline is associated with a first computer system; expand code of the definition to obtain expanded pipeline code comprising implementation-specific code; remove the implementation-specific code from the expanded pipeline code; and after removing the implementation-specific code, generate a container image file for implementing a container associated with a second computer system, different from the first computer system, for executing the CI/CD pipeline. 16. The computing system of claim 15 , wherein the implementation-specific code comprises at least one: of code related to logical separations associated with the set of stages, or CI/CD pipeline scheduling code. 17. The computing system of claim 15 , wherein the processing device is further to cause the second computer system to implement the container for executing the CI/CD pipeline. 18. The computing system of claim 15 , wherein, to generate the container image file, the processing device is further to: identify an operating system for executing the container; define a set of variables within the container image file for handling inputs for executing the CI/CD pipeline; and receive storage location information defining a storage location for handling outputs during container execution of the CI/CD pipeline. 19. The computing system of claim 15 , wherein the first computer system is a CI/CD system, and wherein the second computer system is a host.
Implementation aspects, e.g. pipeline latches; pipeline synchronisation and clocking · CPC title
Image based installation; Cloning; Build to order · CPC title
Adapting program code to run in a different environment; Porting · CPC title
Instruction operation extension or modification · CPC title
for non-native instruction execution, e.g. executing a command; for Java instruction set · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.