GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves jobs associated with a specific GitLab runner by its ID. It is useful for monitoring and managing CI/CD jobs executed by runners in GitLab. For example, users can filter jobs by status, order them by ID, paginate results, and specify sorting order to get detailed job information for a particular runner.

Use Case Examples

  1. Retrieve all jobs for a runner with ID 123, filtering by status 'running' and sorting results in descending order.
  2. Get the second page of jobs for a runner, with 20 jobs per page, to review job history.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Query Parameters Collection of optional query parameters to filter and paginate the jobs.
Path Parameters Path parameter specifying the runner ID to get jobs for.

Output

JSON

  • id - Unique identifier of the job.
  • status - Current status of the job.
  • runner_id - ID of the runner executing the job.
  • created_at - Timestamp when the job was created.
  • started_at - Timestamp when the job started.
  • finished_at - Timestamp when the job finished.
  • duration - Duration of the job execution.
  • user - User who triggered the job.
  • pipeline - Pipeline associated with the job.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the runner ID path parameter is provided and valid; missing or invalid ID will cause request failure.
  • Verify that the authentication token is valid and has sufficient permissions to access runner jobs.
  • Check query parameter values for correctness, especially enums like status and sort order, to avoid API errors.
  • If pagination parameters are used, ensure they are integers and within valid ranges to prevent unexpected results.

Links

Discussion