Pipeline manager

Patent metadata

Field	Value
Publication number	US-11922153-B2
Application number	US-202117305730-A
Country	US
Kind code	B2
Filing date	Jul 14, 2021
Priority date	Jul 14, 2021
Publication date	Mar 5, 2024
Grant date	Mar 5, 2024

Abstract

The exemplary embodiments are related to a pipeline manager configured to manage a software development pipeline. The pipeline manager receives, via a user interface (UI), a representation of a pipeline comprising a plurality of blocks, wherein each block comprises a defined input and a defined output, executes each block of the pipeline, validates output of each block of the pipeline based on the execution of the block and stores the output of each block and updating data that defines the pipeline based on the output of each block.

First claim

What is claimed is:

1. A method, comprising:
receiving, via a user interface (UI), a representation of a pipeline comprising a plurality of blocks, wherein each block comprises a defined input and a defined output;
executing each block of the pipeline;
validating output of each block of the pipeline based on the execution of the block;
storing the output of each block and updating data that defines the pipeline based on the output of each block; and
generating a wiring from a first one of the blocks to a second one of the blocks, wherein the wiring indicates a first output of the first one of the blocks is a first input to the second one of the blocks and wherein the wiring is based on a property reference comprising a value of a current execution state of the pipeline.

2. The method of claim 1 , wherein the plurality of blocks include at least two serial blocks, wherein the output of a first serial block is the input for a second serial block.

3. The method of claim 1 , wherein the plurality of blocks include at least two parallel blocks, wherein the execution of the at least two parallel blocks are performed simultaneously.

4. The method of claim 1 , wherein each block comprises a block type comprising a block type handler, a schema, and a block type stage.

5. The method of claim 4 , wherein the block type handler corresponds to a handler that is used to run the block.

6. The method of claim 4 , wherein the schema refers to objects that include the defined input and a defined output of the block.

7. The method of claim 4 , wherein the pipeline comprises a plurality of stages and wherein the block type stage defines one or more of the plurality of stages for which the block is used.

8. The method of claim 1 , further comprising:
signing one or more of the blocks or the pipeline when a change is made to the one or more of the blocks or the pipeline; and
storing the outputs of the execution with the signature for the one or more of the blocks or the pipeline.

9. The method of claim 1 , further comprising:
receiving, via the UI, one of a change to one of the plurality of blocks or a new block in the pipeline; and
executing the blocks in the pipeline, wherein the execution comprises only executing the blocks where the change was made or the new block that was added.

10. The method of claim 1 , wherein the pipeline includes one of a user based permission defining users allowed to access the pipeline or a role based permission defining assigned roles of users allowed to access the pipeline.

11. The method of claim 10 , wherein the access comprises multiple levels of access and wherein each user based permission or role based permission is granted access to one or more of the multiple levels of access.

12. The method of claim 1 , wherein each of the plurality of blocks includes one of a user based permission defining users allowed to access the block or a role based permission defining assigned roles of users allowed to access the block.

13. The method of claim 1 , wherein the output of one of the blocks is configured to be shared with a block of another pipeline when (i) a block sequence of the one of the blocks and a block sequence of the block of the another pipeline are the same and (ii) a permission level of the pipeline and the another pipeline are compatible.

14. The method of claim 1 , further comprising:
generating, when the execution of the pipeline is complete, a pipeline execute birth certificate comprising a signature and a time stamp.

15. A non-transitory computer readable storage medium comprising a set of instructions configured to be executed by a processor, wherein the set of instructions cause the processor to perform operations, comprising:
receiving, via a user interface (UI), a representation of a pipeline comprising a plurality of blocks, wherein each block comprises a defined input and a defined output;
executing each block of the pipeline;
validating output of each block of the pipeline based on the execution of the block;
storing the output of each block and updating data that defines the pipeline based on the output of each block; and
generating a wiring from a first one of the blocks to a second one of the blocks, wherein the wiring indicates a first output of the first one of the blocks is a first input to the second one of the blocks and wherein the wiring is based on a property reference comprising a value of a current execution state of the pipeline.

16. The computer readable storage medium of claim 15 , wherein each block comprises a block type comprising a block type handler, a schema, and a block type stage.

17. The computer readable storage medium of claim 15 , wherein the operations further comprise:
signing one or more of the blocks or the pipeline when a change is made to the one or more of the blocks or the pipeline; and
storing the outputs of the execution with the signature for the one or more of the blocks or the pipeline.

18. The method of claim 1 , wherein generating the wiring is performed automatically without input from a user.

19. The method of claim 1 , further comprising:
modifying the pipeline; and
identifying missing input for one or more blocks or missing dependencies for one or more blocks based on modifications to the pipeline.

20. The method of claim 1 , further comprising:
disabling the first one of the blocks;
replacing the value of the current execution state of the pipeline with a static value; and
determining dependencies between blocks based on the first one of the blocks being disables and the static value.

Assignees

• Wind River Systems Inc

Inventors

• Jones Matt
• Nasser Salim
• Wessel Jason

Classifications

• G06F8/4452 Primary

  Software pipelining · CPC title

• G06F8/65

  Updates (security arrangements therefor G06F21/57) · CPC title

• G06F8/77

  Software metrics · CPC title

• G06F9/463

  Program control block organisation · CPC title

• G06F8/60 Primary

  Software deployment · CPC title