In software engineering, continuous integration (CI) is the routine with regards to blending all engineer working duplicates to a common mainline a few times each day. The principle point of CI is to avert coordination issues. Jenkins is a driving open source constant coordination server worked with Java. It is utilized to manufacture and test programming ventures constantly making it simpler to incorporate changes to the task. It provides more than 985 plugins to help to build and to test any project. Continuous Integration (CI) requires developers to integrate code into a shared repository several times a day. GUI will maintain all latest jobs with their build status and continuous notification referring to design issues, code, failures, etc. Once the project is configured in Jenkins then all future builds are automated. Hence GUI will help to represent basic reporting like run status (successful, failure, unstable) and weather reports (job health). GUI will also provide automatic continuous regression run which will give flag details of new relevant changes in build compared to last run and easy access for code change mapping and auto-selection. GUI will help to eliminate manual verification.

Jenkins, Continuous Integration and Continuous Delivery, Auto Build Trigger, Python Django, Perforce

[1] W. y. PetroChina, Z. t. PetroChina and G. y. PetroChina, ”Design and implementation of continuous integration scheme based on Jenkins and Ansible”, In the Proceedings of the 2018 International Conference on Artificial Intelligence and Big Data (ICAIBD), Chengdu, pp. 245- 249, 2018.
[2] S. A. I. B. S. Arachchi and I. Perera, ”Continuous Integration and Continuous Delivery Pipeline Automation for Agile Software Project Management”, In the Proceedings of the 2018 Moratuwa Engineering Research Conference (MERCon), Moratuwa, pp. 156-161, 2018
[3] N. Seth and R. Khare, ”ACI (automated Continuous Integration) using Jenkins: Key for successful embedded Software development”, In the Proceedings of the 2015 2nd International Conference on Recent Advances in Engineering and Computational Sciences (RAECS), Chandigarh, pp. 1-6, 2015.
[4] P. Rai, Madhurima, S. Dhir, Madhulika and A. Garg, "A prologue of JENKINS with comparative scrutiny of various software integration tools", In the Proceedings of the 2015 2nd International Conference on Computing for Sustainable Global Development (INDIACom), New Delhi, pp. 201-205, 2015 .
[5] S. Puri-Jobi, "Test automation for NFC ICs using Jenkins and NUnit", In the Proceedings of the 2015 IEEE Eighth International Conference on Software Testing, Verification and Validation Workshops (ICSTW), Graz, pp. 1-4, 2015.
[6] C. Mamatha, S C V S L S R. Kiran, “A Novel Approach for Cloud Computing Environment "Implementation of DevOps Architecture in the project development and deployment with help of tools”, International Journal of Scientific Research in Computer Science and Engineering, Vol.6, Issue.2, pp.87-95, 2018.
[7] C. Sisodiya P. Sharma, "Scrutiny to Effectiveness of Various Software Process Model", International Journal of Scientific Research in Computer Science and Engineering, Vol.5, Issue.2, pp.88-93, 2017.