Expose `duration` in Job API entity
What does this MR do?
Expose duration in Job API entity, as suggested by #35794 (moved)
Are there points in the code the reviewer needs to double check?
I haven't added any specs are the current ones doesn't test neither all serialized job attributes, but I'm thinking about a refactor for all the API::Jobs to better rely on schemas (and define missing ones). I can tackle this in a separate MR if it sounds good to you.
Why was this MR needed?
To close #35794 (moved), but mostly at another excuse for me to contribute more to GitLab and getting progressively more familiar with its code base.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together