A computer-implemented method may include: receiving a request to integrate a commit; obtaining analytics data of an author that developed the commit; executing a simulation using the analytics data of the author as inputs to the simulation; obtaining results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit; comparing the results of the simulation with a threshold; determining, by the computing the device, the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and outputting information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project.
|
1. A computer-implemented method comprising:
receiving, by a computing device, a request to integrate a commit that updates or modifies software;
obtaining, by the computing device, analytics data of an author that developed the commit;
executing, by the computing device, a simulation using the analytics data of the author as inputs to the simulation;
obtaining, by the computing device, results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit;
comparing, by the computing device, the results of the simulation with a threshold;
determining, by the computing the device, the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and
outputting, by the computing device, information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project,
wherein the analytics data of the author is selected from a group consisting of:
an historical rate of failure for the author;
a denial rate of merge requests;
a percentage of commits developed by the author that required rework; and
a level of rework needed per commit developed by the author, and
wherein the level of rework is used to identify one or more testing stages that are omitted.
14. A computer program product for reducing integration time of a commit, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a computing device to cause the computing device to:
receive a request to integrate a commit that updates or modifies software;
determine analytics data of the commit;
execute a simulation using the analytics data of the commit as inputs to the simulation;
obtain results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit;
compare the results of the simulation with a threshold;
determine the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and
output information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project,
wherein:
the program instructions further cause the computing device to obtain analytics data of an author that developed the commit, wherein the executing the simulation further includes using the analytics data of the author as inputs to the simulation,
the analytics data of the author is selected from a group consisting of:
an historical rate of failure for the author;
a denial rate of merge requests;
a percentage of commits developed by the author that required rework; and
a level of rework needed per commit developed by the author, and
the level of rework is used to identify one or more testing stages that are omitted.
17. A system comprising:
a CPU, a computer readable memory and a computer readable storage medium associated with a computing device;
program instructions to receive a request to integrate a commit that updates or modifies software;
program instructions to determine analytics data of the commit;
program instructions to obtain analytics data of an author that developed the commit;
program instructions to execute a simulation using the analytics data of the commit and the analytics data of the author as inputs to the simulation;
program instructions to obtain results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit;
program instructions to compare the results of the simulation with a threshold;
program instructions to determine the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and
program instructions to output information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project;
wherein the program instructions are stored on the computer readable storage medium for execution by the CPU via the computer readable memory,
wherein the analytics data of the author is selected from a group consisting of:
an historical rate of failure for the author;
a denial rate of merge requests;
a percentage of commits developed by the author that required rework; and
a level of rework needed per commit developed by the author, and
wherein the level of rework is used to identify one or more testing stages that are omitted.
2. The method of
3. The method of
a complexity of the commit;
an estimated integration time for the commit; and
an impact of the project if the commit is defective.
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
10. The method of
11. The method of
12. The method of
13. The method of
15. The computer program product of
16. The computer program product of
a complexity of the commit;
an estimated integration time for the commit; and
an impact of the project if the commit is defective.
18. The system of
a complexity of the commit;
an estimated integration time for the commit; and
an impact of the project if the commit is defective.
|
The present invention generally relates to reducing integration times in a continuous integration environment and, more particularly, to reducing integration times by omitting excessive testing procedures.
Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies to a shared mainline several times a day. CI may be performed as many as several times per day in certain systems. Continuous Delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. CI and CD aim to build, test, and release software faster and more frequently to reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. Various services are available that provide continuous integration for software deployments. Server-based systems may run in a servlet container and may support various known software deployment tools. CI is often implemented in cloud-based systems and remote application environments.
A continuous integration process may include building, testing, and reporting phases. In the testing phase, a commit undergoes a variety of different tests to ensure that the commit is compliant, performs as expected, and is free of defects that would adversely impact a project in which the commit is integrated.
In an aspect of the invention, a computer-implemented method includes: receiving, by a computing device, a request to integrate a commit; obtaining, by the computing device, analytics data of an author that developed the commit; executing, by the computing device, a simulation using the analytics data of the author as inputs to the simulation; obtaining, by the computing device, results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit; comparing, by the computing device, the results of the simulation with a threshold; determining, by the computing the device, the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and outputting, by the computing device, information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project.
In an aspect of the invention, there is a computer program product for reducing integration time of a commit. The computer program product includes a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a computing device to cause the computing device to: receive a request to integrate a commit; determine analytics data of the commit; execute a simulation using the analytics data of the commit as inputs to the simulation; obtain results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit; compare the results of the simulation with a threshold; determine the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and output information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project.
In an aspect of the invention, a system includes: a CPU, a computer readable memory and a computer readable storage medium associated with a computing device; program instructions to receive a request to integrate a commit; program instructions to determine analytics data of the commit; program instructions to obtain analytics data of an author that developed the commit; program instructions to execute a simulation using the analytics data of the commit and the analytics data of the author as inputs to the simulation; program instructions to obtain results from the simulation, wherein the results indicate error rates when one or more testing stages are omitted from a testing procedure of the commit; program instructions to compare the results of the simulation with a threshold; program instructions to determine the testing procedure based on the comparing, wherein the testing procedure identifies the one or more testing stages that are omitted and one or more testing stages that are included in the testing procedure; and program instructions to output information regarding the determined testing procedure, wherein the outputting causes an integration server to test the commit in accordance with the testing procedure as part of an integration process for integrating the commit to a project. The program instructions are stored on the computer readable storage medium for execution by the CPU via the computer readable memory.
The present invention is described in the detailed description which follows, in reference to the noted plurality of drawings by way of non-limiting examples of exemplary embodiments of the present invention.
The present invention generally relates to reducing integration times in a continuous integration environment and, more particularly, to reducing integration times by omitting excessive testing procedures. Integration testing of new commits and/or other software codes/packages for deployment is routinely performed to ensure that a new commit is compatible, safe, and properly functioning when deployed in a continuous integration software environment. Integration testing may include a series or stages of various different types of test that are performed on a commit prior to deployment. For example, integration testing may include dependency tests, static analysis, virtual machine end state comparison testing, upstream/downstream testing, etc. Integration testing may take a relatively long time to complete in a continuous integration environment. Accordingly, aspects of the present may reduce the number of tests and/or testing stages in the deployment/integration of a new commit while protecting the integrity and functionality of a project in which the commit is integrated.
As described herein, aspects of the present invention may implement statistical modeling, simulation, and/or other techniques to identify error rates and/or other measures of risk that indicate a risk associated with omitting particular testing stages in the integration of a new commit. When the risk measurement (e.g., a projected error rate of omitting a stage) satisfies a tolerance threshold, the testing stage may be omitted, thereby reducing the integration time. In this way, aspects of the present invention may reduce the amount of testing performed without significantly risking the integrity and functionality of a project, application, or code.
As described herein, aspects of the present invention may use analytics data as inputs to a statistical model to measure the risk of omitting testing stages. In embodiments, the analytics data may relate to programmer or author skill/ability, such as the historical rate of failure for a particular programmer, denial rate of merge requests for merging commits developed by the author into a project, percentage of commits that required rework, the level of rework needed per commit, etc. As such, aspects of the present invention may take programmer skill into consideration when determining whether to omit testing states and which testing stages may be omitted. In a situation in which insufficient analytics data is available for a particular programmer, no testing stages may be omitted, and analytics data regarding the programmer's abilities may be collected and stored over time to later determine testing stages that may be omitted for future commits produced by the programmer.
In embodiments, aspects of the present invention may also use analytics data for the commit itself as input to the statistical model/simulation. For example, aspects of the present invention may determine analytics data for the commit, such as the complexity of the commit, an estimate integration time for the commit, impact of a defective commit, etc. Aspects of the present invention may be more likely to omit testing stages for relatively lower complex commits, commits that take a relatively shorter amount of to integrate, and commits that have a relatively low impact if defective.
Aspects of the present invention may provide a technical solution to the technical problem of reducing integration times of commits in a build pipeline. In particular, aspects of the present invention may analyze error-related data associated with a particular user or author who produced a commit to determine a combination of testing stages that may be omitted without significantly adversely affecting a project in which the commit is integrated. Additionally, aspects of the present invention may provide a technical solution to the technical problem of reducing integration times of commits in a build pipeline by tracking and storing user error-related data for use in simulations.
The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.
Referring now to
In cloud computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 12 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a nonremovable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.
Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.
In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and testing procedure determination 96.
Referring back to
As described herein, the testing procedure determination server 220 may use the author analytics data and/or the commit analytics data as inputs into a simulation or statistical model. The outputs of the simulation may include a value or measure of risk indicating a risk level for omitting particular stages, or a particular combination of stages. For example, the outputs of the simulation may identify a level of risk (e.g., likelihood and impact of experiencing an error) when omitting testing stage A, omitting testing stage A and B, omitting testing stage B only, omitting testing stage A and C, omitting testing stage B and C, etc. The testing procedure determination server 220 may then compare the results of the simulation with a tolerance threshold (e.g., a configurable threshold that indicate the highest level of acceptable risk). The testing procedure determination server 220 may identify the combination of testing stages that may be omitted that save the most time while also being within the risk tolerance threshold.
At step 1.3, the testing procedure determination server 220 may output information indicating the testing procedure (e.g., the testing stages to perform and the testing stages that may be omitted). For example, the testing procedure determination server 220 may output information regarding the testing procedure to a integration server 230. At step 1.4, the integration server 230 may integrate the commit in accordance with the testing procedure. That is, when the testing portion of a pipeline integration procedure is initiated, the integration server 230 may perform the testing stages in accordance with the testing procedure (e.g., by omitting those procedures which, when omitted, increase the error rate by less than the tolerance threshold).
The admin device 210 may include a device capable of communicating via a network, such as the network 240. For example, the admin device 210 may correspond to a portable computer device (e.g., a laptop or a tablet computer), a desktop computer, a server, and/or another type of computing device. In some embodiments, the admin device 210 may be used by a programmer/author to develop or produce a commit request. The admin device 210 may provide the commit request to the testing procedure determination server 220 for integration into a project.
The testing procedure determination server 220 may include one or more computing devices (e.g., such as computer system/server 12 of
The integration server 230 may include one or more computing devices (e.g., such as computer system/server 12 of
The network 240 may include network nodes, such as network nodes 10 of
The quantity of devices and/or networks in the environment 500 is not limited to what is shown in
The commit receiving module 610 may include a program module (e.g., program module 42 of
The author analytics repository 620 may include a data storage device (e.g., storage system 34 of
The commit analytics data determination module 630 may include a program module (e.g., program module 42 of
The testing procedure determination module 640 may include a program module (e.g., program module 42 of
In embodiments, the testing procedure determination module 640 may use an object function may as part of the simulation to determine integration error rates when particular testing stages are included or omitted from the testing procedure. For example, the testing procedure determination module 640 may use the example object function:
f(
where
∀xj∈
Each
Equation 1 may represent the joint time of having a vector of all components that have been integrated into a pipeline with the most likely errors given the components. The output of equation 1 may represent the total time for a build. In embodiments, the testing procedure determination module 640 may minimize the time t.
In embodiments, the testing procedure determination module 640 may determine the probability that a particular error will happen if a user introduced the component using the example probability model:
P(xei|user,ū) (3)
where ū represents features about the user.
Additionally, or alternatively, the testing procedure determination module 640 may use a probability density function to determine a probably of an integration error when particular testing stages are included or omitted. In embodiments, any suitable probability density function may be used to model equation 3.
As described herein, the testing procedure determination module 640 may compare the results of the simulation with a tolerance threshold (e.g., a configurable threshold that indicate the highest level of acceptable risk). The testing procedure determination server 220 may identify the combination of testing stages that may be omitted that save the most time while also being within the risk tolerance threshold. The testing procedure determination module 640 may provide information regarding a testing procedure to the integration server 230 (e.g., a testing procedure that identifies which testing stages should be performed and which may be omitted). In embodiments, the testing procedure may identify that all tests should be performed in the event that insufficient author analytics data is available. Further, the results of tests performed may be stored by the author analytics repository 620. As data is collected over time for an author, the analytics data may be used in a simulation to determine the testing procedure for future commit requests received by the author.
As shown in
Process 700 may also include obtaining author analytics data (step 720). For example, the testing procedure determination server 220 may obtain the author analytics data from the author analytics repository 620. As described herein, the author analytics data may include information relating to the author's abilities in developing a commit, such as the historical rate of failure for the author, denial rate of merge requests, percentage of commits that required rework, the level of rework needed per commit, etc.
Process 700 may further include determining commit analytics data (step 730). For example, as described above with respect to the commit analytics data determination module 630, the testing procedure determination server 220 may determine commit analytics data, such as the complexity of the commit, an estimate integration time for the commit, an impact of a project in the event a defective commit is integrated, etc.
Process 700 may also include executing a testing procedure simulation based on author and/or commit analytics data (step 740). For example, as described above with respect to the testing procedure determination module 640, the testing procedure determination server 220 may execute a simulation and/or implements a statistical model to determine a testing procedure for the commit (e.g., a procedure that identifies which testing stages should be performed and which testing stages may be omitted). In embodiments, the testing procedure determination server 220 may execute the simulation using the author analytics data and/or the commit analytics data as inputs. In embodiments, the simulation may determine a measure of risk or an error rate for each combination of testing stages that are omitted. For example, the outputs of the simulation may identify a level of risk (e.g., likelihood and impact of experiencing an error) when omitting testing stage A, omitting testing stage A and B, omitting testing stage B only, omitting testing stage A and C, omitting testing stage B and C, etc. As described above, the testing procedure determination server 220 may use an object function and/or a probability density function to determine the level of risk when omitting testing stages.
Process 700 may further include comparing error results from the simulation with a tolerance threshold (step 750). For example, as described above with respect to the testing procedure determination module 640, the testing procedure determination server 220 may compare the results of the simulation with a tolerance threshold (e.g., a configurable threshold that indicate the highest level of acceptable risk).
Process 700 may also include determining testing stages to perform based on the comparison (step 760). For example, as described above with respect to, the testing procedure determination server 220 may identify the combination of testing stages that may be performed and which stages may be omitted (e.g., those testing stages that, when omitted, save the most time while also being within the risk tolerance threshold).
Process 700 may further include (step 770). For example, as described above with respect to the testing procedure determination module 640, the testing procedure determination server 220 may may provide information regarding a testing procedure to the integration server 230 (e.g., a testing procedure that identifies which testing stages should be performed and which may be omitted). In embodiments, the testing procedure may identify that all tests should be performed in the event that insufficient author analytics data is available. Further, the results of tests performed may be stored by the author analytics repository 620. As data is collected over time for an author, the analytics data may be used in a simulation to determine the testing procedure for future commit requests received by the author.
In embodiments, a service provider could offer to perform the processes described herein. In this case, the service provider can create, maintain, deploy, support, etc., the computer infrastructure that performs the process steps of the invention for one or more customers. These customers may be, for example, any business that uses technology. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
In still additional embodiments, the invention provides a computer-implemented method, via a network. In this case, a computer infrastructure, such as computer system/server 12 (
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Baughman, Aaron K., O'Connell, Brian M., Mcavoy, Cameron
Patent | Priority | Assignee | Title |
11328065, | Jul 26 2019 | STRIPE INC. | Architectures, systems, and methods for building trusted and secure artifacts |
Patent | Priority | Assignee | Title |
10250693, | Sep 09 2011 | Oracle International Corporation | Idempotence for database transactions |
5954665, | Jun 07 1995 | Biosense, Inc | Cardiac ablation catheter using correlation measure |
6810372, | Dec 07 1999 | III Holdings 1, LLC | Multimodal optimization technique in test generation |
6865582, | Jan 03 2000 | Battelle Energy Alliance, LLC | Systems and methods for knowledge discovery in spatial data |
7963925, | Jan 26 2005 | STUART SCHECTER, LLC D B A CARDIATOUCH CONTROL SYSTEMS | Method and apparatus for defining the effect of atrial arrhythmias on cardiac performance and directing therapy using a plurality of intrinsically and extrinsically derived signals |
9244818, | Mar 29 2011 | Amazon Technologies, Inc. | Automated selection of quality control tests to run on a software application |
9588876, | Aug 01 2014 | Microsoft Technology Licensing, LLC | Estimating likelihood of code changes introducing defects |
20030139907, | |||
20050114838, | |||
20050223281, | |||
20050278576, | |||
20060206870, | |||
20070038977, | |||
20080288834, | |||
20100298826, | |||
20150026121, | |||
20150186251, | |||
20150234730, | |||
20150277901, | |||
20150325138, | |||
20170353988, | |||
20170364354, | |||
20180191867, | |||
20180276111, | |||
20180321993, | |||
CN101082876, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Apr 05 2017 | BAUGHMAN, AARON K | International Business Machines Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 041931 | /0519 | |
Apr 05 2017 | MCAVOY, CAMERON | International Business Machines Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 041931 | /0519 | |
Apr 05 2017 | O CONNELL, BRIAN M | International Business Machines Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 041931 | /0519 | |
Apr 07 2017 | International Business Machines Corporation | (assignment on the face of the patent) | / | |||
Sep 30 2021 | International Business Machines Corporation | KYNDRYL, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 057885 | /0644 |
Date | Maintenance Fee Events |
Oct 19 2023 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Date | Maintenance Schedule |
Apr 28 2023 | 4 years fee payment window open |
Oct 28 2023 | 6 months grace period start (w surcharge) |
Apr 28 2024 | patent expiry (for year 4) |
Apr 28 2026 | 2 years to revive unintentionally abandoned end. (for year 4) |
Apr 28 2027 | 8 years fee payment window open |
Oct 28 2027 | 6 months grace period start (w surcharge) |
Apr 28 2028 | patent expiry (for year 8) |
Apr 28 2030 | 2 years to revive unintentionally abandoned end. (for year 8) |
Apr 28 2031 | 12 years fee payment window open |
Oct 28 2031 | 6 months grace period start (w surcharge) |
Apr 28 2032 | patent expiry (for year 12) |
Apr 28 2034 | 2 years to revive unintentionally abandoned end. (for year 12) |