Compliant Kubernetes Service documentation has moved

Please note: You are not reading Kubernetes documentation. If you're looking for Compliant Kubernetes Service documentation, it has moved. Read more here.

Jobs on The Platform are what actually run your applications, databases, caches, and everything else that makes up an environment. Jobs are a one-to-one mapping to containers - every running job has exactly one container. What that job’s container is running is defined by the service. All jobs belong to a service, but a service can have more than one job running.

Types of Jobs

Deploy Jobs

Deploy jobs are the most common job type. These are the jobs that run a container indefinitely. See the list of service types for details on what each type’s containers run.

Build Jobs

Build jobs are the jobs that build the code you push, creating a new image and redeploying the service if the build is successful.

Worker Jobs

Worker jobs are a special job type that are unique to code services. Worker jobs are functionally similar to deploy jobs, but execute a different procfile target. Read more in the Workers article.

Backup and Restore Jobs

Backup and restore jobs correspond to the database backups and restore, initiated via either CLI commands or automated nightly database backups. When the requested task has been completed, the jobs will terminate.

Console Jobs

Console jobs represent an open secure console session. In the event of an unclean exit, a console job will eventually get cleaned up and stopped.

Rake Jobs

Rake jobs represent a running rake task, and will terminate when finished.

Job States

The following are common job states that you might see.

  • scheduled - A host has not yet been found to run the job on.
  • running - The job is in progress.
  • finished - The job is complete.

See also