Abstract: Implementing multiple load balancer drivers for a single load balancer is disclosed. A first request directed to a load balancer to load balance requests based on a first request selection instruction is received. A first particular load balancer driver is selected from a plurality of load balancer drivers based on a load balancer table that correlates request selection instructions to corresponding load balancer drivers of the plurality of load balancer drivers. Subsequent requests that are encompassed by the first request selection instruction directed to the load balancer are caused to be load balanced by the first particular load balancer driver.

Abstract: Systems and methods providing call identification and authentication. In one implementation, a pool of phone numbers is maintained. A request for a phone number for initiating a voice call is received from a client device. A first phone number from the pool of phone numbers is transmitted to the client device. Responsive to receiving, from the client device, the voice call at the first phone number, the client device is declared authenticated.

Abstract: Some examples of the present disclosure relate to generating a distributed debugging environment for a continuous integration (CI) pipeline. For example, a system can detect a failure of a CI pipeline in relation to a code submission for a software project, the CI pipeline being performed in a distributed CI environment including CI nodes. The system can determine a configuration of the distributed CI environment in response to detecting the failure. The system can generate a distributed debugging environment based on the configuration of the distributed CI environment, the distributed debugging environment including debugging nodes that are separate from the CI nodes. The system can modify a configuration setting of the distributed debugging environment for use in determining a source of the failure of the CI pipeline with respect to the code submission.

Abstract: A method is provided that includes receiving, from a first cluster, data intended for a second cluster and routing the data to the second cluster, thereby forming an indirect connection between a first cluster and the second cluster. A network usage of the indirect connection may be monitored and in response to determining that the network usage of the indirect connection exceeds a network usage threshold, a respective remote agent of each of the first and second clusters may be instructed to form a direct connection between the first and second clusters and remove the indirect connection.

Abstract: A method is provided that includes receiving, from a first cluster, data intended for a second cluster and routing the data to the second cluster, thereby forming an indirect connection between a first cluster and the second cluster. A network usage of the indirect connection may be monitored and in response to determining that the network usage of the indirect connection exceeds a network usage threshold, a respective remote agent of each of the first and second clusters may be instructed to form a direct connection between the first and second clusters. The network usage of the direct connection may be monitored and in response to determining that the network usage of the direct connection is below the network usage threshold, the respective remote agent of each of the first and second clusters may be instructed to remove the direct connection.

Abstract: Implementations for estimating the likelihood of successful execution of a request to create a set of computing resources in a cloud computing environment are described. An example method may include receiving, by a processing device, a request to provision a set of computing resources of a cloud computing environment, translating the request into a set of hardware specifications, determining whether the set of hardware specifications is within a quota associated with an initiator of the request, determining whether the cloud computing environment has sufficient available computing resources matching the set of the hardware specifications, and notifying the initiator of the request of the availability of the computing resources specified by the request.

Abstract: Software application dependency trees can be generated and used for white-box testing. In some examples, a method may involve receiving a request to generate a dependency tree for a first software application associated with a computing device. The method may also include identifying a set of software applications also associated with the computing device, each of which the first software application is determined to be dependent upon based on information included in a specification for the first software application. The method may also include receiving, by the computing device with respect to the set of software applications, a corresponding set of dependency trees. The method may further include incorporating each of the dependency trees in the set of dependency trees into the dependency tree for the first software application via a respective incorporation point, and returning the dependency tree for the first software application in response to the request.

Abstract: A method includes receiving a depiction with one or more elements, each element having a location within the depiction. The depiction is analyzed to identify at least one of a first type of element. The depiction is further analyzed to identify at least one of a second type of element. The location of the first and second types of elements is also identified. The method next includes creating an output comprising code to be used in a CI/CD job based on the elements in the analyzed received depiction and their location.

Abstract: Implementations for estimating the likelihood of successful execution of a request to create a set of computing resources in a cloud computing environment are described. An example method may include receiving, by a processing device, a request to provision a set of computing resources of a cloud computing environment, translating the request into a set of hardware specifications, determining whether the set of hardware specifications is within a quota associated with an initiator of the request, determining whether the cloud computing environment has sufficient available computing resources matching the set of the hardware specifications, and notifying the initiator of the request of the availability of the computing resources specified by the request.

Abstract: A method is provided that includes receiving, from a first cluster, data intended for a second cluster and routing the data to the second cluster, thereby forming an indirect connection between a first cluster and the second cluster. A network usage of the indirect connection may be monitored and in response to determining that the network usage of the indirect connection exceeds a network usage threshold, a respective remote agent of each of the first and second clusters may be instructed to form a direct connection between the first and second clusters. The network usage of the direct connection may be monitored and in response to determining that the network usage of the direct connection is below the network usage threshold, the respective remote agent of each of the first and second clusters may be instructed to remove the direct connection.

Abstract: Problematic code changes that broke a software build can be identified. For example, a system can identify a broken software build and a last stable software-build associated with a software project, and generate a history of code commits associated with the software project based on commit logs from commit repositories. The code commits in the history were applied to the software project after the last stable software-build and before the broken software build. The system can then iteratively test the code commits in the history to determine a problematic code-commit that is at least partially responsible for the broken software build.

Abstract: Providing an enhanced continuous integration (CI)/continuous delivery (CD) build script debugging environment is disclosed. In one example, the CI/CD build script debugging environment inserts a breakpoint within a CI/CD build script that includes one or more build script steps. During execution of the CI/CD build script within the CI/CD build script debugging environment, execution is paused at the breakpoint, and a language-specific debugging environment suitable for debugging the next build script step is automatically identified and launched. Some examples may also provide that the CI/CD build script debugging environment allows the user to resume execution of the CI/CD build script within the CI/CD build script debugging environment without further pauses, and/or to “step over” a build script step by executing the build script step within the CI/CD build script debugging environment without launching a language-specific debugging environment.

Abstract: Virtualized computing resources can be managed in a cloud computing environment. For example, a system can receive input indicating that a cloud computing environment is to be reverted back to a prior state prior to an event occurring. Based on the input, the system can determine actions that were performed in the cloud computing environment in response to the event. Each action can involve a creation, a modification, or a deletion of a virtualized computing resource in the cloud computing environment. The system can determine a particular order in which the actions were performed by analyzing timestamps corresponding to the actions. The system can then revert the cloud computing environment back to the prior state by performing an inverse of each action in the plurality of actions in a reverse order to the particular order.

Abstract: Problematic code changes that broke a software build can be identified. For example, a system can identify a broken software build and a last stable software-build associated with a software project, and generate a history of code commits associated with the software project based on commit logs from commit repositories. The code commits in the history were applied to the software project after the last stable software-build and before the broken software build. The system can then iteratively test the code commits in the history to determine a problematic code-commit that is at least partially responsible for the broken software build.

Abstract: Software application dependency trees can be generated and used for white-box testing. In some examples, a method may involve receiving a request to generate a dependency tree for a first software application associated with a computing device. The method may also include identifying a set of software applications also associated with the computing device, each of which the first software application is determined to be dependent upon based on information included in a specification for the first software application. The method may also include receiving, by the computing device with respect to the set of software applications, a corresponding set of dependency trees. The method may further include incorporating each of the dependency trees in the set of dependency trees into the dependency tree for the first software application via a respective incorporation point, and returning the dependency tree for the first software application in response to the request.

Abstract: A method includes receiving a depiction with one or more elements, each element having a location within the depiction. The depiction is analyzed to identify at least one of a first type of element. The depiction is further analyzed to identify at least one of a second type of element. The location of the first and second types of elements is also identified. The method next includes creating an output comprising code to be used in a CI/CD job based on the elements in the analyzed received depiction and their location.

Abstract: Providing an enhanced continuous integration (CI)/continuous delivery (CD) build script debugging environment is disclosed. In one example, the CI/CD build script debugging environment inserts a breakpoint within a CI/CD build script that includes one or more build script steps. During execution of the CI/CD build script within the CI/CD build script debugging environment, execution is paused at the breakpoint, and a language-specific debugging environment suitable for debugging the next build script step is automatically identified and launched. Some examples may also provide that the CI/CD build script debugging environment allows the user to resume execution of the CI/CD build script within the CI/CD build script debugging environment without further pauses, and/or to “step over” a build script step by executing the build script step within the CI/CD build script debugging environment without launching a language-specific debugging environment.

Abstract: Dynamically revising an in-process build is disclosed. A build system receives a build configuration comprising information that defines a plurality of successive stages. Each stage includes at least one step, and one or more of the stages include a plurality of successive steps. The build configuration defines a build process that, when completed, alters a state of a storage device. The build system initiates a build process sequence on the build configuration. The build system, after initiating the build process sequence, receives notification of a desire to add a revision to a particular stage of the plurality of stages defined in the build configuration. A determination is made that performance of the particular stage has or has not begun. In response to the determination, a subsequent build process action is performed.

Abstract: Implementing multiple load balancer drivers for a single load balancer is disclosed. A first request directed to a load balancer to load balance requests based on a first request selection instruction is received. A first particular load balancer driver is selected from a plurality of load balancer drivers based on a load balancer table that correlates request selection instructions to corresponding load balancer drivers of the plurality of load balancer drivers. Subsequent requests that are encompassed by the first request selection instruction directed to the load balancer are caused to be load balanced by the first particular load balancer driver.

Abstract: Virtualized computing resources can be managed in a cloud computing environment. For example, a system can receive input indicating that a cloud computing environment is to be reverted back to a prior state prior to an event occurring. Based on the input, the system can determine actions that were performed in the cloud computing environment in response to the event. Each action can involve a creation, a modification, or a deletion of a virtualized computing resource in the cloud computing environment. The system can determine a particular order in which the actions were performed by analyzing timestamps corresponding to the actions. The system can then revert the cloud computing environment back to the prior state by performing an inverse of each action in the plurality of actions in a reverse order to the particular order.