Migrating Legacy Cron Jobs to Jenkins CI/CD for a Global Cybersecurity Company

The company, a worldwide cybersecurity provider serving enterprises, governments, and SMEs, faced a cumbersome legacy workflow that relied heavily on cron jobs and Makefiles to build, test, and release software across many concurrent projects, including virtualization tools like KVM and VirtualBox.

The primary objective was to eliminate cron‑based scripts and migrate all automation to Jenkins, creating a unified CI/CD toolchain.

Solution steps included replacing each project's cron job and Makefile with a Jenkinsfile, using Jenkins plugins and HTTP APIs instead of shell commands, and moving all source code to GitLab so that commits automatically trigger Jenkins pipelines. Builds run in containers, with back‑end components in Python/C++ and front‑end in Node.js, and resulting images are pushed to a private Harbor registry for deployment to test environments.

Additional practices covered convincing developers to adopt Jenkins, notifying stakeholders of build and test results via Slack and email, integrating Jenkins with GitLab through the Jenkins‑GitLab plugin, connecting Docker via the Jenkins‑Docker plugin, and monitoring Jenkins health using Grafana and Prometheus.

After implementation, every team member has a Jenkins account, providing full visibility through the Jenkins UI, effectively creating a DevSecOps hub. The outcomes include fully automated triggers, real‑time code status for developers and QA, easier code management with GitLab, simplified image handling with a private registry, and continuous visibility of Jenkins status to quickly detect server or service failures.