Add Project, Job, Pipeline GLQL presenters

What does this MR do and why?

Configure GLQL presenters for the newly added types: Project, Job and Pipeline.

References

Screenshots or screen recordings

image

image

image

How to set up and validate locally

Try some GLQL queries yourself:

title: Jobs
query: type = Job and project = "gitlab-org/gitlab-test"
fields: id, name, status, webPath, stage, kind, duration, coverage, failureMessage, refPath, commitPath, source, schedulingType, tags, active, stuck, allowFailure, cancelable, retryable, playable, manualJob, scheduled, retried, triggered, created, started, finished, queued, erased
limit: 5
display: table
title: Pipeline
query: type = Pipeline and project = "gitlab-org/gitlab-shell" and status = success
fields: id, iid, path, status, ref, refPath, sha, commitPath, source, configSource, duration, coverage, computeMinutes, totalJobs, failedJobsCount, failureReason, yamlErrors, yamlErrorMessages, warnings, complete, child, latest, stuck, active, cancelable, retryable, created, updated, started, finished, committed
limit: 5
display: table
title: Project
query: type = project and namespace = "gitlab-org"
fields: id, fullPath, webUrl, description, descriptionHtml, visibility, archived, starCount,
  forksCount, lastActivity, path, created, updated, issuesEnabled, mergeRequestsEnabled,
  secretPushProtectionEnabled, duoFeaturesEnabled, forked, openIssuesCount, openMergeRequestsCount, group
limit: 10
display: table

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Daniele Rossetti

Merge request reports

Loading