Manage recurring jobs
Review the recurring jobs on your instance, check their run history, and adjust their run schedules
Recurring jobs
Run any job or action on a schedule you define, from a nightly cleanup to an hourly compliance check
Cloud Management Platform (CMP) can run any job or action on a recurring schedule. Use a recurring job to power servers on before the working day and shut them down after it, or to check one rule every hour while others run once a day. CMP ships with a set of built-in recurring jobs, and you can add your own.
Overlapping runs
A recurring job normally has only one active run at a time. If a run is still going when the next one is due, CMP skips the new run and records it in the job engine log, typically /var/log/cloudbolt/jobengine.log.
A recurring job can instead be set to allow parallel runs, so a new run starts even while the previous one is still going. The built-in Auto-power control servers and Auto-power control resources jobs work this way.
Export and import
Every recurring job can be exported and imported. A recurring job created from an action can also encrypt its secrets with a password on export. See Recurring jobs with secrets.
Create recurring jobs
Add a recurring job from a job you already run, from an action, from a source code repository, or from a file
Built-in recurring jobs
The recurring jobs that ship with Cloud Management Platform (CMP), and their default state
Recurring jobs with secrets
Protect passwords and other sensitive values with your own password when exporting a recurring job