Automated Build

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 252 Experts worldwide ranked by ideXlab platform

Haifeng Shen - One of the best experts on this subject based on the ideXlab platform.

  • ICSOC Workshops - SORCER: A decentralised continuous integration platform for service-oriented software systems
    Lecture Notes in Computer Science, 2019
    Co-Authors: Jameel Almalki, Haifeng Shen
    Abstract:

    Continuous integration (CI) is a key practice where developers integrate frequently via a shared repository to enable Automated Build, test, and release of software systems. While enabling CI in a centralised development environment has been a common practice, no much work has been done to effectively support CI of decentralised service-oriented systems where centralised repositories are unavailable. This paper presents SORCER, a decentralised interface-based continuous integration platform that makes it easy for developers to perform integrated Build and test of service-oriented systems whose service constituents are owned and managed by different organisations to only expose their interfaces without access to their source codes.

  • ASWEC - Developing Cross-Organisational Service-Based Software Systems through Decentralised Interface-Oriented Continuous Integration
    2018 25th Australasian Software Engineering Conference (ASWEC), 2018
    Co-Authors: Jameel Almalki, Haifeng Shen
    Abstract:

    Continuous integration (CI) is a key practice where software developers integrate frequently via a shared repository to enable Automated Build, test, and release of software features. At the same time, digital economies are moving towards a service-oriented model with which software projects have become complex service-based systems orchestrated through service composition. While enabling CI in a centralised software development environment has been a common practice, little work has been done to optimally support CI in cross-organisational service-based software systems whose constituents are usually owned and managed by different organisations to only expose their interfaces. This paper presents a new decentralised interface-oriented CI model that is particularly optimised for supporting CI of cross-organisational service-based software systems. To demonstrate the viability and the effectiveness of the proposed approach, the paper further presents a proof-of-concept prototype that provides tool support, followed by an experimental evaluation that compares the prototype against an established technology stack for implementing CI using the service-oriented approach.

Ashish Gehani - One of the best experts on this subject based on the ideXlab platform.

  • FMICS - Wholly!: A Build System For The Modern Software Stack
    Formal Methods for Industrial Critical Systems, 2018
    Co-Authors: Loic Gelle, Hassen Saidi, Ashish Gehani
    Abstract:

    Wholly! is an Automated Build system for the modern software stack. It is designed for reproducible and verifiable Builds of optimized and debloated software that runs uniformly on traditional desktops, the cloud, and IoT devices. Wholly! uses Linux containers to ensure the integrity and reproducibility of the Build environment. It uses the clang compiler to generate LLVM bitcode for all produced libraries and binaries to allow for whole program analysis, specialization, and optimization. The clang compiler and install tools are all built with Wholly! as well. Wholly! has been applied to Build Alpine Linux, Docker containers, microservices, and IoT software. We show that software packages built in Wholly! are faster, smaller, and more amenable to whole program analysis.

  • Wholly!: A Build System For The Modern Software Stack
    Formal Methods for Industrial Critical Systems, 2018
    Co-Authors: Loic Gelle, Hassen Saidi, Ashish Gehani
    Abstract:

    Wholly! is an Automated Build system for the modern software stack. It is designed for reproducible and verifiable Builds of optimized and debloated software that runs uniformly on traditional desktops, the cloud, and IoT devices. Wholly! uses Linux containers to ensure the integrity and reproducibility of the Build environment. It uses the clang compiler to generate LLVM bitcode for all produced libraries and binaries to allow for whole program analysis, specialization, and optimization. The clang compiler and install tools are all built with Wholly! as well. Wholly! has been applied to Build Alpine Linux, Docker containers, microservices, and IoT software. We show that software packages built in Wholly! are faster, smaller, and more amenable to whole program analysis.

Ting Wang - One of the best experts on this subject based on the ideXlab platform.

  • ISSRE - A Study of Regression Test Selection in Continuous Integration Environments
    2018 IEEE 29th International Symposium on Software Reliability Engineering (ISSRE), 2018
    Co-Authors: Ting Wang
    Abstract:

    Continuous integration (CI) systems perform the Automated Build, test execution, and delivery of the software. CI can provide fast feedback on software changes, minimizing the time and effort required in each iteration. In the meantime, it is important to ensure that enough testing is performed prior to code submission to avoid breaking Builds. Recent approaches have been proposed to improve the cost-effectiveness of regression testing through techniques such as regression test selection (RTS). These approaches target at CI environments because traditional RTS techniques often use code instrumentation or very fine-grained dependency analysis, which may not be able to handle rapid changes. In this paper, we study in-depth the usage of RTS in CI environments for different open-source projects. We analyze 918 open-source projects using CI in GitHub to understand 1) under what conditions RTS is needed, and 2) how to balance the trade-offs between granularity levels to perform cost-effective RTS. The findings of this study can aid practitioners and researchers to develop more advanced RTS techniques for being adapted to CI environments.

Yu. L. Tikhonov - One of the best experts on this subject based on the ideXlab platform.

  • To the problem of "The Instrumental complex for ontological engineering purpose" software system design.
    arXiv: Artificial Intelligence, 2018
    Co-Authors: A. V. Palagin, N. G. Petrenko, V. Yu. Velychko, K. S. Malakhov, Yu. L. Tikhonov
    Abstract:

    The given work describes methodological principles of design instrumental complex of ontological purpose. Instrumental complex intends for the implementation of the integrated information technologies Automated Build of domain ontologies. Results focus on enhancing the effectiveness of the automatic analysis and understanding of natural-language texts, Building of knowledge description of subject areas (primarily in the area of science and technology) and for interdisciplinary research in conjunction with the solution of complex problems.

Xiaoyin Wang - One of the best experts on this subject based on the ideXlab platform.

  • ESEM - Automatic Building of Java projects in software repositories: a study on feasibility and challenges
    2017 ACM IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM), 2017
    Co-Authors: Foyzul Hassan, Mostafa, Edmund S. L. Lam, Xiaoyin Wang
    Abstract:

    Despite the advancement in software Build tools such as Maven and Gradle, human involvement is still often required in software Building. To enable large-scale advanced program analysis and data mining of software artifacts, software engineering researchers need to have a large corpus of built software, so automatic software Building becomes essential to improve research productivity. In this paper, we present a feasibility study on automatic software Building. Particularly, we first put state-of-the-art Build automation tools (Ant, Maven and Gradle) to the test by automatically executing their respective default Build commands on top 200 Java projects from GitHub. Next, we focus on the 86 projects that failed this initial Automated Build attempt, manually examining and determining correct Build sequences to Build each of these projects. We present a detailed Build failure taxonomy from these Build results and show that at least 57% Build failures can be automatically resolved.