Software Delivery Pipeline Management
US-2018173525-A1 · Jun 21, 2018 · US
US10228936B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10228936-B2 |
| Application number | US-201615381250-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 16, 2016 |
| Priority date | Dec 16, 2016 |
| Publication date | Mar 12, 2019 |
| Grant date | Mar 12, 2019 |
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.
Examples described relate to managing a software delivery pipeline. In an example, a modified software may be identified. Further, a modification in the modified software may be identified. Further, a type of the modification may be identified. Further, a stage of a software delivery pipeline management system may be identified based on the type of the modification. Further, the modified software may be placed in the identified stage of the software delivery pipeline management system.
Opening claim text (preview).
The invention claimed is: 1. A method of performing tests of a modified software in a software delivery pipeline management system, comprising: identifying, by the software delivery pipeline management system, the modified software, the software delivery pipeline management system comprising a plurality of stages arranged in a sequential order; identifying, by the software delivery pipeline management system, a plurality of modifications in the modified software based on metadata associated with the modified software, wherein the metadata comprises a plurality of a pre-defined indications associated with multiple types of modifications; identifying, by the software delivery pipeline management system, a plurality of types of the plurality of modifications based on the metadata; identifying, by the software delivery pipeline management system, a second plurality of stages of the software delivery pipeline management system based on the plurality of types of the plurality of modifications, wherein the identified second plurality of stages is included in the plurality of stages of the software delivery pipeline management system, wherein the plurality of stages comprises at least a development stage, a quality assurance stage, and a production stage; successively deploying, by the software delivery pipeline management system, the modified software through the second plurality of stages in the software delivery pipeline management system beginning with an earliest stage in the second plurality of stages; and performing, by the software delivery pipeline management system, tests associated with the second plurality of stages on the modified software, the performing comprising bypassing one or more tests associated with one or more stages prior to the second plurality of stages. 2. The method of claim 1 , wherein the plurality of stages further comprises a performance testing stage, a security testing stage, and a staging stage. 3. The method of claim 1 , wherein the metadata comprises a pre-defined comment related to the modification. 4. The method of claim 1 , wherein the metadata comprises a plurality of pre-defined numerical codes associated with the plurality of modification types. 5. A system for performing tests of a modified software, comprising: a hardware processor; and a non-transitory storage medium storing instructions, the instructions executable by the hardware processor to: identify the modified software to be tested in a plurality of stages of a software delivery pipeline management system; identify a plurality of modifications in the modified software based on metadata associated with the modified software, wherein the metadata comprises a plurality of a pre-defined indications associated with multiple types of modifications; identify a plurality of types of the plurality of modifications based on the metadata; identify a second plurality of stages of the software delivery pipeline management system based on the plurality of types of the plurality of modifications, wherein the identified second plurality of stages is included in the plurality of stages of the software delivery pipeline management system, wherein the plurality of stages comprises at least a development stage, a quality assurance stage, and a production stage; successively deploy the modified software through the second plurality of stages in the software delivery pipeline management system beginning with an earliest stage in the second plurality of stages; and perform a plurality of tests associated with the second plurality of stages on the modified software, comprising bypassing one or more tests associated with one or more stages prior to the identified second plurality of stages. 6. The system of claim 5 , wherein the metadata comprises a pre-defined comment related to the modification. 7. The system of claim 5 , wherein the metadata comprises a plurality of pre-defined numerical codes associated with the plurality of modification types. 8. The system of claim 5 , wherein the plurality of stages further comprises a performance testing stage, a security testing stage, and a staging stage. 9. A non-transitory machine-readable storage medium comprising instructions for performing tests of a modified software, the instructions executable by a processor to: identify a modified software to be tested in a plurality of stages of a software delivery pipeline management system; identify a plurality of modifications in the modified software based on metadata associated with the modified software, wherein the metadata comprises a plurality of a pre-defined indications associated with multiple types of modifications; identify a plurality of types of the plurality of modifications based on the metadata; identify a second plurality of stages of the software delivery pipeline management system based on the plurality of types of the plurality of modifications, wherein the identified second plurality of stages is included in the plurality of stages of the software delivery pipeline management system, wherein the plurality of stages comprises at least a development stage, a quality assurance stage, and a production stage; successively deploy the modified software through the second plurality of stages in the software delivery pipeline management system beginning with an earliest stage in the second plurality of stages; and perform a plurality of tests associated with the identified second plurality of stages of the software delivery pipeline management system on the modified software, comprising a bypass of one or more tests associated with one or more stages prior to the identified second plurality of stages. 10. The storage medium of claim 9 , wherein the plurality of stages further comprises a performance testing stage, a security testing stage, and a staging stage. 11. The storage medium of claim 9 , wherein the metadata comprises a plurality of pre-defined numerical codes associated with the plurality of modification types.
Software deployment · CPC title
Software metrics · CPC title
for test execution, e.g. scheduling of test suites · CPC title
Arrangements for software engineering (testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06) · CPC title
Prevention of errors by analysis, debugging or testing of software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.