Achieving Software Release Management and Continuous Integration using Maven, Jenkins and Artifactory

It is often required that the developers working on a single module or software project, while working from remote locations. Scenarios like that increase complexity and challenge to manage releases and to merge their daily work in a single artifact. For component based development, developers are r...

Ful tanımlama

Kaydedildi:
Detaylı Bibliyografya
Asıl Yazarlar: Shahbaz Ali Syed (Yazar), Tariq Rahim Soomro (Yazar)
Materyal Türü: Kitap
Baskı/Yayın Bilgisi: Institute of Business Management, 2018-12-01T00:00:00Z.
Konular:
Online Erişim:Connect to this object online.
Etiketler: Etiketle
Etiket eklenmemiş, İlk siz ekleyin!

MARC

LEADER 00000 am a22000003u 4500
001 doaj_c9c112ceb1b6465da0ec110a56f9a43e
042 |a dc 
100 1 0 |a Shahbaz Ali Syed  |e author 
700 1 0 |a Tariq Rahim Soomro  |e author 
245 0 0 |a Achieving Software Release Management and Continuous Integration using Maven, Jenkins and Artifactory 
260 |b Institute of Business Management,   |c 2018-12-01T00:00:00Z. 
500 |a 2520-4475 
500 |a 2521-9359 
520 |a It is often required that the developers working on a single module or software project, while working from remote locations. Scenarios like that increase complexity and challenge to manage releases and to merge their daily work in a single artifact. For component based development, developers are responsible for the merging their own work with others and to make sure the integrations went smooth with no error and problems. Sometimes it's hard to do this job because of the large size of team members, big project size or geographically separated teams.  Through Continuous integration this whole process becomes lot easier because all the validations and verifications will be done by an automated job.  This job will check for the changes in the project code and whenever a change happens it will run the build process automatically, which detects errors and problems with the code and also notifies the concerned team member who is responsible for this error. This study introduces an approach to setup a Continuous Integrations techniques in a project using open source tools like Maven, Jenkins and Artifactory. 
546 |a EN 
690 |a continuous integration 
690 |a maven 
690 |a jenkins 
690 |a artifactory 
690 |a Education 
690 |a L 
655 7 |a article  |2 local 
786 0 |n International Journal of Experiential Learning & Case Studies, Vol 3, Iss 2, Pp 236-245 (2018) 
787 0 |n http://jmsnew.iobmresearch.com/index.php/ijelcs/article/view/327 
787 0 |n https://doaj.org/toc/2520-4475 
787 0 |n https://doaj.org/toc/2521-9359 
856 4 1 |u https://doaj.org/article/c9c112ceb1b6465da0ec110a56f9a43e  |z Connect to this object online.