The rapid evolution of software delivery models has shifted the focus from manual releases toward fully automated pipelines. Continuous Integration and Continuous Deployment (CI/CD) have become central pillars of modern software engineering, enabling faster iterations, early defect detection, and consistent delivery across environments. Among the most widely adopted tools for implementing CI/CD are Jenkins, an open-source automation server known for its extensibility, and GitHub Actions, a cloud-native CI/CD platform tightly integrated with GitHub repositories.

This paper provides a comparative analysis of Jenkins and GitHub Actions in the context of DevOps practices, focusing on setup complexity, scalability, customization, integration flexibility, and costefficiency. The research highlights how Jenkins excels in flexibility and plugin support for hybrid infrastructures, while GitHub Actions simplifies workflow management through YAML-based declarative pipelines and seamless GitHub integration. The study emphasizes practical implementation scenarios in modern web projects, including Node.js and .NET Core applications. By evaluating both platforms through performance metrics and developer experience, the paper aims to guide software teams in choosing an optimal CI/CD solution aligned with their project scale and organizational maturity.

The study uses a comparative methodology supported by literature review and prototype
evaluation in Node.js and .NET environments

https://knowledgecenter.ubt-uni.net/cgi/viewcontent.cgi?article=5208&context=conference