International Business Machines Corporation

Christopher Lawrence Brealey

Shinoj Zacharias

Vladimir Klicnik

Lok Tin Loi

Dirk Alexander Seelemann, Ii

Christopher N Taylor

Jeffrey Grant Johnston

David Martin Lauzon

Thomas C Schmidt

Ritchard Leonard Schacher

Jason Ashley Sholl

Yen Lu

Simon Helsen

Philippe Mulet

Joel Cayne

Zina Mostafia

A method, computer program product, and system includes a processor(s) identifying one or more resources of a shared computing environment utilized in delivery of an application, to users of the shared computing environment. The processor(s) monitors communications to the one or more resources, to identify and intercept operations related to delivery of the application. The processor(s) analyze the intercepted operations, to determine when the operations comprise a pattern occurring with a frequency indicative of a predetermined level of confidence, where the pattern comprises one or more delivery operations. Based on determining the pattern occurs with the frequency, the processor(s) generates an automated delivery pipeline for the application, where the automated delivery pipeline automates at least one of the one or more delivery operations comprising the pattern. The processor(s) utilizes the automated delivery pipeline to deliver a new version of the application.

Automatic creation of delivery pipelines

Examining source code repositories for indications of orthogonal technologies in actual use or of potential usefulness in the development and continuous delivery of the contents of the repositories.

System for modeling toolchains-based source repository analysis

The method includes identifying a test report log for a regression test. The method further includes identifying one or more errors in the identified test report log. The method further includes determining a severity category for the one or more identified errors in the identified test report log. The method further includes determining a severity category for the identified test report log based on the determined severity category for the one or more identified errors in the identified test report log.

Identifying severity of test execution failures by analyzing test execution logs

A query for data in a UDDI registry is developed. A URI query having parameters that identify the data is provided. A UDDI query having a UDDI specified format based on the parameters in the URI query is generated. The UDDI query is sent to the UDDI registry.

UDDI metadata query development

A computer algorithm is encapsulated in at least two modules: at least one communication operation of the computer algorithm is encapsulated in a communication module, separately from the rest of the operations of the algorithm which may be encapsulated in an algorithm module. The separately encapsulated communication operation is made available to the algorithm module during its execution. Modules for data objects encapsulating data communicated may also be provided. A framework may be provided to ensure compatibility between different modules, wherein a plurality of protocols are provided and each module implements a corresponding protocol. All environment-dependent communication operations may be separately encapsulated so that one of the communication module and the algorithm module may be modified without modifying the other.

Separate encapsulation of communication operations in computer algorithms

A metadata repository for use in an integrated development environment is provided. The metadata repository is layered to define levels of common behaviour useful to different types of application development tools. The most general use tools have access to metadata at the level of simple constructed types; more specialised tools have access to components that contain properties of a target language; highly specialised tools have access to composed partitionable part metadata that can be used for constructing distributed applications.

Hierarchical metadata store for an integrated development environment

When data, such as tool data, is commonly accessible, there is a danger that concurrent user processes will make overlapping modifications and leave the data in an incomplete or incomprehensible state. The invention provides a locking mechanism to guard against this. The lock objects are maintained in pool or repository. Two types of lock objects are provided; shareable locks that may be shared by many user processes and permit only read access to the locked data, and exclusive locks, useable by only one user process at a time, that permit the owning process to modify the locked data.

Growing community of inventors

Markham, Canada

Christopher Lawrence Brealey