An error occurred while fetching the assigned milestone of the selected merge_request.
Rename `build_events` to `job_events`
What does this MR do?
This MR renames build_events
to job_events
everywhere. That way there is no more confusion on what param to use.
Its job_events
.
We will need to support older params in API V3 thought.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
The build_events
attribute was accidentally ignored in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10586 causing https://gitlab.com/gitlab-org/gitlab-ce/issues/31620
@zj already suggested this solution, but the tools for zero downtime migrations weren't in place yet.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #31620 (closed)
Merge request reports
Activity
Please register or sign in to reply