Hewlett Packard Enterprise Development LP

Micro Focus Lcc

Entit Software LLC

Hewlett-Packard Development Company, L.p.

Miroslav Novak

Albert Regner

Petr Dousa

Filip Blaha

Lukas Barton

Jan Vana

Gil Baruch

Vladimir Dubsky

Adi Godkin

Noam Kachko

Vojtěch Janota

Gali Brafman

Roman Rubas

Liran Levy

Petr Panuska

In some examples, continuous integration and continuous deployment (CI/CD) system failure analysis and resolution may include analyzing data for a CI/CD system to identify anomalous tests related to the CI/CD system. A plurality of hypotheses on a cause of failure associated with the CI/CD system may be determined based on a further analysis of the analyzed data. The determined hypotheses may be prioritized based on a confidence level analysis. Failure resolution to prevent failure associated with the CI/CD system may be determine based on a response to one of the prioritized hypotheses. Further, the determined failure resolution may be implemented.

Continuous integration and continuous deployment system failure analysis and resolution

According to an example, dynamic build pipeline execution may include extracting a pipeline flow related to build jobs, and generating, by using the extracted pipeline flow, a pipeline model that includes a plurality of pipelines related to the pipeline flow. Each pipeline of the plurality of pipelines may represent a set of related build jobs, and include an entry point to access the set of related build jobs. Dynamic build pipeline execution may further include generating another model related to the pipeline model to execute a build job of the set of related build jobs for a pipeline of the plurality of pipelines based on a parameter specified for the another model.

Dynamic build pipeline execution

A technique includes tracking changes to a code base using a source code management application; and maintaining a correlation between defects in the code base and changes addressing the defects. The technique includes determining a defect density in a subset of the code base associated with implementation of a requirement for the code base. Determining the defect density includes identifying how many defects are addressed by changes that modify the subset of the code base.

Identifying a defect density

Disclosed herein is a system and method that determine whether activity pertaining to a software development project violates at least one development rule whose associated severity level exceeds a predetermined threshold.

Software development activity

A system to generate an interactive layered visualization of a software system includes a storage device to storage a model of the system that defines entities and relationships among entities. The system also includes a visualization tool to generate nodes representing the entities and assign nodes to layers in a set of ordered layers in accordance with rules associated with each layer. A layered layout of the software system is thereby generated and an interactive visualization of the layered layout is rendered for display to the user.

Interactive layered visualization of a layered software architecture

A technique to determine defect density in a portion or subset of code. Changes to code may be tracked. Defects in the code that are addressed by the changes may also be tracked. A defect density in a portion or subset of the code having a characteristic can be determined by identifying changes modifying the portion or subset of the code and that address a defect.

A computer implemented method includes extracting requirement data from a software development system, the requirement data defining a software development requirement during a predetermined period of time. The method further includes extracting from the software development system an indication of a state of software development at the beginning of the period of time, and an indication of a state of software development at the end of the period of time. The method further includes calculating a change in the state of software development during the period of time and generating a report that enables comparing the calculated change in the state of software development with the software development requirement. A computer readable medium product and a data processing system are also disclosed.

System and method for software development report generation

A test planning tool for defining a test plan for testing updates to a software product aggregates information from a variety of diverse sources to generate an application model. The application includes a detailed model of the components of the application and their dependencies, a logical structure of the components, requirements associated with changes to the components, organizational entities responsible for the changes, and various other information, such as test coverage and defect information. The application model is presented to the user in a manner that allows the user to select components of interest, drill down and view change details and requirements, and to use that information to develop a test plan.

Test planning tool for software updates

A method of migrating artifacts between service-oriented architecture repositories is provided herein. The method includes receiving a request to export an artifact from a first repository. The artifact comprises metadata associated with a service-oriented architecture. Additionally, the method includes retrieving data from one or more aggregated relationships of the artifact. The method also includes packaging the retrieved data into a data store comprising the selected data.

Growing community of inventors

Prague, Czechia

Miroslav Novak