Relevant bibliographies by topics / Continous integration

Journal articles
Dissertations / Theses
Books
Book chapters
Conference papers
Reports

Academic literature on the topic 'Continous integration'

Author: Grafiati

Published: 4 June 2021

Last updated: 14 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Continous integration.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Continous integration"

Albaihaqi, Muhammad Fauzan, Anisa Nurul Wilda, and Bambang Sugiantoro. "Deploying an Application to Cloud Platform Using Continous Integration and Continous Delivery." Proceeding International Conference on Science and Engineering 3 (April 30, 2020): 279–82. http://dx.doi.org/10.14421/icse.v3.513.

Full text

Abstract:

Cloud Computing is the best way for bussiness owner deploy an application to reduce cost issue because it is implement pay as you go concept. Generally, an application on production level or deployed into cloud instance should not have any error or bug. It should be tested and maintain properly. The problem when an application have intensive development that takes more effort to test the application and deploy. So, need a strategy to deploy an application into cloud instance to make the proccess more efficient. Nowadays, Version Control System (VCS) platform provide Continous Integration and Continous Delivery (CI/CD) feature. Users can utilize that platform to perform automated test and deployment easily. This reasearch purposed to examine how to use CI/CD feature and evaluate it in case of deploying web application to Cloud Platform. Researcher use Gitlab wich is provide CI/CD feature for free and deploy the app to Amazon Web Service. The researcher also utilize docker container to accommodate all processes. The result are Continous Integration can improove application quality because most lines of codes are tested using unit or feature test scenario. Using CI/CD feature improove security issue of deployment. Deployment proccess run automatically without human intervention so it will reduce human error factors. This feature also ensure high availability of an application. Deployment proccess will take zero downtime. The application can quickly update without any downtime and configuration. Last, docker container take an important role for deployment of application into cloud instance.

APA, Harvard, Vancouver, ISO, and other styles

Lim, Sangwoo, Kilyong Kim, and Seojeong Lee. "Case study of customizing a Continous Integration Tool for Maritime Software." Journal of Digital Contents Society 16, no. 6 (December 31, 2015): 893–900. http://dx.doi.org/10.9728/dcs.2015.16.6.893.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Yang, Li, Xin Yu Gen, and Xie Dong Cao. "Research on Virtual Data Access to Oil-Gas Information Integration Platform Based on MTCA-DDA." Applied Mechanics and Materials 278-280 (January 2013): 1853–56. http://dx.doi.org/10.4028/www.scientific.net/amm.278-280.1853.

Full text

Abstract:

To solve virtual access to distributed oil-gas field data, a new distributed data access model is used to virtual data access center integration platform in oil-gas field.By introducing multi-task cooperative agent (MTCA-DDA), collaboration of MTCA-DDA can efficiently solve distributed data access collaboration problem. Failure server scheme guarantees distributed data continous access. Periodic exchange and data cache mechanism greatly improve data distributed store and access speed.Virtual data access center integration platform shows MTCA-DDA model can improve data access efficiency and enhance the reliability of data access.MTCA-DDA model with periodic exchange and data cache can effectively solve storage and reliability of massive distributed data access and provides a new way for similar distributed application.

APA, Harvard, Vancouver, ISO, and other styles

Frühbeck, Gema, Javier Gómez-Ambrosi, Francisco José Muruzábal, and María Angela Burrell. "The adipocyte: a model for integration of endocrine and metabolic signaling in energy metabolism regulation." American Journal of Physiology-Endocrinology and Metabolism 280, no. 6 (June 1, 2001): E827—E847. http://dx.doi.org/10.1152/ajpendo.2001.280.6.e827.

Full text

Abstract:

The ability to ensure continous availability of energy despite highly variable supplies in the environment is a major determinant of the survival of all species. In higher organisms, including mammals, the capacity to efficiently store excess energy as triglycerides in adipocytes, from which stored energy could be rapidly released for use at other sites, was developed. To orchestrate the processes of energy storage and release, highly integrated systems operating on several physiological levels have evolved. The adipocyte is no longer considered a passive bystander, because fat cells actively secrete many members of the cytokine family, such as leptin, tumor necrosis factor-α, and interleukin-6, among other cytokine signals, which influence peripheral fuel storage, mobilization, and combustion, as well as energy homeostasis. The existence of a network of adipose tissue signaling pathways, arranged in a hierarchical fashion, constitutes a metabolic repertoire that enables the organism to adapt to a wide range of different metabolic challenges, such as starvation, stress, infection, and short periods of gross energy excess.

APA, Harvard, Vancouver, ISO, and other styles

Widiyono, Dwi Cahaya, and Artiningsih Artiningsih. "Kinerja Pelayanan Petikemas Di Pelabuhan: Komparasi Pelabuhan Tanjung Perak Surabaya Dan Pelabuhan Di Asia." Jurnal Planologi 17, no. 2 (October 30, 2020): 168. http://dx.doi.org/10.30659/jpsa.v17i2.7915.

Full text

Abstract:

The focus of this paper is to evaluate the container services at Port of Tanjung Perak and compare it with other ports in Asia. A list of twenty (20) attributes is used as an assessment indicator with a five-point Likert scale, then analyzed using Customer Satisfaction Index (CSI) and Importance-Performance Analysis (IPA) matrixes to measure service quality from users perspective. The results of the analysis addressed the CSI value of this study was 69.21% which refers to the service of the Port of Tanjung Perak Surabaya included in the category of satisfied. The IPA matrixes of the Port of Tanjung Perak confirm that three attributes were the main priorities for improved performance, namely related to congestion at the port, efficiency on-dock operation of containers at port and integration into intermodal transport system. In the ‘Assurance’ dimension, Port of Tanjung Perak is in the fourth position, above the Shanghai Port in China. In the ‘Tangible’, ‘Relability’, ‘Emphaty’ and ‘Responsiveness’ dimensions, Port of Tanjung Perak still needs to make continous improvements.

APA, Harvard, Vancouver, ISO, and other styles

Nur Aisyah and Suratno. "The Cultivation Of The Religious Values As Character Forming Students." EDUTEC : Journal of Education And Technology 3, no. 1 (September 30, 2019): 12–19. http://dx.doi.org/10.29062/edu.v3i1.2.

Full text

Abstract:

Character education in schools aimed at improving the quality of the implementation and results of school education towards achieving the formation of character and noble character of learners as a whole, integrated, balanced and appropriate competency standards. Character education is applied in the implementation of learning by using a contextual approach for students to connect or associate materials studied to real life. This study aimed to describe the implementation of character education, the curriculum used, and the results achieved in shaping the character of students. The research was carried out by a naturalistic qualitative approach, and its subjects were the Elementary School’s principal, vice principal, teachers/homeroom teachers and students and the students’ parents. The data were collected through observation and interviewing and document analysis. The validity of data was used the source, method, and theory triangulation, the prolongation of observation, continous observation, sufficient reference, checking partners through discussion, and member check. The data analysis included the data reduction, data display and conclusion. The result of the research are: (1) character education planning is done by integrating the religious values are matched with the standards of competence and basic competence, suitability with the material, and are translated into a learning device. Character values developed or implemented through habituation and exemplary school culture, (2) the implementation of character education is done in learning is divided into three sections, the first integrated into the subjects, both in local content, and the third through the self-development of habituation, exemplary, and extracurricular. Character education in extracurricular activities carried out by entering the value of the main characters in each activity option. Barriers to implementation of the characteristics of students, families, and communities. Facilities and support facilities play an important role in the integration of the value of the character, (3) character education evaluation process carried out during the learning process and when students interact outside the classroom which in turn reported to students parents.

APA, Harvard, Vancouver, ISO, and other styles

S.K, Arpita, Amrathesh Amrathesh, and Dr Govinda Raju M. "A review on Continuous Integration, Delivery and Deployment using Jenkins." Journal of University of Shanghai for Science and Technology 23, no. 06 (June 18, 2021): 919–22. http://dx.doi.org/10.51201/jusst/21/05376.

Full text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

Dyvak, Y. A. "Analytical review of approaches to integration of software systems." PROBLEMS IN PROGRAMMING, no. 1 (March 2021): 036–48. http://dx.doi.org/10.15407/pp2021.01.036.

Full text

Abstract:

Conducted comparison analysis of existing approaches to integrations of software systems, with the purpose of continuous design of new alternative approaches for resolving integration tasks and web-service composition tasks. Conducted integration of payment system with online store with one of the mentioned approaches for a deeper understanding of problems that caused during the integrations of a software system. Were considered challenges that actual for integration developers during the integrations and methods for resolving raised issues. Defined the key moments of integrations of software systems and interactions between them that we should pay attention to. The subject of research needs a new point s of view to the issue and new alternative approaches that might bring more flexibility, increase performance, and they will find the right place for applying in the field of integrations of software systems and the composition of web-services.

APA, Harvard, Vancouver, ISO, and other styles

DHANY, AKBAR. "Implementation of Docker and Continuous Integration / Continuous Delivery for Management Information System Development." IJEEIT International Journal of Electrical Engineering and Information Technology 3, no. 2 (January 28, 2021): 20–24. http://dx.doi.org/10.29138/ijeeit.v3i2.1208.

Full text

Abstract:

A series of Development and Operations (DevOps) in the process of making the Narotama University Management Information System have not been implemented properly by previous developers. There are improvements or additional features of the Management Information System that are in accordance with the functionality and the increasing development needs that will be used by the academic community, so that the Management Information System developer has a little difficulty in integrating documents and distributing applications with different packages to the Production Server. In this study, a new system design is proposed by applying the practice of Continuous Integration / Continuous Delivery as a document integration process and can simplify the application distribution process, as well as implementing the Docker Container Platform as an application container with different packages that can be run on production server together. The results of implementing the practice of Continuous Integration / Continuous Delivery and the implementation of the Docker Container Platform are able to help integrate documents between developers and be able to release fixes and add features packaged in different containers automatically and periodically without long delays. which only takes an average of 17.9 seconds in the process of sending the application to the Production Server.

APA, Harvard, Vancouver, ISO, and other styles

Gabriel, Richard, Anna Paruzynski, Ralph Eckenberg, Cynthia C. Bartholomae, Ali Nowrouzi, Wei Wang, Kerstin Schwarzwaelder, et al. "Comprehensive and Unbiased Integration Site Analysis in Clinical Gene Therapy." Blood 112, no. 11 (November 16, 2008): 2351. http://dx.doi.org/10.1182/blood.v112.11.2351.2351.

Full text

Abstract:

Abstract Retroviral vectors are commonly used gene delivery tools in clinical gene therapy providing stable integration and continuous gene expression of the transgene in the treated host cell. However, integration of the reverse transcribed vector DNA into the host genome is, by itself, a mutagenic eventthat may directly contribute to severe adverse events. The latter has dramatically been obbserved in individual cases in several, otherwise successful, gene therapy trials. Thus, a comprehensive analysis of the existing integration site pool in a transduced sample is indispensable to identify potential in vivo selection of affected cell clones and uncontrolled vector-induced cell proliferation. To date, there are several methods available to study the integration site distribution of retroviral vectors or other integrating elements as transposons. Each of these techniques makes use of restriction enzymes to digest the genomic DNA. To reveal particular vector integrations, a recognition motif of the used restriction enzyme has to be located in an appropriate distance to the integration locus in the host genome. Therefore, the genomic distribution of the recognition sequences directly impact the outcome of restriction enzyme dependent integration site analysis. We here report a validated genomic accessibility model which precisely determines the fraction of the human genome that can be analyzed with one reaction set up (i.e. restriction enzyme used). For our modeling, we used the clinically relevant linear amplification mediated PCR (LAM-PCR) as integration site analysis method of choice and the commonly used frequently cutting restriction enzymes (‘four-cutters’). We show that the most frequent four cutter motif (AATT) gives access to 54.5% of all possible integrations in the human genome, whereas the rarest distributed motif (CGCG) only identifies 2.9%. This restriction bias can be minimized by analyzing the same sample with different enzymes. A combination of the 5 most potent four cutter restriction enzymes gives access to 88.7% of the analyzable genome. Furthermore, we established an unbiased, non-restrictive integration site analysis technique based on (nr) LAM-PCR. Direct ligation of a single-stranded DNA sequence to the linear PCR product evades the need for restriction enzymes to recover integration sites. While standard LAM-PCR was done repeatedly with 3 different enzymes to detect integration sites present in lentivirally transduced single cell clones, nrLAM-PCR detected all integrations in these clones in one single reaction setup. This newly developed method comprehensively recovers genomic locations of integrating elements regardless of a restriction enzyme introduced bias. Our data show that the recovery rate of integration sites present in a transduced sample strongly depends on the restriction enzyme(s) used. However, we demonstrate that the genomic accessibility of viral integration sites indeed can be determined and minimized a priori, and that a non restrictive LAM-PCR approach circumvents the existing limitations. Analysis of the clonal inventory by these methods will allow determining the pharmacodynamics of insertional vectors with unprecedented precision, facilitating development and clinical testing of insertional vector systems.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Dissertations / Theses on the topic "Continous integration"

Inge, Arvid, and Leo Jordansson. "Plattform för kontinuerlig integrering : En applikation för bygg- och testprocesser." Thesis, Karlstads universitet, Institutionen för matematik och datavetenskap (from 2013), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-78116.

Full text

Abstract:

För att möta kraven på ständiga förändringar har många företag börjat jobba enligt den iterativa, agila modellen Scrum. Denna modell innefattar bl.a. att praktisera kontinuerlig integrering (CI) där utvecklare regelbundet sammanfogar och testar kod. Målet med projektet är att förenkla denna process hos Epiroc i Örebro, så att berörda parter utnyttjar en gemensam CI-portal. Resultatet av projektet är en fungerande webbapplikation som ger Epirocs utvecklare möjlighet att praktisera CI genom att bygga och testa sin kod samt granska resultat från detta i ett modernt och användarvänligt gränssnitt. Vår uppfattning är att drifttsättningen av produkten kommer bidra till återkoppling från användare angående förbättringar. Övergången till kontinuerlig integrering som arbetsprocess hos Epiroc är inte fulländad, många aspekter av applikationens användningsområde är föränderliga. Stor vikt har därför lagts på applikationens modularitet under utvecklingsprocessen vilket ger utrymme för framtida utveckling av applikationen efter Epirocs behov. I dagsläget kan verktyget användas för att starta och övervaka bygg- och testjobb på en Jenkinsserver, men kan i framtiden få en större roll i Epirocs utvecklingskedja, exempelvis som databashanterare för testkodbasen.
Global technological advances are rapid, with this constant change, the demands on companies ability to adapt their digital products constantly increase when rapid changes are to be welcomed and the pace of production increases. To meet the requirements, many companies have started working according to the iterative, agile model Scrum. Part of this model includes practicing continuous integration (CI) where developers continuously merge and test code. The aim of the project is to simplify this process at Epiroc in Örebro, Sweden, so that interested parties are collaborating through a single CI portal. The end result of the project is a working web application that gives developers the opportunity to practice CI by building and testing their code, and review results from this in a modern and user-friendly interface. Commissioning of the application will contribute to input from the users on improvements. The application is modular, which leaves plenty of room for future development.

APA, Harvard, Vancouver, ISO, and other styles

Lundgren, Anna. "Pragmatisk mjukvarutestning : Hur kan agila metoder implementeras i ett pågående utvecklingsprojekt?" Thesis, Umeå universitet, Institutionen för informatik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-49978.

Full text

Abstract:

There are several ways of conducting software testing where some may include users and others may include personnel whose work task is to execute test on systems. Although most developers and project managers understand the point of testing the system, it is not always being done and the most common reason is that there is no time for it. However, this is a false assumption as it may instead cause some bugs in the system that would not have been there in the first place if tests had been there to prevent bugs in the code. My purpose for this thesis was to find suggestions for changes in the development process in an ongoing project used by Acino and Svenska Försäkringsfabriken in order to increase the quality of the system used. In this thesis, I have approached the purpose by pursuing a case study of the two companies through observation and interviews. By doing this I acquired the relevant information to make suggestions for change. In my case study, I have analysed the work process, which includes the types of testing and development conducted on the system. Through this I have found suggestions for changes that can generate better quality of both the system and work process. The changes that I've suggested are directed against both the code that the system consists of and the work processes used by the two companies. While the suggestions I have found is not entirely new for the companies it is something that’s not included in either the code or process, but my hope is that I have created an awareness which could ultimately generate a positive change.

APA, Harvard, Vancouver, ISO, and other styles

Lindqvist, Didrik. "DETECTION of INFRASTRUCTURE ANOMALIES in BUILD LOGS USING MACHINE LEARNINGText classification on Continous Integration log files." Thesis, Umeå universitet, Institutionen för datavetenskap, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-164730.

Full text

Abstract:

Continuous integration is a practice where software developers integrate their code to a bigger codebase multiple times per day. Before the integration, the code is built and tested by e.g open source build tools such as Jenkins, and the information produced during this process is stored in a log file. Sometimes these builds fail, and the cause can be either user or infrastructure related. A user related error may be that the code cannot compile due to syntax error and an infrastructure error could be a DNS problem. This thesis evaluated how well machine learning can be used to label the cause on failed build logs as either user or infrastructure. This thesis compared the performance of three machine learning algorithms: support-vector machine, random forest, and gradient boosting classifier. Two different datasets are used in this study. A balanced dataset used for training and validation and another dataset used for testing. The preprocessing step, including feature selection, is done using term frequency-inverse document frequency, which converts the text from the build log to a machine learning friendly format. The study also evaluated three different sizes of n-grams for each algorithm and dataset. The performance for the three machine learning algorithms is evaluated by comparing the precision, recall, and F1-score for each model. The three machine learning algorithms and the methodology around preprocessing and evaluation are explained in this study. The results show that machine learning can be used as a tool to help the CI-owners, but may not be used to fully replace the classification done manually today. The machine learning algorithm that performed the best was gradient boosting classifier with an bag of 1 and 2-grams, with a precision, recall and F1-score of 0.87, 0.73 and 0.79.i

APA, Harvard, Vancouver, ISO, and other styles

Ondrušek, Libor. "Správa přepínání procesů v aplikaci Jenkins." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2012. http://www.nusl.cz/ntk/nusl-412866.

Full text

Abstract:

The project deals with design and solution of plug-in for a Jenkins server, which allows management of jobs running on the nodes in the cluster of continuous integration system servers. This plug-in should allow pause the long time job, done process with higher priority and restore original job in state where it was interrupted.

APA, Harvard, Vancouver, ISO, and other styles

García, Díaz Vicente. "MDCI: Model-Driven Continuous Integration." Doctoral thesis, Universidad de Oviedo, 2011. http://hdl.handle.net/10803/80298.

Full text

Abstract:

El propósito de esta Tesis es llevar a cabo un proceso en el que se aplique la práctica de la integración continua en un desarrollo de software dirigido por modelos de forma eficiente, mediante el cual los desarrollos de software puedan beneficiarse conjuntamente de las mejoras y ventajas que proporcionan la aproximación de desarrollo de la ingeniería dirigida por modelos y la práctica de la integración continua. La aproximación de la ingeniería dirigida por modelos es el último salto natural de la ingeniería del software en cuanto a la búsqueda de métodos de desarrollo que elevan el nivel de abstracción hasta el punto en el que los expertos de un dominio de conocimiento, ajenos al mundo informático, son capaces de guiar y cambiar la lógica de los sistemas informáticos. La práctica de la integración continua es una recomendación de las principales metodologías de desarrollo, que tiene como objetivo la realización de integraciones automáticas del software en etapas tempranas del desarrollo, ofreciendo ventajas como la reducción del riesgo intrínseco que, dado su carácter temporal y único, tienen todos los proyectos. Con la unión de la ingeniería dirigida por modelos y de la práctica de la integración continua se busca ofrecer, a los equipos de desarrollo que trabajan utilizando algún tipo de iniciativa de la ingeniería dirigida por modelos, la posibilidad de integrar de forma continua y distribuida sus desarrollos. Al mismo tiempo, los clientes, verdaderos expertos del dominio de conocimiento en su ámbito de negocio, se benefician del aumento del nivel de abstracción de las técnicas de desarrollo para que ellos mismos, y de forma transparente, sean capaces de modificar su propio sistema informático sin la ayuda de personal técnico ajeno a su negocio, ahorrando así tiempo y costes. Para cumplir con el objetivo de esta Tesis doctoral se construye un prototipo que salva los impedimentos actuales que no permiten la unión entre estos dos nuevos activos de la ingeniería del software. Los principales problemas encontrados están relacionados con la selección de una iniciativa de desarrollo apropiada, los sistemas de control de versiones especialmente adaptados para trabajar con modelos, la generación incremental de artefactos a partir de modelos y la adaptación a las herramientas actuales de integración continua de forma optimizada. La separación del trabajo realizado en diferentes bloques permite ofrecer soluciones de forma tanto aislada como en conjunto, dando lugar a un trabajo iterativo e incremental de comienzo a fin. Para analizar las ventajas que ofrece la propuesta de este trabajo frente a otras posibilidades de desarrollo, se realiza una evaluación mediante la creación de diferentes casos de prueba en los que la medición de diferentes parámetros ofrecen una estimación numérica de las ventajas reales obtenidas. El análisis descriptivo, el contraste de hipótesis y las técnicas de regresión permiten una mejor interpretación de los resultados. Finalmente, se define el proceso, objetivo último de este trabajo, mediante la respuesta a diferentes preguntas planteadas, que facilitan su comprensión y entendimiento.
The purpose of this Thesis is to create a process in which the continuous integration practice can be applied to a model-driven software development in an e ective way, through which software developments can bene t jointly and simultaneously from the improvements and advantages provided by the model-driven engineering development approach and the continuous integration practice. The model-driven engineering approach is the last natural step of software engineering in the search for development approaches that raise the level of abstraction to the point that experts in a domain of knowledge, outside the computer world, are able to guide and change the logic of computer systems. The continuous integration practice is a recommendation of the most widely accepted development methodologies that aims to carry out automatic software integrations in early stages of development, o ering bene ts such as reducing the inherent risk that, given its unique nature, every project has. By merging the model-driven engineering and the continuous integration practice, the aim is to provide to development teams that work using some kind of model-driven engineering initiative, the possibility to integrate their developments in a continuous and distributed way. At the same time, customers, the real experts in the domain of knowledge in their eld of business, can bene t from the increased level of abstraction in developing techniques. Thus, they, in a transparent manner, are able to modify their own computer system without the help of external technical sta , so saving time and costs. To meet the objective of this Thesis, a prototype which saves all the current constraints that do not allow the union between these two new tools of software engineering is build. The main problems found were related to the selection of an appropriate development initiative, the version control systems specially adapted to working with models, the incremental generation of artifacts from models, and the optimized adaptation to existing continuous integration tools. The separation of work in di erent blocks can provide solutions, both in isolation or in conjunction, resulting in an iterative and incremental work from beginning to end. To analyze the bene ts of the proposal in this work compared to other development possibilities, an evaluation is performed by creating di erent test cases in which the measurement of di erent parameters can give a numerical estimate of the real bene ts obtained. The descriptive analysis, the hypothesis testing, and regression techniques allow a better interpretation of results. Finally, the process, the main objective of this work, is de ned by answering various questions posed to facilitate its comprehension and understanding.

APA, Harvard, Vancouver, ISO, and other styles

Saari, M. (Marko). "Implementing new continuous integration tool." Master's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201706022481.

Full text

Abstract:

This thesis studied the implementation of new Continuous Integration tool by focusing on existing problems and possible arising problems when implementing the new Continuous Integration tool. The thesis supported a project run by one international software development company with the main goal of replacing the current Continuous Integration tool from CruiseControl.NET with some more suitable alternative tool. The purpose of this thesis was to research about the topic and the existing tool to support the project in the implementation of the new Continuous Integration tool. On the literature review, first the current state of Continuous Integration tool in the company was discussed. Then the literature review focused on the research about Continuous Integration, Continuous Delivery and Continuous Deployment. Alternative Continuous Integration tools were also studied as the company had two Continuous Integration tools to choose from: Bamboo and Jenkins. The problems of the current Continuous Integration tool in the company were studied by conducting a survey. This survey was based on existing studies on the problems of Continuous Integration tools. Pilot testing and reviews also had impact on the final survey. 37 people out of the target population (89) participated in the survey. Survey results showed that those 37 people had different background but most of them had a long history in the company. Some participants did not answer all of the questions. Two lists of issues were created by analyzing the survey results: Issues of current Continuous Integration tool and Issues when implementing new Continuous Integration tool. Two biggest issues from the list of issues of the current Continuous Integration tool were Lack of hardware and Build duration. Solution for these is that better hardware solves the Lack of hardware and improves the build duration with better hardware capacity and parallelization. Two biggest issues from the list of issues when implementing new Continuous Integration tool were Resistance to change and Lack of knowledge. The findings from past research suggest that implementing new Continuous Integration tool requires change of work of everyone to actually work. The solution for Lack of knowledge was that training is required for employees to actually know the way of using the new Continuous Integration tool. Suggested solutions were based on existing research and on the survey results. The study provided two lists of Continuous Integration tool problems and proposals for possible solutions for those. The results can be used for selecting Continuous Integration tool as the study compared the results between Bamboo and Jenkins. Comprehensive study on the problems of Continuous Integration tool and the comparison of Continuous Integration tools provided reasoned support for the project of the company.

APA, Harvard, Vancouver, ISO, and other styles

Kerkelä, J. (Joni). "Continuous Integration server performance monitoring." Master's thesis, University of Oulu, 2018. http://urn.fi/URN:NBN:fi:oulu-201805091678.

Full text

Abstract:

Continuous Integration (CI) is standard practice in Agile software development for source code management, including handling changes between development branches and master branch, and providing feedback for stakeholders. In the Continuous Integration the desirable practice is for development branches the be merged in to master branch daily. Before development branches is to be merged to master branch, the automated test tests builds are run on them and feedback of the tests is provided to developer and possible other stakeholders. If the tests are run without errors, the development branch is to be merged to master branch. The problems may arise, when the automated test build durations have variance. This leads developers to experience volatile service level causing irregularity to development process. The cause for the build duration variance can be the variance in the available system resources in the CI server. In some cases, the resource variation can cause false failures on the test build results as for example when there is defined maximum test build duration time limiter or when individual build step operation produces timeouts. To be able to resolve the resource starvation on the CI server, there needs to be means for identifying the resource starvation events in relation to test build statistics. By being able to identify relation between build statistics and resource starvation events, root cause, as starving resource, can be identified. By identifying the starving resource or resources, the system resources can be updated by adding more specific resource or handling the starvation through reserving the specific resource for key processes. The objective for this research is to implement monitoring tool for monitoring the Jenkins server’s builds and system resources during the builds. The thesis was conducted in the case company’s CI project including large-scale development project as customer project. The problem with case company was volatile test build durations and very insufficient data about system resources in the starvation events. The implemented monitoring tool achieved for providing extensive system resource data with combining it with the test build statistics to provide information about system resource availability in relation to test build statistics. The results indicate that the monitoring tool can be used for identifying resource starvation events and possible root causes for the events. The limitation of the implemented monitoring tool is the dependency for the database server as Elasticsearch. Elasticsearch was chosen to be used as database to establish adaptive monitoring data presenting functionality via Kibana server. This restricts portability of the monitoring tool to Jenkins instances as the monitoring tool needs mentioned instances for full functionality.

APA, Harvard, Vancouver, ISO, and other styles

Hämäläinen, Thomas, and Hillevi Strömberg. "Vägen till kontinuerliga leveranser : En fallstudie om continuous delivery och DevOps i en offentlig organisation." Thesis, Umeå universitet, Institutionen för informatik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-120739.

Full text

Abstract:

Information system development projecs are often considered a costly and uncertain process were projects often exceed the scheduled time and budget. By continuously integrating source code and do regular builds problems can be discovered almost directly and thus minimizing the cost to fix them. In this qualitative study we have focused on which challenges a large public organization who cooperate with an external provider can face when adopting continuous integration and continuous delivery. We have interviewed six employees within the organisation and two employees from the external provider, who are all in some way connected to the software development process. The results showed that our interviewees are interested in agile software development and to be able to deliver high quality software continuously. We also found that the software development process is complex and has a lot of barriers and handovers that slows the process down. Our conclusion is that the organization needs to change their approach to software development. To achieve this the organisation needs to adopt Devops, which means erasing the barriers between development and operations.

APA, Harvard, Vancouver, ISO, and other styles

Zhao, Xuhui. "Automatic analysis for continuous integration test failures." Thesis, Högskolan i Gävle, Elektronik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:hig:diva-30187.

Full text

Abstract:

CI (Continuous Integration) is a software development practice which became more and more popular in last decade. Ericsson followed the trends and used CI several years. Because of the complexity of RBS (Radio Base Station) software few levels of CI have been implemented there. In RCS (RBS Control System) module CI there are many automatic JCAT (Java Common Auto Tester) test loops running every day and some of them failed. This thesis tries to find a way to classify these test failures automatically, so efficiency and lead time can be improved. Two methods are presented and investigated in this report, rule matching and machine learning. After analysis and comparisons rule matching approach is selected because it does not require huge effort in the initial phase and rule matched data can be used as labeled data for machine learning. This approach requires manual work to add new rules continuously but with correctly defined rules the accuracy is 100%, if the rule is general it can classify one type of issue including the ones which never happen before. One analysis system is designed and implemented, and only small update is required to the result report block of the CI flow. One matching example is showed and according to estimation this method could save many man hours every year.

APA, Harvard, Vancouver, ISO, and other styles

Nyholm, Tobias. "Effektiv Mjukvaruutveckling Med Continuous Integration Och Automatisering." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-142385.

Full text

Abstract:

Effektiv utveckling kan göra lika stor skillnad som en eller kanske två extra utvecklare till teamet. För att ligga i framkant i effektiv mjukvaruutveckling så måste man definiera hur man är effektiv och vad det innebär. Man kan med stor framgång se sig om kring hur andra företag och organisationer har uppnått högre effektivitet. I rapporten diskuteras best practice och hur R2Meton AB jobbade i början av 2013. Sedan presenteras en utvecklingsmodell som R2Meton AB har implementerat för att bli mer effektiva. Modellen innefattar bland annat automatiserat bygge, tester, analyser och distribution. En högre grad av automatisering och analyser innebär en större enhetlighet och kvalitet. Hjärtat i hela modellen är givetvis en continuous integration server som stegvis tar processen framåt. Det är även den som ger feedback till utvecklarna om något har gått fel eller om dem brutit mot de förutbestämda kvalitetskraven. Med hög kvalitet, enhetlighet och tydliga policys så blir koden lättare att underhålla och vidareutveckla samt mer pålitlig.
Effective software development may increase the productivity of the team as much as one or maybe two extra programmers. If you want to work efficiently you have to define what efficiency is and what it really means. You should study examples from other businesses and companies to see what they have done and try to understand why some of them succeeded and why some failed. The report will discuss best practices in software development and how R2Meton AB used to do their development. A model will be presented that R2Meton AB has implemented to improve their efficiency. The model describes how to automate builds, tests, analysis and deployment of the software to a testing environment. The increased automation and code analysis will provide more standardization and higher quality. Continuous integration is the heart of the model. The continuous integration server is the core that makes sure the process is moving forward. It does also give the developers feedback when the build breaks or when they fail to comply with the quality profile. With a high quality codebase, standards and clear policies you will get software that is easy to maintain, further develop and is more reliable.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Books on the topic "Continous integration"

Macharla, Pradeep. Android Continuous Integration. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2796-1.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Pouclet, Romain. Pro iOS Continuous Integration. Berkeley, CA: Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0124-4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Lenz, Moritz. Python Continuous Integration and Delivery. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-4281-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Versluis, Gerald. Xamarin Continuous Integration and Delivery. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2716-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

1966-, Ambler Scott W., ed. Recipies for continuous database integration: Evolutionary database development. Boston, Mass: Addison Wesley Professional, 2007.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

1979-, Matyas Steve, and Glover Andrew 1976-, eds. Continuous integration: Improving software quality and reducing risk. Upper Saddle River, NJ: Addison-Wesley, 2007.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Zaanen, Adriaan C. Continuity, integration, and Fourier theory. Berlin: Springer-Verlag, 1989.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Social exclusion inclusion continuum: A paradigm shift. Bangalore: Niruta Publications, 2012.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Recesso, Arthur. Integrating technology into teaching: The technology and learning continuum. Boston, MA: Houghton Mifflin, 2007.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

Recesso, Arthur. Integrating technology into teaching: The technology and learning continuum. Boston, MA: Houghton Mifflin, 2007.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

More sources

Book chapters on the topic "Continous integration"

Ritchie, Stephen D. "Continuous Integration." In Pro .NET Best Practices, 201–29. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-4024-2_10.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Zandstra, Matt. "Continuous Integration." In PHP Objects, Patterns, and Practice, 427–50. Berkeley, CA: Apress, 2010. http://dx.doi.org/10.1007/978-1-4302-2926-1_20.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Mishra, Abhishek. "Continuous Integration." In iOS Code Testing, 283–316. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2689-6_9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Holmes, Marc. "Continuous Integration." In Expert .NET Delivery Using NAnt and CruiseControl.NET, 167–97. Berkeley, CA: Apress, 2005. http://dx.doi.org/10.1007/978-1-4302-0023-9_6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Zandstra, Matt. "Continuous Integration." In PHP Objects, Patterns, and Practice, 497–523. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1996-6_21.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Acuña, Pablo. "Continuous Integration." In Deploying Rails with Docker, Kubernetes and ECS, 99–123. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2415-1_5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Zandstra, Matt. "Continuous Integration." In PHP Obejcts, Patterns, and Practice, 431–56. Berkeley, CA: Apress, 2013. http://dx.doi.org/10.1007/978-1-4302-6032-5_20.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Dalton, Jeff. "Continuous Integration." In Great Big Agile, 151–52. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4206-3_22.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Varanasi, Balaji. "Continuous Integration." In Introducing Maven, 127–35. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5410-3_9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Rosenfield Boeira, Julia Naomi. "Continuous Integration." In Lean Game Development, 67–75. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3216-3_7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Continous integration"

Ciutina, Adrian, Cristian Vulcu, and Rafaela Don. "Semi-continous beam-to-column joints for slim-floor systems in seismic zones." In 12th international conference on ‘Advances in Steel-Concrete Composite Structures’ - ASCCS 2018. Valencia: Universitat Politècnica València, 2018. http://dx.doi.org/10.4995/asccs2018.2018.7199.

Full text

Abstract:

The slim-floor building system is attractive to constructors and architects due to the integration of steel beam in the overall height of the floor, which leads to additional floor-to-floor space, used mostly in acquiring additional storeys. The concrete slab offers natural fire protection for steel beams, while the use of novel corrugated steel sheeting reduces the concrete volume, and replaces the secondary beams (for usual spans of steel structures). Currently the slim-floor solutions are applied in non-seismic regions, and there are few studies that consider continuous or semi-continuous fixing of slim-floor beams. The present study was performed with the aim to develop reliable end-plate bolted connections for slim-floor beams, capable of being applicable to buildings located in areas with seismic hazard. It is based on numerical finite element analysis, developed in two stages. In a first stage, a finite element numerical model was calibrated based on a four point bending test of a slim-floor beam. Further, a case study was analysed for the investigation of beam-to-column joints with moment resisting connections between slim-floor beams and columns. The response was investigated considering both sagging and hogging bending moment. The results are analysed in terms of moment-rotation curve characteristics and failure mechanism.

APA, Harvard, Vancouver, ISO, and other styles

Felidre, Wagner, Leonardo Furtado, Daniel A. da Costa, Bruno Cartaxo, and Gustavo Pinto. "Continuous Integration Theater." In 2019 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM). IEEE, 2019. http://dx.doi.org/10.1109/esem.2019.8870152.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Kupsch, James A., Barton P. Miller, Vamshi Basupalli, and Josef Burger. "From continuous integration to continuous assurance." In 2017 IEEE 28th Annual Software Technology Conference (STC). IEEE, 2017. http://dx.doi.org/10.1109/stc.2017.8234450.

Full text

APA, Harvard, Vancouver, ISO, and other styles

van der Storm, Tijs. "Backtracking Incremental Continuous Integration." In 2008 12th European Conference on Software Maintenance and Reengineering (CSMR). IEEE, 2008. http://dx.doi.org/10.1109/csmr.2008.4493318.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Vassallo, Carmine. "Enabling Continuous Improvement of a Continuous Integration Process." In 2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE). IEEE, 2019. http://dx.doi.org/10.1109/ase.2019.00151.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Reiterer, Stefan H., Sinan Balci, Desheng Fu, Martin Benedikt, Andreas Soppa, and Helena Szczerbicka. "Continuous Integration for Vehicle Simulations." In 2020 25th IEEE International Conference on Emerging Technologies and Factory Automation (ETFA). IEEE, 2020. http://dx.doi.org/10.1109/etfa46521.2020.9211976.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Vigario, Joana Coelho, Claudio Teixeira, and Joaquim Sousa Pinto. "Continuous integration using cloud computing." In 2015 10th Iberian Conference on Information Systems and Technologies (CISTI). IEEE, 2015. http://dx.doi.org/10.1109/cisti.2015.7170451.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Chang, Carl K. "Agile, Continuous Integration, and DevOps." In 2019 IEEE 43rd Annual Computer Software and Applications Conference (COMPSAC). IEEE, 2019. http://dx.doi.org/10.1109/compsac.2019.00038.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Knauss, Eric, Patrizio Pelliccione, Rogardt Heldal, Magnus Ågren, Sofia Hellman, and Daniel Maniette. "Continuous Integration Beyond the Team." In ESEM '16: ACM/IEEE 9th International Symposium on Empirical Software Engineering and Measurement. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2961111.2962639.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Hilton, Michael. "Understanding and improving continuous integration." In FSE'16: 24nd ACM SIGSOFT International Symposium on the Foundations of Software Engineering. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2950290.2983952.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Continous integration"

Wang, Liming. Continuous Data Integration for Land Use and Transportation Planning and Modeling. Portland State University Library, June 2014. http://dx.doi.org/10.15760/trec.37.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Papoutsakis, Eleftherios. Engineering Complex Microbial Phenotypes with Continuous Genetic Integration and Plasmid Based Multi-Gene Library. Fort Belvoir, VA: Defense Technical Information Center, January 2010. http://dx.doi.org/10.21236/ada548874.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Adams, Terry R. Continuous Integration! You Keep Using Those Words. I Do Not Think They Mean What You Think They Mean. Office of Scientific and Technical Information (OSTI), March 2019. http://dx.doi.org/10.2172/1493522.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Adams, Terry R. Continuous Integration! You Keep Saying Those Words. I Do Not Think They Mean What You Think They Mean. Office of Scientific and Technical Information (OSTI), February 2019. http://dx.doi.org/10.2172/1494455.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Lee, J. Brian, Maxim Likhachev, and Ronald C. Arkin. Selection of Behavioral Parameters: Integration of Discontinuous Switching via Case-Based Reasoning With Continuous Adaptation via Learning Momentum. Fort Belvoir, VA: Defense Technical Information Center, January 2002. http://dx.doi.org/10.21236/ada451775.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Mittelsteadt, Matthew. AI Verification: Mechanisms to Ensure AI Arms Control Compliance. Center for Security and Emerging Technology, February 2021. http://dx.doi.org/10.51593/20190020.

Full text

Abstract:

The rapid integration of artificial intelligence into military systems raises critical questions of ethics, design and safety. While many states and organizations have called for some form of “AI arms control,” few have discussed the technical details of verifying countries’ compliance with these regulations. This brief offers a starting point, defining the goals of “AI verification” and proposing several mechanisms to support arms inspections and continuous verification.

APA, Harvard, Vancouver, ISO, and other styles

Jha, M. C., R. L. McCormick, R. F. Hogsett, R. M. Rowe, and K. R. Anast. Development of an advanced continuous mild gasification process for the production of coproducts. Task 4, System integration studies: Char upgrading. Office of Scientific and Technical Information (OSTI), December 1991. http://dx.doi.org/10.2172/10145427.

Full text

APA, Harvard, Vancouver, ISO, and other styles

David S. Shafer, David McGraw, Lynn H. Karr, Greg McCurdy, Tammy L. Kluesner, Karen J. Gray, and Jeffrey Tappen. Comparison of Ambient Radon Concentrations in Air in the Northern Mojave Desert from Continuous and Integrating Instruments. Office of Scientific and Technical Information (OSTI), May 2010. http://dx.doi.org/10.2172/1009522.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Brinkerhoff, Derick W., and Anna Wetterberg. Governance and Sector Outcomes: Making the Connections. RTI Press, September 2018. http://dx.doi.org/10.3768/rtipress.2018.pb.0019.1809.

Full text

Abstract:

A critical issue in international development is how donor-funded programs can support sustainable and long-lasting changes in assisted countries. Among the factors associated with sustainability is improved governance. However, many donor-funded initiatives are focused on achieving results in specific sectors, such as health, education, and agriculture. How can how governance interventions contribute to achieving sector-specific results? This brief explores this question and discusses how international development practice has incorporated recognition of the links between governance and sector outcomes. The brief develops a stylized continuum of how governance elements relate to sector interventions and contribute to expected outcomes. We discuss factors that either impede or impel governance integration and close with some observations regarding prospects for integrated programming. The audience for the brief is the international development policy and practitioner communities, and secondarily, academics with an interest in the topic. Key take-aways include: (1) there is ample evidence of positive contributions from improved governance to sector-specific outcomes, but few guideposts exist for practical and effective governance integration; (2) barriers to integration include urgent sector priorities that overshadow governance concerns, requirements to demonstrate progress towards ambitious sector targets, and complex choices related to measurement; and (3) sustainability and self-reliance are major drivers for integration and are facilitated by the flexibility and adaptation that governance integration enables.

APA, Harvard, Vancouver, ISO, and other styles

Randle, Lawrence L. Integrating Verses Merging of the Guard and Reserve: Should the United States Continue to Maintain Duplicate Federal and State Military Reserve Forces. Fort Belvoir, VA: Defense Technical Information Center, February 2002. http://dx.doi.org/10.21236/ada400997.

Full text

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!