Abstract: A data processing system implements receiving a definition of a software pipeline in an entry point file and referenced templates; dividing the definition of the software pipeline into a pipeline definition skeleton and tasks which definitions included in the definition of the software pipeline; determining each of the tasks as allowed or disallowed according to an output template, and applying a code-driven or AI-driven function to modify any disallowed task into converted/allowed task(s); constructing a first prompt by appending the allowed task and the converted/allowed task(s) to a first instruction string including instructions to a generative model to re-arrange the allowed task and the converted/allowed task(s) into a new definition of the software pipeline; providing the first prompt to the generative model and receiving the new definition of the software pipeline from the generative model; and delivering the new definition of the software pipeline to a user device.

Abstract: A data processing system implements receiving a definition of a software pipeline in an entry point file and referenced templates; dividing the definition of the software pipeline into a pipeline definition skeleton and tasks which definitions included in the definition of the software pipeline; determining each of the tasks as allowed or disallowed according to an output template, and applying a code-driven or AI-driven function to modify any disallowed task into converted/allowed task(s); constructing a first prompt by appending the allowed task and the converted/allowed task(s) to a first instruction string including instructions to a generative model to re-arrange the allowed task and the converted/allowed task(s) into a new definition of the software pipeline; providing the first prompt to the generative model and receiving the new definition of the software pipeline from the generative model; and delivering the new definition of the software pipeline to a user device.

Abstract: Disclosed are embodiments for reducing processing requirements in complex build environments. Complex build environments frequently perform multiple builds per day, in some cases, multiple builds are occurring in parallel. Some of these builds and some fail. Moreover, a definition of success or failure of a build can vary across individual engineers or teams of engineers. In a complex build environment that is rapidly generating multiple build results simultaneously, identifying which builds are appropriate for use can be difficult. Many teams solve this problem by increasing a frequency of builds to rapidly detect any problems with documents recently checked into a document repository. However, this relatively high frequency of builds can impose large processing and/or cost burdens on an organization. By providing sophisticated methods of extracting validation information from existing builds, the disclosed embodiments reduce processing requirements and improved efficiency of enterprise build environments.

Abstract: Disclosed are embodiments for reducing processing requirements in complex build environments. Complex build environments frequently perform multiple builds per day, in some cases, multiple builds are occurring in parallel. Some of these builds and some fail. Moreover, a definition of success or failure of a build can vary across individual engineers or teams of engineers. In a complex build environment that is rapidly generating multiple build results simultaneously, identifying which builds are appropriate for use can be difficult. Many teams solve this problem by increasing a frequency of builds to rapidly detect any problems with documents recently checked into a document repository. However, this relatively high frequency of builds can impose large processing and/or cost burdens on an organization. By providing sophisticated methods of extracting validation information from existing builds, the disclosed embodiments reduce processing requirements and improved efficiency of enterprise build environments.

Abstract: Software build isolation is provided. Systems, methods and computer-readable devices provide for receiving a request from a user who is a member of a team or group for allocation of a machine from a pool of machines. A determination is made as to whether a limit has been reached on the number of machines available to the team or group. If the limit has not been reached, the machine is provisioned and the user is notified that the machine has been provisioned and allocated to the user. In addition, in response to receiving a notification that an asset is ready for backup, an asset is replicated on an archive server. Dependencies of the asset on dependent assets are determined and the dependent assets are replicated on the archive server.

Abstract: Software build isolation is provided. Systems, methods and computer-readable devices provide for receiving a request from a user who is a member of a team or group for allocation of a machine from a pool of machines. A determination is made as to whether a limit has been reached on the number of machines available to the team or group. If the limit has not been reached, the machine is provisioned and the user is notified that the machine has been provisioned and allocated to the user. In addition, in response to receiving a notification that an asset is ready for backup, an asset is replicated on an archive server. Dependencies of the asset on dependent assets are determined and the dependent assets are replicated on the archive server.

Abstract: Software build isolation is provided. Systems, methods and computer-readable devices provide for receiving a request from a user who is a member of a team or group for allocation of a machine from a pool of machines. A determination is made as to whether a limit has been reached on the number of machines available to the team or group. If the limit has not been reached, the machine is provisioned and the user is notified that the machine has been provisioned and allocated to the user. In addition, in response to receiving a notification that an asset is ready for backup, an asset is replicated on an archive server. Dependencies of the asset on dependent assets are determined and the dependent assets are replicated on the archive server.

Abstract: Management of an extensive code database having multiple user tenants building code is provided. A request to check-in code is received, and a build and validation to check-in the update to a user's code is performed. The validation results in indication of an error due to a bad state of the system that performed the build. The build machine is rebooted, and a second build is performed. Optionally, a user is prompted during a grace time period to cancel the corrective action of rebooting the build machine. Optionally, the validation error may be indicated as a product issue, a network issue, or a known limitation in the compiler. Optionally, other corrective actions such as preventing retrying the build and escalating the error may be taken. Optionally, the build may be prevented when the check-in includes code that produced an error on a previous build.

Abstract: Cross-machine build scheduling of a codebase is provided. Systems, methods and computer-readable devices provide for breaking a monolithic codebase into a plurality of tenants. A file containing entries associated with one of the tenants is read, and a selected entry in the file is examined to determine if the entry is requesting the execution of parallel loop. If so, each loop of the parallel loops is executed in parallel, and the selected entry in the file is examined to determine if the entry is an independent loop. If so, the independent loop is executed, and the selected entry in the file is examined to determine if the entry is a dependent loop. If so, execution of the dependent loop is held.

Abstract: Software build isolation is provided. Systems, methods and computer-readable devices provide for receiving a request from a user who is a member of a team or group for allocation of a machine from a pool of machines. A determination is made as to whether a limit has been reached on the number of machines available to the team or group. If the limit has not been reached, the machine is provisioned and the user is notified that the machine has been provisioned and allocated to the user. In addition, in response to receiving a notification that an asset is ready for backup, an asset is replicated on an archive server. Dependencies of the asset on dependent assets are determined and the dependent assets are replicated on the archive server.

Abstract: Management of a monolithic code is provided. A request to check-in a first code into a first tenant code of the monolithic code may be received. In response to receiving the request to check-in the first code, a first build of the first tenant code may be performed. A validation of the first build may be performed. Validation results may be provided.

Abstract: Detecting machine utilization activity may be provided. Client machine activity within a computer network may be monitored to determine if the client machine is available for use, or if the computer is already engaged in one or more activities. During a predetermined receive period, machine activity information for a given client machine. The machine activity information for the client machine is compared to previously stored machine activity information to determine if an activity state for the client machine has changed. If the activity state of the client machine has changed, the activity state for the machine is updated. Machine activity information for all computers in the computer network may be used to track and optimize resources with the computer network.

Abstract: Various technologies and techniques are disclosed for using historical trends from prior tests to prioritize how failures are reported in later tests. After a user changes a software development project, one or more tests are run to detect failures during execution of the tests. Any detected failures are analyzed in comparison with historical failures for the software development project across tests run for multiple users. Any detected failures are categorized as new or old. New failures are reported with a different emphasis than old failures, such as with new failures being reported as a higher priority than old failures.

Abstract: Detecting machine utilization activity may be provided. Client machine activity within a computer network may be monitored to determine if the client machine is available for use, or if the computer is already engaged in one or more activities. During a predetermined receive period, machine activity information for a given client machine. The machine activity information for the client machine is compared to previously stored machine activity information to determine if an activity state for the client machine has changed. If the activity state of the client machine has changed, the activity state for the machine is updated. Machine activity information for all computers in the computer network may be used to track and optimize resources with the computer network.