Draft: Batch deployment.associations[].values before POSTing to Jira

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

What does this MR do and why?

Batch deployment.associations[].values before POSTing to Jira

This is in order to comply with the schema for POST /rest/deployments/0.1/bulk, that won't accept a deployment with an association containing more than 500 values.

Our schema file is modified to reflect this constraint.

That schema is then used for checking the stubbed request in the test.

Batching is done in a private method of the Jira Connect client. For convenience, the Grape entities are converted to JSON before batching, the way they are expected to be converted to send a request.

References

Intending to close this issue.

Documentation for relevant endpoint

MR acceptance checklist

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

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.