You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Spring Data releases, we update multiple releases for multiple projects. This results in one GET to obtain the current release and multiple DELETE and POST roundtrips to delete old releases and create new ones.
For a project, we have all details of the desired state at hand so it would be neat to have a resource to post the release state containing all releases that should be listed under a project. It would correspond with a PUT request where the server side would figure out which releases to delete, which to update and which to retain.
The benefit for the API is to reduce the number of roundtrips from 15 /* modules */ * (1 + /* GET */ + 16 /* approx. 8 versions to delete and 8 versions to add on a typical release day */) plus all retries when rate limiting or 40x errors happen to 15 roundtrips.
The text was updated successfully, but these errors were encountered:
For Spring Data releases, we update multiple releases for multiple projects. This results in one
GET
to obtain the current release and multipleDELETE
andPOST
roundtrips to delete old releases and create new ones.For a project, we have all details of the desired state at hand so it would be neat to have a resource to post the release state containing all releases that should be listed under a project. It would correspond with a
PUT
request where the server side would figure out which releases to delete, which to update and which to retain.Something along the lines of:
The benefit for the API is to reduce the number of roundtrips from
15 /* modules */ * (1 + /* GET */ + 16 /* approx. 8 versions to delete and 8 versions to add on a typical release day */)
plus all retries when rate limiting or40x
errors happen to15
roundtrips.The text was updated successfully, but these errors were encountered: