BACKGROUND

The present disclosure relates generally to a system and method for creating and executing interfaces to incident systems and continuous integration systems.

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

Cloud computing relates to the sharing of computing resources that are generally accessed via the Internet. In particular, a cloud computing infrastructure allows users, such as individuals and/or enterprises, to access a shared pool of computing resources, such as servers, storage devices, networks, applications, and/or other computing based services. By doing so, users are able to access computing resources on demand that are located at remote locations, which resources may be used to perform a variety computing functions (e.g., storing and/or processing large quantities of computing data). For enterprise and other organization users, cloud computing provides flexibility in accessing cloud computing resources without accruing large up-front costs, such as purchasing expensive network equipment or investing large amounts of time in establishing a private network infrastructure. Instead, by utilizing cloud computing resources, users are able redirect their resources to focus on their enterprise's core functions.

Within the context of cloud computing solutions for data repositories, users may be asked to deal with ever increasing amounts of data, e.g., including certain date-based information stored in the data repositories. In fact, the amount of cloud-based and date-based data collected and stored in today's cloud computing solutions, such as cloud-based repositories, may be orders of magnitude greater than what was historically collected and stored. Users tasked with automating and/or troubleshooting enterprise, IT, and/or other organization-related functions (e.g., incident tracking and/or help desk-related functions) navigate ever increasing amounts of date-based data to properly and efficiently perform their job functions. In certain embodiments, cloned data repositories may be created. With this in mind, the following embodiments are directed to improving the manner in which certain objects for certain data repositories, including cloned data repositories, may be developed via incident systems and/or continuous integration systems.

SUMMARY

A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.

Information Technology (IT) networks may include a number of computing devices, server systems, databases, and the like that generate, collect, and store information. As increasing amounts of data representing vast resources become available, it becomes increasingly difficult to analyze the data, interact with the data, and/or provide reports for the data. The current embodiments enable customized systems and methods that may include an integration hub enabling the creation of integration “spokes.” For example, an incident integration spoke may be used to interface with incident or issue management systems, such as Jira®. Jira® is available from Atlassian, Co., of London, United Kingdom. A continuous integration (CI) spoke may be used to interface with continuous integration (CI) systems such as Jenkins. Jenkins is available via the Jenkins project headed by the Software in the Public Interest (SPI), a non-profit 501 (c) (3) organization, of New York, U.S.A.

The incident integration spoke may interface with the incident management system to track and manage issues. Issues tracked by the incident system may include new features to add to certain software applications, bugs found in the software applications, tasks (e.g., software development tasks) to complete, and so on. The issues may then be tracked and managed via visual dashboards and workflow tracking as the software is developed and/or maintained.

In certain embodiments, the techniques described herein may automate the code merging and building of software, for example, on a continuous (e.g., scheduled) basis via the CI integration spoke. For example, source code from multiple sources may be tested (e.g., unit tested) via the CI system and combined into a main branch corresponding to a software application. Commits to a source repository, manual triggers and the like, may additionally or alternatively be used by the CI system to execute builds (e.g., compiles) of the main branch and/or other code branches.

The integration hub may additionally include or operatively couple with visual development tools, including a Flow Designer system. The Flow Designer system may be used by non-technical personnel, among others, to develop code. For example, the Flow Designer system may enable the non-technical personnel to use natural language to more easily create and visualize objects and flows that automate certain tasks. Indeed, information flow objects may be created without typing or otherwise entering text in a programming language.

