This documentation describes Pivotal Scheduler.
Pivotal Scheduler is a service for scheduling the execution of Diego tasks, such as database migrations, emails, or batch jobs, as well as the execution of outbound HTTP calls.
Pivotal Scheduler enables developers to do the following:
- Create, run, and schedule jobs and view job history.
- Create, run, and schedule calls and view call history.
The following table provides version and version-support information about Pivotal Scheduler.
|Release date||February 21, 2019|
|Compatible Ops Manager version(s)||v2.3.x or later|
|Compatible Pivotal Application Service version(s) *||v2.3.x or later|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
Pivotal Scheduler requires a MySQL database.
You can use either of the following:
- MySQL for Pivotal Platform v2.3 or later. See MySQL for Pivotal Platform.
- An external MySQL database
If your app uses a buildpack that does not generate a
webprocess type, such as Ruby or Python, you should do the following:
- Before pushing your app, create a Procfile in the root directory of the app.
- Declare a
webprocess type in the file.
If you do not declare this process type, your app will not be accessible through the cf CLI after you create Scheduler jobs for it.
The maximum number of tasks that you can schedule is determined by the memory and disk quotas in the Pivotal Scheduler org and space. For more information, see Running Tasks.