Cronjobs

There are several cronjobs defined in our infrastructure. They can be in several places, such as:

• as cronjob directly on the servers (most likely deployed via our infrastructure Ansible repo)

• as GitLab CI/CD pipelines

• in applications (e.g. Celery tasks)

Time	Action	Source
*:03	Incremental rsnapshot server backups	backup_fs Ansible role
*:43	MySQL mybackup / mydumper database backups	backup_db Ansible role
02:22	Garbage collecting	Docker Registry
03:33	Automatic server & service reboots	reboot Ansible role
04:44	Scheduled CI/CD Docker image builds	Docker Images
05:55	Scheduled CI/CD test & nightly build runs	Python Libraries & Blueprints

Important

All cronjobs need to be in sync to provide / ensure a stable environment. Always try to follow the following cronjob schedules, so that a reboot won’t interfere with a service, backup job, or alike.

Hint

Please note if a new service or server is automatically rebooted, the maintenance window in the Monitoring must also be updated.