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

Shahbaz Ali Syed, Tariq Rahim Soomro


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.


Continuous Integration, Maven, Jenkins, Artifactory

Full Text:



Apache Software Project. (2018). Maven – Introduction. Retrieved from

Eliav, R. (2018). The Release Management Process Explained: Optimizing IT. Retrieved from

Forselius, P., & Kakola, T. (2009, January). An information systems design product theory for software project estimation and measurement systems. In System Sciences, 2009. HICSS'09. 42nd Hawaii International Conference on (pp. 1-10). IEEE.

Fowler, M. (2006). Continuous Integration. Retrieved from

Gaston, D., Peterson, J., Permann, C., Andrs, D., Slaughter, A., & Miller, J. (2014). Continuous integration for concurrent computational framework and application development. Journal of Open Research Software, 2(1).

Henson, E. (2009). News, Tips, and Advice for Technology Professionals - TechRepublic. Retrieved from

Holck, J., & Jørgensen, N. (2003). Continuous integration and quality assurance: A case study of two open source projects. Australasian Journal of Information Systems, 11(1).

Jfrog Artifactory. (2018). Artifactory - Universal Artifact Repository Manager - JFrog. Retrieved from

Jyothi, V. E., & Rao, K. N. (2011). Effective implementation of agile practices. International Journal of Advanced Computer Science and Applications, 2(3).

Kaur, M. R., Choudhary, M., & Mehta, M. R. (2012). Agile Process: An Enhancement to The Process Of Software Development. International journal of computer science and network security (IJCSNS), 12(7), 101-105.

Kawaguchi, K. (2018). Meet Jenkins - Jenkins - Jenkins Wiki. Retrieved from

Oracle. (2014). Developing Applications Using Continuous Integration. Retrieved from

Scholte, O. (2018). Maven – Password Encryption. Retrieved from

Van Der Storm, T. (2005, September). Continuous release and upgrade of component-based software. In Proceedings of the 12th international workshop on Software configuration management (pp. 43-57). ACM.

Vlaanderen, K., Jansen, S., Brinkkemper, S., & Jaspers, E. (2011). The agile requirements refinery: Applying SCRUM principles to software product management. Information and software technology, 53(1), 58-70.

Wright, H. K., & Perry, D. E. (2012, June). Release engineering practices and pitfalls. In Proceedings of the 34th International Conference on Software Engineering (pp. 1281-1284). IEEE Press.



  • There are currently no refbacks.

Copyright (c) 2018 International Journal of Experiential Learning & Case Studies

Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 International License.