CI/CD PIPELINE SIMULATOR: A BROWSER-BASED FRAMEWORK FOR INTERACTIVE DEVLOPS EDUCATION AND DEPLOYMENT WORKFLOW VISUALIZATION
DOI:
https://doi.org/10.5281/zenodo.21410124Keywords:
CI/CD Pipeline, DevOps Education, Tkinter, Software Deployment Simulation, Continuous Integration, Pipeline Visualization, Python GUIAbstract
The complexity of modern software delivery has proven that CI/CD pipelines are crucial elements of professional practices. Despite its wide application in the real world, practical tools to learn and explore the concept remain limited in educational context. This paper proposes a desktop-based CI/CD Pipeline Simulator built using Tkinter, to bridge theoretical concepts and practical execution. The simulation consists of the three main parts of the deployment pipeline, build, test and deployment. The integrated tool runs all three parts sequentially within a single executable. A user can input Python code, then the system can compile and scan code for possible errors, and simulates the deployment process. Real-time progress bars and a log to detail the step by step processing provide users instant feedback throughout the process. Upon successful deployment, it creates a dynamic simulated prototype of an application, allowing UI characteristics such as labels on buttons, colors of backgrounds, and interactive functions to be changed by only manipulating variables within the code. It encourages learners to experience pipeline steps without needing to configure servers, cloud accounts, or complex tooling. Experiments suggest the tool effectively demonstrates basic DevOps practices such as verification of build, conditional testing gate and environmental dependent deployment. The tool is portable across different platforms, and effective for undergraduate courses, independent study, and rapid prototyping. This project establishes a feasible educational tool for DevOps teaching, and laid groundwork for further developments such as container integration, trigger of branches and multi-environment staging
References
I. M. Shahin, M. A. Babar, and L. Zhu, “Continuous integration, delivery and deployment: A systematic review on approaches, tools, challenges and practices,” IEEE Access, vol. 5, pp. 3909–3943, 2017.
II. L. Chen, “Continuous delivery: Huge benefits, but challenges too,” IEEE Software, vol. 32, no. 2, pp. 50–54, Mar. 2015.
III. J. Humble and D. Farley, Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Boston, MA: Addison-Wesley, 2010.
IV. B. Fitzgerald and K. J. Stol, “Continuous software engineering: A roadmap and agenda,” J. Syst. Softw., vol. 123, pp. 176–189, Jan. 2017.
V. S. Zampetti, S. Scalabrino, R. Oliveto, G. Canfora, and M. Di Penta, “How open source projects use static code analysis tools in continuous integration pipelines,” in Proc. IEEE/ACM 14th Int. Conf. Mining Softw. Repositories (MSR), Buenos Aires, Argentina, 2017, pp. 334–344.
VI. Python Software Foundation, “Tkinter — Python interface to Tcl/Tk,” Python 3 Documentation, 2024. [Online]. Available: https://docs.python.org/3/library/tkinter.html
VII. R. Hilton, T. Tunnell, K. Huang, D. Marinov, and D. Dig, “Usage, costs, and benefits of continuous integration in open-source projects,” in Proc. 31st IEEE/ACM Int. Conf. Automated Softw. Eng. (ASE), Singapore, 2016, pp. 426–437.
Additional Files
Published
How to Cite
Issue
Section
License
Copyright (c) 2026 International Educational Journal of Science and Engineering

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