Continuous Integration Process Research Articles

Managing and editing UML documents: structure, integration, automation

Unified Modeling Language (UML) plays an important role in the modern software development process by offering standardized methods for visual modeling, analysis, and design of complex systems. This paper discusses the main aspects of storing, editing, and integrating UML documents with integrated development environments (IDEs). The main focus is on comparing the two main formats for storing UML models – XML Metadata Interchange (XMI) and JavaScript Object Notation (JSON). XMI, being an official standard developed by Object Management Group, provides a high degree of detail and compatibility with various UML tools, making it preferable for large and complex projects that require support for the full UML specification. At the same time, JSON is simple and flexible, which makes it suitable for projects where speed of development and ease of integration are important, although it is inferior to XMI in describing complex aspects of UML models. The paper analyzes in detail the methods of editing UML documents, including manual editing and automated approaches, using APIs and scripts. Manual editing is useful when you need to make small changes to the structure of a UML document, but it can be time-consuming and error-prone when working with large projects. Automation, on the other hand, provides effective tools for mass editing and generating UML elements, which significantly speeds up development and minimizes the likelihood of errors, especially since modern tools such as StarUML offer the necessary tools for programmatically modifying UML documents by integrating them into development processes. Combining of UML documents with integrated development environments also plays a key role in increasing development efficiency, as this allows automating code generation based on UML models, maintaining synchronization between code and diagrams, and facilitating visualization and documentation of architectural solutions. Despite the significant advantages, there are challenges associated with limited support for all UML features and potential conflicts between models and code. This only emphasizes the need for further research in this area. Prospects for further research include the development of new methods and tools for working with UML documents, improving their integration with development environments, and using artificial intelligence to automate the analysis and design of UML models. Attention should also be paid to the using of UML with continuous integration processes, which can significantly increase the flexibility and adaptability of software development. Thus, the study of the structure of storing, editing, and integrating UML documents is an important area for optimizing the design and development of modern software systems.

Automating Test Reporting: Integrating Allure Reports with GitHub Workflows for Enhanced Software Testing

Allure Reports, an open-source framework, significantly enhance the visualization and comprehensibility of test results in software testing. This paper explores the integration of Allure Reports with GitHub Workflows to automate the generation, publication, and management of detailed and interactive test reports. The primary focus is on improving communication, debugging processes, and overall testing efficiency through auto- mated, real-time reporting solutions. Key features of Allure Re- ports include interactive visualizations, comprehensive overviews, detailed test case information, customizable reports, and seamless integration with Continuous Integration/Continuous Deployment (CI/CD) pipelines. Additionally, the paper discusses the role of GitHub Pages and GitHub Artifacts in making test results accessible and supporting continuous integration and delivery processes. The implementation of this integration resulted in enhanced transparency, collaboration, and efficiency within development teams, as well as improved test result visibility and debugging capabilities. Empirical studies support our findings, highlighting improvements in task efficiency and reduced debugging time through the use of automated reporting and continuous integration practices [1- 3].

A conceptual model of the continuous glucose monitoring integration process for older adults with diabetes developed using participatory systems science methods

AimsContinuous glucose monitoring (CGM) use remains low in older adults. We aimed to develop a conceptual model of CGM integration among older adults with type 1 and type 2 diabetes. MethodsWe previously engaged older adults with type 1 diabetes using participatory system science methods to develop a model of the system of factors that shape CGM integration. To validate and expand the model, we conducted semi-structured interviews with 17 older adults with type 1 and type 2 diabetes and 3 caregivers. Vignettes representing each integration phase were used to elicit outcomes and strategies to support CGM use. Data were analyzed using team-based causal loop diagraming. ResultsThe model includes six phases spanning (1) CGM uptake; (2) device set-up; acquisition of (3) belief in oneself to use CGM effectively; (4) belief that CGM is preferable to blood glucose monitoring; (5) belief in future CGM benefits CGM; and (6) development of a sense of reliance on CGM. Causal loop diagrams visualize factors and feedback loops shaping outcomes at each phase. Participants proposed support strategies spanning clinical, educational, and behavioral interventions. ConclusionsThe model underscores the complex transition of learning new technology and provides opportunities for tailored support for older adults.

Performance Analysis of Devops Practice Implementation Of CI/CD Using Jenkins

Continuous Integration and Continuous Delivery (CI/CD) are methods used in agile development to automate and speed up the process of building, testing, and validating services. To support and simplify all development and deployment processes, several methods such as containerized and CI/CD automation are needed. In this research, a DevOps Practice is carried out which includes process integration, deployment, and testing automatically using a tool called Jenkins. These tools are open source automation servers to help the Continuous Integration and Continuous Deployment process. Jenkins is equipped with various open source plugins that can be used to simplify and assist CI/CD automation and testing processes. The implementation of CI/CD in performance testing makes the testing process integrated, automated, and can be run on a regular basis.

Научно-технологический потенциал как стратегический ресурс союзной экономики

Scientific and technological potential of the country is formed due to the continuous progressive integration process of fundamental and applied science achievements into practice of economic activity of the subjects of the real sector of the national economy. The directions of scientific, technical, and innovative development ensure the creation of innovative production facilities to produce of science intensive and high-tech products. Successful Belarusian-Russian cooperation ensures further development of scientific, technological and innovative potential of a unique interstate association - the Union State. The improvement of technical means and production technologies leads not only to the production structure optimization and improvement of management systems and production organization, but also to the emergence of new professions, development of the personnel professional competencies, increasing the requirements of the employers to the intellectual level and quality of professional training and radical transformation of labour market.

Addressing Performance and Scalability Issues in Large-Scale Jenkins Deployments

Jenkins, an open-source automation server, has become a cornerstone in modern software development pipelines, facilitating continuous integration and delivery (CI/CD) processes. However, as the scale of Jenkins deployments increases, organizations encounter significant challenges related to performance and scalability. This review paper delves into the various strategies and approaches aimed at mitigating these challenges in large-scale Jenkins deployments. The paper begins by identifying the key performance bottlenecks and scalability limitations inherent in Jenkins at scale. It explores the impact of factors such as increased workload, extensive plugin usage, and complex pipeline configurations on Jenkins’ performance. Subsequently, the review examines existing research and industry practices in addressing these issues. Several techniques have been proposed and implemented to enhance the performance and scalability of Jenkins deployments. These include optimizing resource utilization through efficient job scheduling algorithms, leveraging distributed architectures to distribute workloads across multiple nodes, and employing caching mechanisms to reduce build times and alleviate strain on Jenkins masters. Furthermore, the paper discusses the role of infrastructureas-code (IaC) practices and containerization technologies in streamlining Jenkins deployments and improving scalability. Moreover, the paper highlights the importance of monitoring and instrumentation in identifying performance bottlenecks and optimizing Jenkins deployments continuously. It discusses various monitoring tools and techniques for gathering performance metrics and diagnosing issues in large-scale Jenkins environments. Overall, this paper provides valuable insights into the challenges faced by organizations deploying Jenkins at scale and offers a comprehensive overview of strategies and best practices for addressing performance and scalability issues. By adopting these approaches, organizations can ensure the efficient operation of their Jenkins infrastructure, enabling smoother CI/CD workflows and enhancing overall software delivery capabilities.

Social Network Analysis of Indonesia Migrant Workers in Hong Kong: Study Social Integration Between Health Care and “KOTKIHO”

In the research, the relationship between the social networks of migrant domestic workers from Indonesia in Hong Kong and the accessibility of medical care and legal protection is investigated. To help others and support the struggle of BMI organizations and groups in Hong Kong, the Coalition of Indonesian Labor Organizations in Hong Kong (KOTKIHO) was founded out of concern and solidarity.. Similarly, participant observations from formal and informal activities were used in this research, which also drew on field notes. In order to control risk and gain access to resources for their health and well-being, KOTKIHO strategically use their strong and weak ties, deciding within their social network who and what to discuss with reference to medical issues. For characterizing and assessing the continuous dynamic social integration process, researchers suggest using social network analysis. Their employers, who can also provide them with access to institutional and social resources, are carefully negotiated with regarding their rights and opportunities. Participate in online discussions and debates regarding the health policies of their native and host nations. To better comprehend the complexity and intricacy of social integration, social network analysis must be done using a mixed-methods approach due to its limitations as a relatively new tool in the field of social integration research. It also demonstrates the establishment, activation, and mobilization of migrant social networks around discourses on state-designed immigration-related health policy

Effects of Maker Education Integrating ARCS on Learners' Performance, Motivation, Self-Efficacy

Maker movement has become very popular in recent years. It is a process of continuous experimentation, integration, and thinking of a series of practical skills and creative ideas. The application of maker in education can be called Maker Education. In the learning process of maker education, if learners have the ability to integrate interdisciplinary knowledge, this process will be more effective. On the other hand, some scholars pointed out that the Maker movement is a trial-and-error cycle and requires multiple capabilities such as reflection, feedback, communication, and coordination. However, most learners are lack these abilities, and they also prone to frustration and learned helplessness in the learning process, especially learners with low and medium learning achievements.

Extended Model of Code Orchestration and Deployment Platform

This paper is focused on the process of continuous integration and respective orchestration tooling. It provides a summary on existing tooling with feature analysis and applications. The research explores techniques, processes, and solutions for code orchestration. It includes a comparison of the modern platforms and discusses the topic of extendibility of such products by presenting an architectural model that supports the integration of general-purpose extensions.

Multi-Disciplinary Access in Conceptual Design for Advertising of The Public Space

This master's thesis is a qualitative empirical research for multidisciplinary conceptualization of an urban public space, with emphasis on development processes for affirmation of ecological and social sustainability, and structuring of socio-spatial relations. The research includes an inter-contextual analysis of a comprehensive theoretical context and a specific case study that highlights urban community gardens as potential initiatives for spatial and social reshaping. The findings of the research support a conceptual design of public space that popularly does not result in a tangible product, but can also be activism for rethinking what exists or a continuous process of socio-spatial relations. The research complements the theoretical framework of the design methodology with conceptual analysis of the design as a process of continuous integration of several disciplines.

SecDocker: Hardening the Continuous Integration Workflow

Current Continuous Integration (CI) processes face significant intrinsic cybersecurity challenges. The idea is not only to solve and test formal or regulatory security requirements of source code but also to adhere to the same principles to the CI pipeline itself. This paper presents an overview of current security issues in CI workflow. It designs, develops, and deploys a new tool for the secure deployment of a container-based CI pipeline flow without slowing down release cycles. The tool, called SecDocker for its Docker-based approach, is publicly available in GitHub. It implements a transparent application firewall based on a configuration mechanism avoiding issues in the CI workflow associated with intended or unintended container configurations. Integrated with other DevOps Engineers tools, it provides feedback from only those scenarios that match specific patterns, addressing future container security issues.

Parallel Test Prioritization

Although regression testing is important to guarantee the software quality in software evolution, it suffers from the widely known cost problem. To address this problem, existing researchers made dedicated efforts on test prioritization, which optimizes the execution order of tests to detect faults earlier; while practitioners in industry leveraged more computing resources to save the time cost of regression testing. By combining these two orthogonal solutions, in this article, we define the problem of parallel test prioritization, which is to conduct test prioritization in the scenario of parallel test execution to reduce the cost of regression testing. Different from traditional sequential test prioritization, parallel test prioritization aims at generating a set of test sequences, each of which is allocated in an individual computing resource and executed in parallel. In particular, we propose eight parallel test prioritization techniques by adapting the existing four sequential test prioritization techniques, by including and excluding testing time in prioritization. To investigate the performance of the eight parallel test prioritization techniques, we conducted an extensive study on 54 open-source projects and a case study on 16 commercial projects from Baidu , a famous search service provider with 600M monthly active users. According to the two studies, parallel test prioritization does improve the efficiency of regression testing, and cost-aware additional parallel test prioritization technique significantly outperforms the other techniques, indicating that this technique is a good choice for practical parallel testing. Besides, we also investigated the influence of two external factors, the number of computing resources and time allowed for parallel testing, and find that more computing resources indeed improve the performance of parallel test prioritization. In addition, we investigated the influence of two more factors, test granularity and coverage criterion, and find that parallel test prioritization can still accelerate regression testing in parallel scenario. Moreover, we investigated the benefit of parallel test prioritization on the regression testing process of continuous integration, considering both the cumulative acceleration performance and the overhead of prioritization techniques, and the results demonstrate the superiority of parallel test prioritization.

A review on Continuous Integration, Delivery and Deployment using Jenkins

Continuous Integration (CI) is the technique of integrating small changes made to the code more often rather than waiting till the end of the development cycle for integration. The software practice wherein the software deployment can be done anytime to the market is called Continuous Delivery (CD). With continuous integration and continuous delivery, the problem of taking time to find and resolve the bug can be reduced to a large extent. As the time to find the bugs and fix them gets reduced, many releases adhering to the given timeline can be made by an organization. Various software tools have been developed for the continuous integration process which includes Jenkins, Bitbucket, TeamCity. In this paper, a review on the standard practices, approaches, challenges faced while using the continuous integration/delivery in the software development, methods of solving them, and using Jenkins for the implantation of continuous integration/delivery is done.

Enhancing the efficiency of continuous integration environment in DevOps

Faster release of features to the production environment is the need of the hour of every IT organizations. This faster and continuous software delivery is made possible through DevOps. DevOps is a set of practices that bridges the gap between development team and operations team. The different aspects of DevOps came from agile methodology. Continuous integration is the paramount of DevOps life cycle. In a continuous integration development practice, the development code and the applications code are continuously integrated several times a day. Developers follow the practice of committing changes frequently into the version control system such as git. A change in the version control system triggers the continuous integration system such as Jenkins. This exploratory study presents the ways that support the developers during the build break in continuous integration environment and thereby improve the efficiency of continuous integration process. Our findings contribute that the selected list of plugins in the Jenkins support the developers during the build break, thus developers can come up with faster recovery of build failures which in turn increase the efficiency of continuous integration environment.

Emergence and development of Uyghur medicine from the perspective of Chinese traditional medicine

The origin of medicine, to some extent, can be seen as the evolution of primitive medical knowledge and experience, and it is a process of continuous integration as well as inheritance of the good and elimination of the bad. There are four important factors, including labor (the external factor), survival instinct (the internal factor), representative doctors (the dominant factor), and philosophy (the critical factor), and only by the inspiration of philosophy can we establish and improve the theoretical system of medicine that will comprise the accumulated primitive medical experience, and instinctive medical practice. Here, we proposed that Uyghur Medicine is considered neither indigenous nor introduced. It is rooted in Chinese traditional cultures, and after integrating ancient Chinese philosophy with primitive medical experience and practice in Western China, and subsequently being inspired and enlightened by traditional Chinese medicine (TCM, Han Medicine), it gradually evolves and matures over time. Consequently, TCM (Han Medicine) has extensively contributed to the emergence and development of Uyghur Medicine. Specifically, the medical knowledge and practice of TCM (Han Medicine) introduced into Western China are the basis, whereas those of Persian Medicine and Ancient Indian Medicine introduced through the Silk Road are the important sources of enrichment.

DevOps - A collaboration Of Developing & Deploying Software

DevOps is the fuse of tasks performed by a company’s application development and systems operations teams. The team DevOps is being used in distinct ways. DevOps is a major innovation in Information System development. In its most broad definition, DevOps is an operational ideology that stimulate better communication between development and operations as more elements of operations become programmable. The DevOps approach seeks to meld application development and deployment into a more streamlined process that aligns development quality assurance (QA) and operations team efforts. This approach also shifts some of the operation team’s responsibilities back to the development team in order to facilitate continuous development, continuous integration, continuous delivery and continuous monitoring processes. The necessity for tearing down the silos between development and operations has been expedited by the need to release code faster and more often in order to help the organization respond in a more agile manner to changing business requirements. Other drivers for breaking down the silos include the increasing use of cloud computing and advances in software defined infrastructures, microservices, containers and automation.

HLR Framework Development for Continuous Integration

Home Location Register (HLR) and Home Subscriber Server (HSS) are the master databases which manages Second Generation (2G), Third Generation (3G) and Fourth Generation (4G) networks. The Continuous Integration (CI) process requires engineers to integrate application features into a single repository frequently. In this paper, an automated HLR framework development for testing the 2G, 3G, 4G or LTE and IMS application features is presented. The HLR framework helps to install and configure the HLR test machines. This framework helps to automate the configuration management on the test machines using Jenkins server to run Sanity and Regression. The HLR Framework Development for Continuous Integration is going to reduce the manual efforts by automating the task of Continuous Integration process such as installation, configuration, execution and generation of a report.

TECHNOLOGIE OF TEAM COLLABORATION OF DEVELOPMENT OF DECISION SUPPORT SYSTEM FOR MANAGER OF PHARMACY

There are some problems that arise during development of the decision support system that includes team collaboration, management and progress of the work, continuous integration and continuous delivery processes, development of the project by several people and working on single source code. This problem appears in every cross-functional team and interfere of proper work, so approaches for solving them must to know every software engineer. At this topic describes how this problem can be solved using example of team development of the project called “Decision support system for manger of pharmacy network”. The purpose of this paper is to analyze existing practices for the collective development of decision support systems and to identify key best practices that will allow the most efficient creation of decision support system at any scale with team collaboration. By now is very important question about choosing technologies for development of decision support system. So there is a high necessity in developing such system to be used in web browser and mobile phones with various mobile operation system like Android or IOS besides even for laptop OS like Windows or Mac OS. As follows development is conducted using different programming languages and engagement of the specialists with different skills. As the result this topic shows key problems of the cross-functional team development and defines main ways of their prevention and also increase team productivity. In this article highlights the key issues encountered in the development of the decision support systems by cross-functional teams, and presents tools and approaches for improving and reducing the cost of the development and maintenance using example of the manager of the pharmacy network. An approach is described of the development of decision support systems with the team of developers that have different knowledge of technologies and programming languages and different skills of working with automated environments. These approaches and tools can significantly improve the quality of the product that is developing, improve communication inside team, adjust tasks and develop functionality within the scheduled time frame

Непрерывная интеграция функционального наполнения распределенных пакетов прикладных программ

We propose a new approach to solving important practical problems of complex debugging, joint testing, and analysis of the execution time of software module versions in a heterogeneous distributed computing environment that integrating Grid and cloud computing. These problems arise in the process of supporting the continuous integration of modules of distributed applied software packages. The study focuses on the packages that are used to conduct large-scale computational experiments. The scientific novelty of the proposed approach is to combine the methodology for creating the packages with modern software development practices based on its continuous integration using knowledge about the specifics of the problems being solved. Our contribution is multifold. We expanded the capabilities of continuous integration tools by developing new additional tools for the markup and transformation of data from poorly structured sources and predicting modules execution time. In addition, we developed a technological scheme of the joint applying our developed tools and external systems for continuous integration. Therefore, we provide a more large range of capabilities of continuous integration in relation to the processes of creating and using the packages in comparison with the well-known tools. The fundamental basis of their functioning is a new conceptual model of the packages. This model supports the specification, planning, and execution of software continuous integration processes taking into account the specific subject data and problems being solved. Applying the developed tools in practice leads to a decrease in the number of errors and failures of applied software in the development and use of the packages. In turn, such decrease significantly reduces the time for large-scale computational experiments and increases the efficiency of using resources of the environment. The results of practical experiments on the use of system prototype for continuous integration of applied software show their high efficiency.

PhenoMeNal: processing and analysis of metabolomics data in the cloud.

BackgroundMetabolomics is the comprehensive study of a multitude of small molecules to gain insight into an organism's metabolism. The research field is dynamic and expanding with applications across biomedical, biotechnological, and many other applied biological domains. Its computationally intensive nature has driven requirements for open data formats, data repositories, and data analysis tools. However, the rapid progress has resulted in a mosaic of independent, and sometimes incompatible, analysis methods that are difficult to connect into a useful and complete data analysis solution.FindingsPhenoMeNal (Phenome and Metabolome aNalysis) is an advanced and complete solution to set up Infrastructure-as-a-Service (IaaS) that brings workflow-oriented, interoperable metabolomics data analysis platforms into the cloud. PhenoMeNal seamlessly integrates a wide array of existing open-source tools that are tested and packaged as Docker containers through the project's continuous integration process and deployed based on a kubernetes orchestration framework. It also provides a number of standardized, automated, and published analysis workflows in the user interfaces Galaxy, Jupyter, Luigi, and Pachyderm.ConclusionsPhenoMeNal constitutes a keystone solution in cloud e-infrastructures available for metabolomics. PhenoMeNal is a unique and complete solution for setting up cloud e-infrastructures through easy-to-use web interfaces that can be scaled to any custom public and private cloud environment. By harmonizing and automating software installation and configuration and through ready-to-use scientific workflow user interfaces, PhenoMeNal has succeeded in providing scientists with workflow-driven, reproducible, and shareable metabolomics data analysis platforms that are interfaced through standard data formats, representative datasets, versioned, and have been tested for reproducibility and interoperability. The elastic implementation of PhenoMeNal further allows easy adaptation of the infrastructure to other application areas and ‘omics research domains.