scholarly journals A review on Continuous Integration, Delivery and Deployment using Jenkins

2021 ◽  
Vol 23 (06) ◽  
pp. 919-922
Author(s):  
Arpita S.K ◽  
◽  
Amrathesh Amrathesh ◽  
Dr. Govinda Raju M ◽  
◽  
...  
Keyword(s):  
Software Development ◽  
Software Tools ◽  
Integration Process ◽  
Continuous Integration ◽  
Software Deployment ◽  
Development Cycle ◽  
Continuous Delivery ◽  
Standard Practices ◽  
Development Methods ◽  
The Given

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.

scholarly journals DevOPS Now and Then

2020 ◽  
Author(s):  
Raju Singh
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Continuous Improvement ◽  
Building Blocks ◽  
Extended Version ◽  
Agile Method ◽  
Development Cycle ◽  
Development Life Cycle ◽  
Continuous Delivery ◽  
Software Development Life Cycle

DevOps is an emerging practice to be followed in the Software Development life cycle. The name DevOps indicates that it’s an integration of the Development and Operation team. It is followed to integrate the various stages of the development cycle. DevOps is an extended version of the existing Agile method. DevOps aims at continuous integration, Continuous Delivery, Continuous Improvement, faster feedback and security. This paper reviews the building blocks of DevOps, challenges in adopting DevOps, Models to improve DevOps practices and Future works on DevOps

scholarly journals A Comparison on Continuous Integration and Continuous Deployment (CI/CD) on Cloud Based on Various Deployment and Testing Strategies

2021 ◽  
Vol 9 (VI) ◽  
pp. 4968-4977
Author(s):  
Avishek Singh
Keyword(s):  
Software Development ◽  
Development Process ◽  
Continuous Integration ◽  
Testing Strategies ◽  
Rapid Release ◽  
Development Lifecycle ◽  
Continuous Delivery ◽  
Software Development Lifecycle ◽  
Continuous Interaction ◽  
Continuous Feedback

Continuous Integration/Continuous Delivery/Deployment (CI/CD) emphasizes the rapid release of small, incremental changes and the use of automation throughout the development process. CI/CD technique is central to DevOps and key to its success. Consumers expect to have continuous interaction with DevOps team so that they can provide their continuous feedback. DevOps is blending of two terms: development and operations which aims to provide conjoin approach to industry’s software development and operation team job in software development lifecycle. Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that enable organizations to frequently and reliably release new features and products. Shows the comparison on deployments. With the increasing interest in literature on continuous practices, it is important to systematically review and synthesize the approaches, tools, challenges, and practices reported for adopting and implementing continuous practices.

Application of Principles From the Scrum Agile Method to a Prototype Vehicle Control Development Cycle

2014 ◽  
Author(s):  
Derek Bonderczuk ◽  
Patrick Currier ◽  
Matthew Nelson
Keyword(s):  
Control System ◽  
Software Development ◽  
Vehicle Control ◽  
Agile Method ◽  
Staffing Levels ◽  
Development Cycle ◽  
Experimental Vehicle ◽  
Agile Software ◽  
Development Methods

Traditional methods for organization of controls development tend not to facilitate the speedy completion of complex tasks such as development of an experimental vehicle control system, particularly when staffing levels are low. This paper proposes the use of Scrum Agile software development methods to streamline the control development cycle for a prototype vehicle. The EcoCAR 2 competition vehicle at Embry-Riddle Aeronautical University is used as a case study for this implementation. Specific protocols and workflows for development are outlined and examples of implementation on the EcoCAR 2 vehicle are provided. Implementation results indicate that the method allowed for an aggressive development schedule for the vehicle software without compromising reliability, maintainability, or upgradeability.

scholarly journals Factors to be Considered When to Design Software Development Plan

2012 ◽  
Vol 6-7 ◽  
pp. 3-8
Author(s):  
Yu Gao ◽  
Xiang Zhong Feng
Keyword(s):  
Software Development ◽  
Development Plan ◽  
Team Development ◽  
Difficulty Level ◽  
Design Work ◽  
Study Results ◽  
Design Software ◽  
Development Risks ◽  
Development Methods ◽  
Main Factor

It is an important prerequisite to ensure the success of software development that designing a reasonable and suitable software development plan. In the past, when discussing the design of the software development plan, people focus limited to a specific development tasks, so the lack of universality. In order to guide design work of software development plan, starting from the perspective of software engineering, the main factor to be considered has been studied when designing software development plan. These factors are: the type and size of the software, the experience of use for reference to predecessors, difficulty level to obtain users' needs, development techniques and tools, situation of development team, development risks, the software development methods that can be chosen. This study results can improve the rationality and applicability of the software development plan.

scholarly journals A Roadmap to Continuous Integration for ATLAS Software Development

2017 ◽  
Vol 898 ◽  
pp. 072009
Author(s):  
J Elmsheuser ◽  
A Krasznahorkay ◽  
E Obreshkov ◽  
A Undrus ◽  
Keyword(s):  
Software Development ◽  
Continuous Integration ◽  
Atlas Software

The Design and Implementation of Code Generation Based on J2EE in the Development of JBPM Workflow System

2012 ◽  
Vol 263-266 ◽  
pp. 1961-1968
Author(s):  
Yong Chao Song ◽  
Bu Dan Wu ◽  
Jun Liang Chen
Keyword(s):  
Software Development ◽  
Code Generation ◽  
System Development ◽  
Source Code ◽  
Design And Implementation ◽  
Workflow System ◽  
Development Cycle ◽  
The Cost ◽  
Static Form

According to the feature of the JBPM workflow system development, the target code generated is determined by analyzing the process of JBPM workflow development and the architecture of J2EE. The code generation tool generates code by parsing the static form source code and loading the code generation template. The code generation tool greatly shortens the JBPM workflow system development cycle and reduces the cost of software development which has the good practicality and scalability.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Sign in / Sign up

Export Citation Format

Share Document