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

For a global cybersecurity company that must stay ahead of hackers, fraudsters, and cyber‑crime trends, the cumbersome legacy processes for building, testing, and releasing software were a huge challenge.

Organization

Global cybersecurity solutions for enterprises, governments, and SMBs

Programming Languages

C/C++, Node.js, Python, Golang

Platform

Docker/Kubernetes, Linux, macOS, Windows

Version Control System

GitLab

Build Tools

Makefile, Jenkinsfile

Background

This international cybersecurity firm serves enterprises, governments, and small businesses worldwide. The development team constantly juggles many concurrent projects, including virtualization tools such as kernel‑based KVM, IKVM, and Oracle’s open‑source VirtualBox. While inter‑project dependencies are well managed, almost everything else is driven by cron jobs – the time‑based scheduler native to Unix‑like operating systems.

Goal

Move all build, test, and release activities to Jenkins, eliminating reliance on cron jobs and ad‑hoc scripts.

Solution and Results

The primary objective was to establish an automated CI/CD toolchain. By using several Jenkins steps, the team replaced each project's cron scripts and Makefiles with a dedicated Jenkinsfile , leveraging Jenkins plugin APIs or HTTP‑based APIs instead of raw shell commands.

Another challenge emerged: migrating all source code to GitLab.

Developers now push code to GitLab, which triggers Jenkins to run the corresponding Jenkinsfile. Code is built inside containers; the backend is written in Python/C++, the frontend in Node.js. The resulting images are pushed to a private Harbor registry. Jenkins then pulls the new images, deploys them to a test environment, runs automated tests, and if they pass, the product manager can release the latest version.

Key steps included:

Convincing developers to adopt Jenkins.

Creating a Jenkinsfile for each project.

Removing Makefiles and cron scripts.

Making Jenkins the only viable option for developers.

Notifying users of build/test results via Slack and email.

Integrating GitLab using the Jenkins‑GitLab plugin.

Integrating containers using the Jenkins‑Docker plugin.

Monitoring Jenkins with Grafana and Prometheus.

Now every team member has a Jenkins account, and all activities are visible through the Jenkins UI, effectively creating a DevSecOps hub. The outcomes include:

Fully automated triggers for all pipelines.

Real‑time visibility for developers and QA on what their code is doing.

Simplified code management through GitLab integration.

Easier image handling via private registry integration.

Continuous Jenkins status visibility to detect server or service failures promptly.