Software provenance validation
US-12111957-B2 · Oct 8, 2024 · US
US2025224933A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2025224933-A1 |
| Application number | US-202418403940-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jan 4, 2024 |
| Priority date | Jan 4, 2024 |
| Publication date | Jul 10, 2025 |
| Grant date | — |
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 remote build orchestrator for building and testing a software program is described and includes a generator service for generating a build graph from a definition of the software program input to the remote build orchestrator, the build graph comprising a plurality of actions, wherein the actions are defined by inputs, outputs, and commands, and wherein outputs of actions that are dependent on other actions for inputs are represented in the build graph by placeholders; an unwinder service for receiving the build graph from the generator service and processing the build graph into a series of requests for execution of the actions; and a remote build execution service for executing the actions in response to the received requests and returning results of the executing to the unwinder service.
Opening claim text (preview).
What is claimed is: 1 . A remote build orchestrator for building and testing a software program, the remote orchestrator comprising: a processor; a memory accessible by the processor; a generator service for generating a build graph from a definition of the software program input to the remote orchestrator, the build graph comprising a plurality of actions, wherein the actions are defined by inputs, outputs, and commands, wherein the actions are defined by the inputs, outputs and commands of the actions, and wherein outputs of actions that are dependent on other actions for inputs are represented in the build graph by placeholders; an unwinder service for receiving the build graph from the generator service and processing the build graph into a series of requests for execution of the actions; and a remote build execution service for executing the actions in response to the received requests and returning results of the executing to the unwinder service. 2 . The remote build orchestrator of claim 1 , wherein the unwinder service uses the results returned from the remote build execution service to replace the placeholders with actual data resulting from the executing. 3 . The remote build orchestrator of claim 1 , wherein the unwinder service comprises a plurality of unwinder pods. 4 . The remote build orchestrator of claim 3 , wherein the unwinder service comprises a ring hash load balancer for load balancing the unwinder pods. 5 . The remote build orchestrator of claim 1 , wherein the build graph comprises a Merkle tree. 6 . The remote build orchestrator of claim 1 , wherein the placeholders comprise signatures that uniquely and deterministically represent the dependent actions. 7 . The remote build orchestrator of claim 1 , wherein the requests comprise remote execution application programming interface requests. 8 . The remote build orchestrator of claim 1 , wherein each of the generator service, the unwinder service, and the remote broker execution service are executed on separate machines. 9 . The remote build orchestrator of claim 1 , wherein the build graph is provided to the unwinder service via a network connection. 10 . The remote build orchestrator of claim 1 , wherein subsequent to completion of execution of all of the actions by the remote broker execution service, the remote build orchestrator generates an aggregate pass-fail result based on the execution of all of the actions. 11 . A computer-implemented method for building and testing a software program, the computer-implemented method comprising: generating a build graph from a definition of the software program input to a remote build orchestrator, the build graph comprising a plurality of actions, wherein the actions are defined by inputs, outputs, and commands, and wherein outputs of actions that are dependent on other actions for inputs are represented in the build graph by placeholders; processing the build graph into a series of requests for execution of the actions; and executing the actions in response to the received requests to produce results, wherein the generating, the processing, and the executing are each performed by a different machine entity. 12 . The computer-implemented method of claim 11 , further comprising using the results to replace the placeholders with data comprising the results. 13 . The computer-implemented method of claim 11 , further comprising performing ring hash load balancing in connection with the processing. 14 . The computer-implemented method of claim 11 , wherein the build graph comprises a Merkle representation. 15 . The computer-implemented method of claim 11 , wherein the placeholders comprise signatures that uniquely and deterministically represent the dependent actions. 16 . The computer-implemented method of claim 11 , further comprising, subsequent to completion of execution of all of the actions, returning an aggregate pass-fail result based on the execution of all of the actions. 17 . One or more non-transitory computer-readable storage media comprising instructions for execution that, when executed by a processor, are operable to cause to be performed operations comprising: generating a build graph from a definition of the software program input to a remote build orchestrator, the build graph comprising a plurality of actions, wherein the actions are defined by inputs, outputs, and commands, and wherein outputs of actions that are dependent on other actions for inputs are represented in the build graph by placeholders; processing the build graph into a series of requests for execution of the actions; executing the actions in response to the received requests to produce results; and subsequent to completion of execution of all of the actions, returning an aggregate pass-fail result based on the execution of all of the actions. 18 . The one or more non-transitory computer-readable storage media of claim 17 , wherein the operations further comprise: using the results to replace the placeholders with data comprising the results; and re-executing the actions comprising the placeholders subsequent to the replacing. 19 . The one or more non-transitory computer-readable storage media of claim 17 , wherein the build graph comprises a Merkle representation of the software project. 20 . The one or more non-transitory computer-readable storage media of claim 17 , wherein the placeholders comprise signatures that uniquely and deterministically represent the dependent actions.
Remote procedure calls [RPC]; Web services · CPC title
Environments for analysis, debugging or testing of software · CPC title
for test execution, e.g. scheduling of test suites · CPC title
model driven · CPC title
Requirements analysis; Specification techniques · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.