Make a GET request to this resource to retrieve the list of system jobs.

The resulting data structure contains:

{
    "count": 99,
    "next": null,
    "previous": null,
    "results": [
        ...
    ]
}

The count field indicates the total number of system jobs found for the given query. The next and previous fields provides links to additional results if there are more than will fit on a single page. The results list contains zero or more system job records.

Results

Each system job data structure includes the following fields:

• id: Database ID for this system job. (integer)
• type: Data type for this system job. (choice)
• url: URL for this system job. (string)
• related: Data structure with URLs of related resources. (object)
• summary_fields: Data structure with name/description for related resources. The output for some objects may be limited for performance reasons. (object)
• created: Timestamp when this system job was created. (datetime)
• modified: Timestamp when this system job was last modified. (datetime)
• name: Name of this system job. (string)
• description: Optional description of this system job. (string)
• unified_job_template: (id)
• launch_type: (choice)
  • manual: Manual
  • relaunch: Relaunch
  • callback: Callback
  • scheduled: Scheduled
  • dependency: Dependency
  • workflow: Workflow
  • webhook: Webhook
  • sync: Sync
  • scm: SCM Update
• status: (choice)
  • new: New
  • pending: Pending
  • waiting: Waiting
  • running: Running
  • successful: Successful
  • failed: Failed
  • error: Error
  • canceled: Canceled
• execution_environment: The container image to be used for execution. (id)
• failed: (boolean)
• started: The date and time the job was queued for starting. (datetime)
• finished: The date and time the job finished execution. (datetime)
• canceled_on: The date and time when the cancel request was sent. (datetime)
• elapsed: Elapsed time in seconds that the job ran. (decimal)
• job_explanation: A status field to indicate the state of the job if it wasn't able to run and capture stdout (string)
• execution_node: The node the job executed on. (string)
• launched_by: (field)
• work_unit_id: The Receptor work unit ID associated with this job. (string)
• system_job_template: (id)
• job_type: (choice)
  • "": ---------
  • cleanup_jobs: Remove jobs older than a certain number of days
  • cleanup_activitystream: Remove activity stream entries older than a certain number of days
  • cleanup_sessions: Removes expired browser sessions from the database
  • cleanup_tokens: Removes expired OAuth 2 access tokens and refresh tokens
• extra_vars: (string)
• result_stdout: (field)

Sorting

To specify that system jobs are returned in a particular order, use the order_by query string parameter on the GET request.

?order_by=name

Prefix the field name with a dash - to sort in reverse:

?order_by=-name

Multiple sorting fields may be specified by separating the field names with a comma ,:

?order_by=name,some_other_field

Pagination

Use the page_size query string parameter to change the number of results returned for each request. Use the page query string parameter to retrieve a particular page of results.

?page_size=100&page=2

The previous and next links returned with the results will set these query string parameters automatically.

Searching

Use the search query string parameter to perform a case-insensitive search within all designated text fields of a model.

?search=findme

(Added in Oracle Linux Automation Manaer) Search across related fields:

?related__search=findme