Abstract: A remote build orchestrator for building and testing a software program is described. The remote build orchestrator 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 includes 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. The remote build orchestrator also includes 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. The remote build orchestrator further includes 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.

Abstract: 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.

Abstract: A build system for compiling and building software projects includes an integrity verification system that serves as a gate for whether to add code to a repository. When the build system receives a software package, the integrity verification system determines an integrity level for the received software package, which may be based on the intended use of the software and how other pieces of software depend on the software package. The integrity verification system determines whether the software package meets the requirements of the determined integrity level, e.g., in terms of code review, code testing, adherence to best practices, etc.

Abstract: Software code is tested to determine relative performance of the software code. Successfully executing a test may be used to flag problems in a code repository to be corrected or criteria for accepting code for acceptance to the repository. To further evaluate test results, the test may be run several times on the same code version to determine a test result stability score describing how the test results may vary in different executions, such as a frequency that the code passes the test. Based on the score, additional tests may be run to further refine test result stability score. To evaluate time-variance of testing, when a code version fails a test, a previous version of the code may be run with the same test and the results compared to determine if a new regression was introduced.