Skip to content

api: Expose `archived` field for CI jobs

What does this MR do and why?

Adds an archived field to CI job entities. Since archived jobs cannot be restarted or "played", this will allow API users to notice that jobs are not available and handle it specifically rather than getting hit with a generic 403 Forbidden error message.

api: Expose archived field for CI jobs

This allows tools to know whether play will work or not before attempting and getting a generic "403 Forbidden" error.

MR acceptance checklist

LGTM from my look at it.

How to set up and validate locally

CI should cover it, but API queries for jobs should now return an archived field with a boolean value.

Merge request reports